Frequently Asked Question to QA Team

When Dev Team Takes 1 Day for Development, Why Does Test need 2 Days for Testing

• Development involves Design, Coding, Unit Testing, Release
• Quality of Development Deliverables can be measured by Bugs found in Test
• Quality of Test Deliverables can be measured by Bugs found in Production
•  With Pure black box testing, possibilities of reducing test estimates may prove risky
• With a mix of black box and white box testing, You can take a calculated risk of Areas of Scope (Must be covered) Vs Sanity Testing in other Areas
• Estimates should be looked at what are the areas covered in testing, Comparision of Development and Test Estimates is *NOT a* valid argument

1 Line of Code Change, Why Do you need 1 Day for Testing ?

Most common question for Test Team. What it takes to Deliver it by XX-XX-XXXX Date ?

Can we cut down Test Estimates by 1 Day ?

• Estimates should be looked to analyze Tasks Covered, Scope of Testing, Percentage of Test Automation in place. 
• With a mix of black box and white box testing, You can take a calculated risk of Areas of Scope (Must be covered) Vs Sanity Testing in other Areas

Why Automation did not catch this bug ?

• Domain expertise comes with experience and exposure. Good Testers have very good domain knowledge of product
• Obvious bugs# can be caught by automation. Layout related / Integration issues would be caught during manual exploratory testing
• Automation plus manual exploratory testing would be good approach to maintain high Quality product

We need 100% Automation

• Building automation framework before product lauch and Priority 1 cases Automation before product release is a good approach dealing with automation
• Based on events captured in production, User Workflows need to converted into equivalent integration scenarios to simulate end user scenarios
• From the production bugs# keep enhancing the Automation suite

Happy Reading!!

Selenium - Demo Test Page

UserName


Password

Selenium 2 - Good Reads

Good Read -
Exploring Selenium 2: Introduction & Lessons Learned in Selenium 1 - Selenium RC is no more required in Selenium2, You can directly manipulate the browser.

Posting below presentation after confirming with Jason Huggins.

Selenium 2 Webinar: The Next Generation of Web and Mobile Application Testing

View more presentations from hugs

Selenium 2 Webinar: The Next Generation of Web and Mobile Application Testing




Hope videos are posted soon in site

Selenium 2: The Future of Selenium is now!

View more presentations from AutomatedTester.

Selenium 2.0 beta 1 Release
Selenium 2 in .NET framework
What is Selenium2
Web Driver Roadmap
Selenium 2.0 and web driver
Migrating to Selenium 2
It's time for QTP to Die

Happy Reading!!

TestNG Example - testng - Passing parmeters in XML File

Our next post is based on my question in stackoverflow site. Let's try an example based on Cedric reply.

Below is example code

import java.util.ArrayList;

import java.util.Iterator;

import java.util.List;

import com.thoughtworks.selenium.Selenium;

import static org.testng.Assert.assertTrue;

import org.testng.annotations.*;

import com.thoughtworks.selenium.*;

public class TestNGXMLData

{

@Test

@Parameters(value={"A","B","C","D"})

public void xmlDataTest(String A, String B, String C, String D)

{ 

            System.out.println("Passing Three parameter to Test "+A +" and "+B + " and "+C);

            String[] elements = D.split(",");

            for (String element : elements)

            {

                  System.out.println("Item is "+element);

                 

            }

}

}

XML for setting parameters

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">

<suite name="Suite" parallel="none">

  <test name="Test" preserve-order="false">

   <parameter name="A" value="1"/> 

   <parameter name="B" value="2"/> 

   <parameter name="C" value="3"/> 

   <parameter name="D" value="4,5,6,7,8"/> 

    <classes>

      <class name="TestNGXMLData"/>

    </classes>

  </test>

</suite>

Right Click on XML and run it as TestNG Test. Below is output in console window

Passing Three parameter to Test 1 and 2 and 3

Item is 4

Item is 5

Item is 6

Item is 7

Item is 8

Extending this example and adding multiple tests and setting it for parallel execution and preserve test order.

Modified XML File

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">

