GSoC.16 Mid-term Review

Finally, the first phase of the coding sprint for the 2016 Google Summer of Code has come and gone. Now is the time for mentors and students to begin submitting mid-term evaluations.

This blog post is a resume of my accomplishments from the time coding began till June 20, which when the midterm evaluation starts.

After 4 weeks of intense hard work, this is what I managed to achieve:

Week 1

• Arrange meetings with mentors and MACC dev team to discuss test requirements.
• Started creating a Test Plan for MACC.
• Familiarize myself more with the code base

Week 2

• Finish setting the baseline for an effective Automated Testing program i.e Had all necessary per-meetings
• Start developing the test requirements that should serve as a blueprint for the entire Automated Testing effort

Week 3

• Finish up with developing the Test Requirements Document for MACC
• Wrote Test Script for verifying Broken Links
• Wrote Test Script for verifying External Links
• Wrote Test Script for verifying Internal Links
• Wrote Test Script for verifying Broken Images

Week 4

• Writing test scripts for;
  • Field validation
  • Error message for wrong input
  • Optional and Mandatory fields
• Expanded the test coverage for the Database test suite

Looking forward to continue coding with Systers for the next six week.

Documentation | Weekly Progress Report | Github Profile

My Automated Testing Experience

Working with the Systers community as an automated sotfware tester, I recognize the importance of good testing practices and thorough test coverage for producing a quality software product.

One important thing I have learned so far with the concept of "Automated Testing" is that there are things that can only be tested manually more efficiently. This is because computers may work faster than human employees, but they are either slower to adjust to changes or require a significant amount of time and expense to develop.

With this fact established, it becomes obvious that the best strategy for ensuring quality is to develop a team with the skills and authority to implement a blended solution.

Verifying broken links using Selenium

Hi, I have started my coding sprint for the 2016 Google Summer of Code by writing a test script to check if all the links on the MACC application is working.

So basically I have achieved this task by verifying for broken links(i.e we need to check the link which is pointing to wrong URL or invalid URL).

 So if the link is pointing to a wrong or invalid URL, we get a 404 page not found error an issue in most web applications which is called Broken Link.

Below I have explain the implementation logic and my own approach:

First extract all links on the site as follows, List list=driver.findElement(By.tagName("a")); .

Then I use HttpURLConnection Class and getResponseCode method to verify the status of the response for each URL like so, 



public static int getResponseCode(String urlString) throws

MalformedURLException, IOException {

URL u = new URL(urlString);

HttpURLConnection huc = (HttpURLConnection) u.openConnection();

huc.setRequestMethod("GET");

huc.connect();

return huc.getResponseCode();

}

Next up, I will be doing thesame for the images. Cheers!