Learn Software Testing with Free Lessons & Tips

public class Priority {

@Test (priority=1)
public void login() {
System.out.println("login");
}

@Test
public void email1() {
System.out.println("email1");
}

@Test (priority=-2)
public void email2() {
System.out.println("email2");
}

//I want a particular test case to run first ....we have to give the ordering

//by default priority=0
//-3 -2 -1 0 1 2 3
//if we have the same priority of 2 test cases then it will run in chronological order
}

public class TestNGAnnotations {

@BeforeMethod
public void beforeM() {
System.out.println("Before Method");
}

@AfterMethod
public void afterMethod() {
System.out.println("After Method");
}

@BeforeClass
public void beforeCl() {
System.out.println("Before Class");
}

@AfterClass
public void afterCls() {
System.out.println("After Class");
}

//Certain code before each Testname
@BeforeTest
public void beforeT() {
System.out.println("Before Test");
}

@AfterTest
public void afterT() {
System.out.println("after Test");
}

@BeforeSuite
public void beforeSuite() {
System.out.println("before Suite");
}

@AfterSuite
public void afterSuite() {
System.out.println("after Suite");
}

@Test
public void testcase1() {
System.out.println("testcase1");
}

@Test
public void testcase2() {
System.out.println("testcase2");
}

}

public class dependsonM {

@Test
public void login() {

System.out.println("login");
}


@Test (dependsOnMethods = {"login"})
public void email() {
//Intentionally I am failing this testcase
Assert.assertTrue(false);
System.out.println("logout");
}


@Test (dependsOnMethods = {"login", "email"})
public void logout() {
System.out.println("logout");
}

}

If you can do programming then, you can start your career with any programming that gives you the right package and scope is very good. But if you are feeling link, you will not be able to do programming, then learn Software Testing. Gap Doesn't matter; everything is dependent on your passion and interest.

TestNG Concepts

TestNG:

TestNG is an automation framework to run the test cases, test suites and do parallel testing. It is an advanced version of Junit. It consists of many features like annotations, groups, parameterization and listeners. It generates html reports as well which is an advanced feature.

Annotations of TestNg:

There are different types of annotations present in TestNG which are used for organized and reusable tests.

1. @BeforeSuite: The method which has this annotation will run before all the tests in the suite runs
2. @AfterSuite: The method which has this annotation will run after all the tests in the suite runs
3. @BeforeTest: The method which has this annotation will run before the tests present inside the class tag of testing.xml is run
4. @AfterTest: The method which has this annotation will run after the tests present inside the class tag of testing.xml is run
5. @BeforeClass: The method which has this annotation will run before the first test in the class is run
6. @AfterClass: The method which has this annotation will run after all tests in the class are run
7. @BeforeMethod: The method which has this annotation will run before each test method runs
8. @AfterMethod: The method which has this annotation will run after each test method runs
9. @Test: This is the main part of the test case
10. @DataProvider: This annotation is used to extract the data from excel and send it to all test methods.
11. @Parameters : To take the inputs from TestNg xml

Example:

<suite name="SampleTestNGXml">

<test name="TestNGAnnotationsExample">

<parameter name="browser" value="Firefox"/>

<parameter> name=”Url” value=” https://www.google.com”

<classes>

<class name=" TestNgExample" />classes>test>suite>

public class TestNgExample()

{

@Parameters({“browser”})

@BeforeSuite

public void  setup(String browser){

if(browser.equlas(“Firefox”)){

WebDriver driver = new FirefoxDriver();

}

else if(browser.equals(“chrome”)){

System.setProperty(“webDriver.chrome.driver”,path);

WebDriver driver = new ChromeDriver();

}

else if(browser.equals(“IE”)){

System.setProperty(“webDriver.ie.driver”,path);

WebDriver driver = new InternetExplorerDriver();

}

}

@BeforeClass

Public void browserSetup(){

DesiredCapabilities dc = new DesiredCapabilities.firefox();

driver = new FirefoxDriver(dc);

driver.manage().timeouts().implicitlywait(60,TimeUnit.SECONDS);

driver.manage().window().setSize(new Dimension(1920,1080));

}

@Parameters({“Url”})

@BeforeTest

public void beforeTest(String url){

driver.get(url);

driver.manage().window().maximize();

}

@DataProvider(name = “sample”)

public object[] getData(){

return new Object[]{

{“TestNg”}}}

@Test(dataProvider=”sample”)

Public void minTest(String searchText){

WebElement searchBox = driver.findElement(By.Id(“fakebox-input”));

searchBox.sendKeys(searchText);

}

@AfterTest

Public void afterTest(){

System.out.println(“any reporting activities using extent Reports”);

}

@AfterClass

Public void afterClass(){

driver.close();

}

@AfterSuite

Public void teardown(){

driver.quit();

}

}