<suite name="Suite" parallel="classes" thread-count="5">

  <test name="firstTest" preserve-order="true">

   <parameter name="A" value="1"/> 

   <parameter name="B" value="2"/> 

   <parameter name="C" value="3"/> 

   <parameter name="D" value="4,5,6,7,8"/> 

    <classes>

      <class name="TestNGXMLData"/>

    </classes>

  </test>

  <test name="secondTest" preserve-order="true">

   <parameter name="A" value="10"/> 

   <parameter name="B" value="20"/> 

   <parameter name="C" value="30"/> 

   <parameter name="D" value="40,50,60,70,80"/> 

    <classes>

      <class name="TestNGXMLData"/>

    </classes>

  </test>

  <test name="thirdTest" preserve-order="true">

   <parameter name="A" value="100"/> 

   <parameter name="B" value="200"/> 

   <parameter name="C" value="300"/> 

   <parameter name="D" value="400,500,600,700,800"/> 

    <classes>

      <class name="TestNGXMLData"/>

    </classes>    

  </test>

</suite>

Modified code adding try-catch block (Keeping up with Coding Guidelines :))

import java.util.ArrayList;

import java.util.Iterator;

import java.util.List;

import com.thoughtworks.selenium.Selenium;

import static org.testng.Assert.assertTrue;

import org.testng.annotations.*;

import com.thoughtworks.selenium.*;

public class TestNGXMLData

{

@Test

@Parameters(value={"A","B","C","D"})

public void xmlDataTest(String A, String B, String C, String D)

{ 

            try

            {

                  System.out.println("Passing Three parameter to Test "+A +" and "+B + " and "+C);

                  String[] elements = D.split(",");

                  for (String element : elements)

                  {

                        System.out.println("Item is "+element);

                       

                  }

            }

            catch(Exception e)

            {

                  System.out.println("Exception Occurred "+ e.toString());

            }

}

}

Output

Passing Three parameter to Test 1 and 2 and 3

Item is 4

Item is 5

Item is 6

Item is 7

Item is 8

Passing Three parameter to Test 10 and 20 and 30

Item is 40

Item is 50

Item is 60

Item is 70

Item is 80

Passing Three parameter to Test 100 and 200 and 300

Item is 400

Item is 500

Item is 600

Item is 700

Item is 800

Happy Reading!!

QA Skills

My Summary of QA skills for Junior/Senior QA Candidate

Junior QA

• Follows defined QA Process
• Prepares Bugs Reports, Status Reporting with all relevant information
• Manages and updates automation suite

Senior QA

• Self Organized
• Challenges the Environment, Raise testing standards by experimenting with new processes/Adopting new Tools
• Aware of Test Automation Framework Design and Development 
• Sound Technical Skills 
• Selfless - Volunteers/mentors team in terms of process/sharing best practices
• Actively involves/drives meaningful discussions and implements best practices  
• Takes calculated risks and delivers products meeting quality bar

Growing to a Test Architect Role

• What is a test architect?
• Test Architect

Impressive QA JD description - link


Every skill (DEV / QA / Automation) can be learned with interest and passion. This JD is a mix of DEV-QA-Automation. This is a very good write up.

One more interesting job-ad from link. Highlighted below are core skills / competencies. This co-relates to a lot of behavior traits

More Reads

What are key properties of great QA team member?
Tips for hiring good testers

Hiring Software Testers in an Information Age

If I Were Hiring Testers
Thoughts on Automation as a Career : Role, Responsibilities and Career Progression

Tools to evaluate for Web Testing

Time is limited, Delivering new products to customers plays a key role. Efficiency in terms of cost, time and effort is the key.

To finalize a test tool for functional/perf test automation below are few guidelines/considerations

• Pick Top 3 test tools in terms of Features provided, Cost, Cost of Training
• Review the tools using Trial versions/Demos
• Analyse effort required to learn the tools, develop the framework and manage the framework
• Evaluate cost for developing in-house tool vs Using Open Source Tools vs Licensing a Tool

Couple of Interesting tools to try out are

• Browsera - Automated browser compatability, layout, JS Errors detection
• Stella - Web Apps Functional Test Tool
• Google Layout Detection Tool
• Crossbrowser testing - For cross platform testing
• Browsermob - Website loadtesting and monitoring tools
• Page Latency Testing , Google Page Speed , web page test
• Multi-Mechanize - Google web performance and load testing framework
• browsershots - Test your web design in different browsers
• WebUI Test Studio - Silverlight, AJAX and MVC Automation
• Traffic Squeezer - Open-Source WAN/Network Optimization and Acceleration Solution
• Browserling - cross-browser testing platform
• Network Speed Simulation for Testing

 More Reads

• Automated Test Tools Evaluation Criteria
• Free Functional and Load Test Tools for Web Apps
• Website Speed Check Tools
• Free tools to measure website performance
• Complete setup guide for Ruby, Cucumber and Watir or Selenium webdriver on Windows

Happy Reading!!