TestNG Annotations and its uses

-

In this article we will go through some TestNG Annotations and their uses.

TestNG Annotations and its uses

  • @BeforeSuite
  • @BeforeTest
  • @BeforeClass
  • @BeforeMethod
  • @Test
  • @AfterMethod
  • @AfterClass
  • @AfterTest
  • @AfterSuite
  • @Guice
  • @Parameters
    • Added in testng.xml file with parameters and value tag after suite/ test tag.
    • Parameters defined at suite level will be applicable for all the tests by default
    • Parameters defined at test level will override the parameters defined at suite level.
    • Not suitable for large scale applications
  • @DataProvider
    • DataProvider is called in the test method with the name.
    • Uses external datasource to import the data.
    • If no DataProvider name is provided, it takes class name by default.

TestNG keywords for Test Method

  • priority
    • Can be -ve
    • Default priority is 0.
    • If priority is not mentioned, the sequence of the execution will be based upon the alphabetical order of methods.
    • Only supports @Test method
  • enabled
    • Can be either true or false
    • If defined as false, test method is skipped.
  • invocationCount
    • Number of times you want to execute a test method.
  • invocationTimeOut
    • Time period is defined for a certain method.
  • throw new SkipException("message")
    • Includes a method in skip count. Total TCs will showcase skip methods.
  • groups
    • Logically group the test cases
    • testng.xml has to be changed accordingly
    • A test method can be part of multiple groups.
    • Contains include and exclude keywords for the test methods.
    • Whatever name is defined in run tag gets executed.
    • Groups can be grouped together by using define keyword
    • Structure of testxng.xml is
<suite name = "Sample Suite">
    <test name = "Sample test">
        <groups>
            <run>
                <include name ="group1"></include>
                <include name="group2"></include>
            </run>
        </groups>
    <classes>
        <class name="PackageName.ClassName"></class>
    <classes>
    </test>
</suite>

<suite name = "Sample Suite">
    <test name = "Sample test">
        <groups>
            <define name = " ExecuteAllGroups>
                <include name ="group1"></include>
                <include name="group2"></include>
                <include name = "group3"> <include>
            </define>
            <run>
                <include name ="ExecuteAllGroups"></include>
                <exclude name = "group4"></exclude>
             </run>
        </groups>
    <classes>
        <class name="PackageName.ClassName"></class>
    <classes>
    </test>
</suite>


  • dependsOnMethods
  • dependsOnGroups
  • dataProviderClass
    • Used when your @DataProvider is present in another class and the reference is made from different class with the help of dataProviderClass.
  • thread-count and parallel
    • To run tests/ classes/ methods in parallel
    • Example syntax given below
    • Provided at the suite level.
    • Syntax of the same is given below
<suite name= "Sample suite" thread-count="2" parallel = "tests">
    <test name = "Sample test">
        <classes>
            <class name="class1"></class>
            <class name="class2"><class>
            <class name="class3"><class>
        <classes>
    </test>

    <test name ="test 2">
        <classes>
            <class name="class4"></class>
            <class name="class5"></class>
        </classes>
    </test>
</suite>

</suite>

  • threadPoolSize
    • Initiates multiple threads.
  • retryAnalyzer
    • Passed along with class name to re-execute the failed test cases. The class name which is passed must implement the interface IRetryAnalyzer.
  • Include or Exclude
    • Methods can be used with include or exclude keyword in a test suite.

Useful interface in TestNG

  • ITestContext
    • Used for creating custom reports.
  • IRetryAnalyzer
    • Implements re-execution of the failed test cases.
  • IAnnotationTransformer


Comments

Post a Comment

Popular posts from this blog

Azure Tutorials Series - Azure Networking

-
Image
In this article, we will learn about Azure networking concepts such as architecture, microservices, virtual networks, VPNs, subnet, VPN gateways and most importantly Network Security Group(NSG). All these terms are to be understood if you appearing for AZ900 Microsoft Azure Fundamentals exam. Azure Networking In previous articles we have learnt about Micro- services and how they work, these are alos loosely coupled architecture. Some of the features includes Independent components interact with each other with the help of queues Can be updated and deployed independently Highly scalable Supports Asynchronous messaging N-tier Architecture Supports loosely coupled architecture Application divided into multiple tiers such that higher tier can access lower tier but not vice versa Tiers are re-usable and can be updated or replaced easily without any hassle. Three-tier in general Web Tier(front end) Application tier(back end) Data tier(Storage) Virtual Network Isolated network shared by few g...
Read more

Testing in CI/CD

-
If you are part of testing fraternity you would have heard CI/CD numerous times by now. It's the talk of the software testing town. In this article, we will cover the basics of CI/CD, what actually it is and how it is implemented in software testing. What is continuous integration? In simple terms, development teams can integrate their code into a shared repository. This helps in maintaining code quality and identifying potential issues with the local version of the code at an early stage. What is continuous delivery? Everything that is being continuously merged by the development team, is continuously deployed to the live environment. Continuous delivery is often coined as ‘Continuous Deployment’ as well. Since most developers work in parallel, continuously integrating their code into one repository would mean that the master branch is continuously updated with new features. In order to ensure that there is no compromise in the code quality with so many changes...
Read more

Azure Tutorials Series - IaaS vs PaaS vs SaaS

-
Image
We already have covered Public vs Private vs Hybrid differentiation in the previous article. In this article we will be covering three categories of cloud computing with relevant examples and details. Most of you might already be using these services in your daily day-to-day tasks unaware of the face that your organisation has already started the transition into the cloud. For an example, Office 365 is a active SaaS(Software as a service) that most of us uses, VMs are examples of IaaS(Infrastructure as a service) and Azure SQL Database is PaaS(Platform as a service). Now how do we differentiate between the three categories as a user? Will cover the details below. Infrastructure as a Service(IaaS) Service provider provides you the hardware User gets some control over the hardware, can customise operating system, storage and VMs. Ensuring service is up and running is shared responsibility While cloud provider makes sure that the hardware is functioning correctly, user needs to make sure ...
Read more