List of Attributes which we use in @Test method:

• alwaysRun: If we want to run a @Test method always, we can set this attribute to true

eg: @Test(alwaysRun= true)

• enabled: If we don’t want a @Testmethod run, we can set the enabled attribute as false

eg: @Test(enabled = false)

• Priority: If we want to run our test cases based on priority ,we can use this attribute.

eg: @Test(Priority = 1)

• groups: If we want to group together @Test methods, we can use this attribute

eg: @Test(groups = “smoketesting”)

• dependsOnGroups : If we want to run a particular @Test method after a particular group of @Test method runs, we can use this attribute

eg: @Test(dependsOnGroups = “smoketesting”)

• dependsOnMethods : If we want to run a particular @Test method after a particular @Test method runs, we can use this attribute

eg: @Test(dependsOnMethods=”testMethodName”)

Example:

Public class attributeExample(){

@Test(groups=”smoketesting”)

public void test1(){

System.out.println(“This method belongs to smoketesting group”);

}

@Test(groups=”smoketesting”)

public void test2(){

System.out.println(“This method belongs to smoketesting group”);

}

@Test(dependsOnGroups=”smoketesting”)

public void test3(){

System.out.println(“This method runs  after smoketesting group methods run”);

}

@Test(dependsOnMethods=”test1”)

public void test4(){

System.out.println(“This method runs after test1 runs”);

}

@Test(enabled = false)

Public void test5(){

System.out.println(“This method will not run till test case is enabled”);

}

@Test(alwaysRun = true)

Public void test6(){

System.out.println(“This method always runs”);

}

@Test(priority=1)

Public void test7(){

System.out.println(“This method runs before any other test method runs as it has first priority”);

}

} 

depends tag in testing.xml:

Till now we have seen dependsOnMethods and dependsOnGroups used for @Test methods to depend on groups and methods. But , we can use the depends on tag in testing.xml to perform the same operation without using the attribute.

Example:

Include&Exclude Tags in TestNg.Xml:

Include and Exclude Tags are used in testing.xml to include or exclude any @Test method to run

Example:

TestNG Listeners:

TestNG listeners are used to execute before or after @test method or suite runs. There are different types of TestNG listeners. Please find them below.

IsuiteListener: This is an interface which  has two methods called onStart() and onFinish(). If a class implements this listener, these methods will run before and after the suite runs.

ITestListener: This interface is also similar to IsuiteListener but the difference is that it will run before and after Test  runs. It consists of below methods.

onStart(): This method will run before @Test method runs

onFinish():This method will run after @Test method runs

onTestFailure(ITestResult result): runs whenever a test fails

onTestSkipped(ITestResult result) : runs whenever a test is skipped

onTestSuccess(ItestResult result): runs whenever a test is succeded

IInvokedMethodListener: This listener will run before and after every method is run. It consists of two methods.

beforeInvocation(): Invokes before each method runs

afterInvoction(): Invokes after each method runs

Example:

public class sampleListener implements ItestListener,IsuiteListener,IInvokeMethodListener{

public void onStart(ISuite suite){

System.out.println(“runs before suite is started”);

}

public void onFinish(ISuite suite){

System.out.println(“runs after suite is started”);

}

public void onStart(ITestContext testContext){

System.out.println(“runs before test is started running”);

}

public void onFinish(ITestContext testContext){

System.out.println(“runs after test is started running”);

}

public void onTestSuccess(ITestContext testContext){

System.out.println(testContext .getName()+“ is successful”);

}

public void onTestFailure(ITestContext testContext){

System.out.println(testContext .getName()+“ is failed”);

//Taking failed Test cases screenshots

File src = ((TakeScreensot)driver).getScreenshotAs(OutputType.FILE)

FileUtils.copyFile(src, new File(path));

}

public void beforeInvocation(IInvokedMethod method,ItestResult result){

System.out.println(“This method is invoked before every method runs”);

}

public void afterInvocation(IInvokedMethod method,ItestResult result){

System.out.println(“This method is invoked after every method runs”);

}

}

Including listener in Testngclass:

@Listeners(sampleListener)

public class testngSampleTest(){

@Test

public void  test1(){

Including listener tag in TestNg.xml:

Debugging is a step by step process of identifying the errors present in the code.  The question here is what kind of mistakes? Usually errors are of two types.
1. Syntax errors
2. Logical errors.
Syntax errors are those where an error present in the syntax of a construct of a language. Such errors are identified by a compiler.
 Logical errors are those where an error present in the logic of the software problem statement. i.e. Software program runs but produces incorrect output.
 Logical errors are identified by the debugging process.  

How to perform Debugging?
 Debugging is not rocket science. It is straightforward. One who knows the software programming knows the debugging activity, but do not see the activity they are performing is debugging.  Let me explain with an example.
 Consider an example C Program of finding a square root of a number without using an SQRT function. Usually, the code for this program is around 20 lines.
 Anyone who writes the program will follow three steps. i.e.
1. read inputs
2. process inputs to produce outputs
3. Display outputs
To read inputs from the console in C, one uses scanf() function.
Similarly to display the outputs on the console, one uses printf() function.
Process operation contains different control structures, loops etc..
On completing the program, one tries to run it to see the written program is correct or not.
 To check that, one need to give input value to the program say 9. The square root of 9 is three, but the program is displaying other than 3. Now we know that the program is written is not performing Square root functionality correctly.  Next step we do is we start analysing the code by printing intermediate values of the logic with the help of the print() function and re-run the program.  Now you see the intermediate output displayed correctly or not.  If correct, then you know the logic written up to this point is right. Then shift the print() function down and check again.  Repeat the process until you find that the intermediate output is deviating from the correct output.  It is the area we know that computation is going wrong.
 This process is called Debugging. Identifying where the error accurately is called localising and correcting the error is called Fixing.  Therefore to summarise, Debugging process constitutes Debugging, Localizing and Fixing.
 Instead of placing printf() statement in the code, there are tools available. With these tools, one can mark a breakpoint and run the program up to that point and check the intermediate output variables or one can run the program statement by statement called step by step method. These features help you to identify the logical errors quickly.

Importance of Debugging?
 Usually, logical errors are complicated to remove and consumes more time in the projects to eliminate them.  So debugging process helps one to identify the logical error and eliminate them quickly.
 Finally,  with excellent Debugging skills, an average programmer/Tester become gets an extra-ordinary rating. But without debugging skills, an extra-ordinary programmer/Tester looks very ordinary.

A software whose failure may cause death or injuries to the users called Safety-Critical Software.
The software present as part of Aeroplanes, or present in Rail as railway signalling software or Automotive (current as part of cars/buses/trucks) or health care (x-rays, scanners etc.).
How is it, safety-critical?
 Let's take an example.
1. The software was written for engine control of an aeroplane. During its flight, if the software fails, then the possibility of flight crash may result in life loss or disabilities.
2. Software written for signalling of train network, failure of that may result in a train collision.
3. break systems software of a Car, whose failure may result in an accident
4. Incorrect results produced by x-rays and scanners leads to health hazards to people.
Usually, all the above software are embedded softwares. As the software is safety-critical, extra care needs to be for software design and development.
Out of the four above, Avionics software is more critical because the aeroplane will not always be on the ground to switch off the system that is creating a problem.  Hence, more care needs to be taken than others while designing software or Testing software.