Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

Package & Class grouping can be done for UNIT Testing (Maven folder structure does it always). It is appropriate as the test cases have to be changed based on the changes done in application packages and classes.

For Screen level testing Custom grouping concept can be used else packing & classification should be based on Screens – Page Object Pattern. Here based on screen changes the grouping need to be changed.

Integration test case which become cross functional demands Custom grouping where package and classification will not be enough.

Parameters are passed for a TEST or SUITE. In JUNIT static variables are used to for such purposes. Here it can be configured in XML if it is a simple parameter.

If the parameter is complex -> Data Providers can be used. Instead of single data, Data Providers can provide a list of data.

3.
TestNG Overview
Features
 TestNG is a testing framework inspired by JUnit and NUnit
 Designed to cover all categories of tests: unit, functional, end-to-end, integration etc.,
 Designed to perform Multi threaded testing, to help in load and stress testing.
 Designed to Group Test Scripts and run them selectively.
 Designed to run test scripts based on dependencies & failures.
 Designed to check module performance such as response time with test timeouts.
 Has a flexible plugin API for report creation and for even changing core behavior.
Benefits
 Overcomes the drawbacks of JUNIT Framework.
 One Stop Shop for various kinds of testing.
 Dependency testing, grouping concept to make testing more powerful and easy.
 Thins the gaps between Development and Testing and encourages Test Driven Development (TDD).
 Combined use of several TestNG's features provides a very intuitive and maintainable testing design.
 Easy Migration from JUNIT to TestNG.
 Easy Integration with framework & tools like Spring, Selenium, Guice, Jenkins etc.
 Easy Reporting

7.
TestNG – “Rhythms of Testing” with
Annotations.
The flow / Life Cycle Methods in Test in Test NG

8.
TestNG – Groups
Test class Grouping as a Package
Test class Grouping as a list of Classes
Test class Grouping as a list of Methods

9.
TestNG – Groups - continued
Test class Grouping as a list of wildcard methods names
Test class Grouping as list of custom group of methods
Adding any method to a custom group

10.
TestNG – Groups - continued
Test class Grouping as a list custom Groups with wildcards
Test class Grouping as list of Group of Groups

11.
TestNG – Groups - continued
Test class Grouping as a Partial Group or Class Level Group
Only TestConfiguration will run
Adding any class into a group leads to partial Group
Pros of Grouping
1. Easy to create test suite / test groups based on need
2. No Compilation Required
3. Custom grouping remains independent of JAVA language literals class & package
4. Custom grouping can be heavily used for Integration testing.
Cautions
1. Grouping which are not done mutually exclusive need to be carefully done, otherwise it will
lead to confusion
2. Grouping and Dependency should go hand in hand.

12.
TestNG – Dependency
Dependency to construct our own symphony both in order and based
on dependency
Independent Method
Hard Dependency – Maintains the order of run,
It will be skipped if the dependent method fails
Soft Dependency – Maintains the order of run,
but does not fails – run always

13.
TestNG – Dependency -
continued
Dependency based on Groups
Pros of Dependency
1. Failure does not get propagated as test methods are skipped based on dependency
2. Dependencies between groups can be done explicitly in xml.
Cautions
1. When dependency & grouping between methods are declared with annotations & xml,
they should go hand in hand – all dependent methods should be grouped together or all
groups should include all dependent methods

25.
JUnit vs TestNG
Feature JUnit 4 TestNG
test annotation @Test @Test
run before all tests in this suite have run – @BeforeSuite
run after all tests in this suite have run – @AfterSuite
run before the test – @BeforeTest
run after the test – @AfterTest
run before the first test method that belongs
to any of these groups is invoked
– @BeforeGroups
run after the last test method that belongs to
any of these groups is invoked
– @AfterGroups
run before the first test method in the current
class is invoked
@BeforeClass @BeforeClass
run after all the test methods in the current
class have been run
@AfterClass @AfterClass
run before each test method @Before @BeforeMethod
run after each test method @After @AfterMethod
ignore test @ignore @Test(enbale=false)
expected exception @Test(expected = ArithmeticException.class)
@Test(expectedExceptions =
ArithmeticException.class)
timeout @Test(timeout = 1000) @Test(timeout = 1000)

26.
Continued..
Other Features present only in Test NG
 Clean Parallel Processing with Thread pools, without using
Thread class.
 Annotation Transformers, Dependency Injection, Listener for
plugging in new reporting & modifying run time test scripts
executions are present.
 To run JUNIT test cases with TestNG
 To convert JUNIT test cases into TestNG test cases.
For Simple Unit Testing it does not matter whether we use JUnit or TestNG, but
when we go for TDD, Integration & end to end testing, skipping of test cases
based on logical & fail fast dependencies & Parameterized testing, clean
Multithread testing, testing groups will help a lot.
As of now, JUnit is popular for Unit Testing, TestNG is more complete & Clean
& popular for TDD, Integration & end to end testing.

27.
Groups vs Universes
 We can classify & group test cases as UNIT,
INTEGRATION & SMOKE and with in this
groups we could have Business functional
segregations.
 School of tests which has to be run has to be
grouped.
 Groups formed should be mutually exclusive.
 If Groups are not mutually exclusive, there
should be another group formed which
combines all non exclusive groups without
redundancy.
 A Group can have “N” no. of mutually
exclusive sub groups.