TestNG output questions

-

In this article we will cover some TestNG output questions which are usually asked in the interview written tests. The questions are bases upon the program execution flow which will help you grasp some grip over it.

TestNG Output Questions

  1. Guess the output of below program
public class AnnotationsSequence {

@Test
public void f() {
    System.out.println("@Test 1 ");
}
@Test
public void f1() {
    System.out.println("@Test 2 ");
}

@BeforeMethod
public void beforeMethod() {
    System.out.println("@BeforeMethod");
}

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

@BeforeTest
public void beforeTest() {
    System.out.println("@BeforeTest");
}

@AfterTest
public void afterTest() {
    System.out.println("@Aftertest");
}

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

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

@BeforeClass
public void beforeClass() {
    System.out.println("@BeforeClass");
}

@AfterClass
public void afterClass() {
    System.out.println("@AfterClass");
}

Output of above program(STCM) -
@BeforeSuite
@BeforeTest
@BeforeClass
@BeforeMethod
@Test 1
@AfterMethod
@BeforeMethod
@Test 2
@AfterMethod
@AfterClass
@AfterTest
@AfterSuite

Explanation - Before Test and After Test will run only once, however before method and after method depends upon your @Test methods, if you will declare 100 @Test methods, they will run 100 times.

2. Guess the output of below example -

public class AnnotationsSequence {

@BeforeMethod
public void beforeMethod() {
    System.out.println("@BeforeMethod");
}

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

@BeforeTest
public void beforeTest() {
    System.out.println("@BeforeTest");
}

@AfterTest
public void afterTest() {
    System.out.println("@Aftertest");
}

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

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

@BeforeClass
public void beforeClass() {
    System.out.println("@BeforeClass");
}

@AfterClass
public void afterClass() {
    System.out.println("@AfterClass");
}

public class Class1 extends AnnotationsSequence {

@Test
public void Method1() {
System.out.println("Inside Method 1");
}

@Test
public void Method2() {
System.out.println("Inside Method 2");
}

public class Class2 extends AnnotationsSequence {

@Test
public void Method3() {
System.out.println("Inside Method 3");
}

@Test
public void Method4() {
System.out.println("Inside Method 4");
}

Output of above program 
@BeforeSuite
@BeforeTest
@BeforeClass
@BeforeMethod
Inside Method 1
@AfterMethod
@BeforeMethod
Inside Method 2
@AfterMethod
@AfterClass
@BeforeClass
@BeforeMethod
Inside Method 3
@AfterMethod
@BeforeMethod
Inside Method 4
@AfterMethod
@AfterClass
@AfterTest
@AfterSuite

The above programs can be easily executed using TestNG.xml file, let us show you how it is achieved. 

<suite name = "Sample suite">
    <test name ="test 1">
        <classes>
            <class name ="PackageName.AnnotationsSequence"> </class>
            <class name ="PackageName.Class1"> </class>
            <class name ="PackageName. Class2"> </class>
        </classes>
    </test>
</suite>

Execute the test suite from TesntNg.xml file itself.

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

Coforge Interview Questions | Automation Testing profile

-
Image
In this article we will cover recent Coforge Interview questions asked for testing profile.  Date of Interview - 19th December 2020 Mode of Interview - Web conference through TEAMS Interviewer - Rahul Sharma Round - L1 Coforge Interview Questions | Automation testing profile Round L1 Tell me about your project I have been working as a QA for XYZ company from 5.4 years, during this tenure,  I have learnt about Manual testing, Selenium, Database testing, TestNg, framework designing and API testing. What is a webdriver? A webdriver is a an automation framework that allows executing our tests in different browsers. It also supports headless execution using HtmlUnit driver. What are hooks? @Before and @After are called Hooks, they are used before and after any test scenario. How would you like your automation framework to be designed? How can you use data properties in Test NG framework? Explain Access specifiers? Access modifiers define the visibility of the class. There are four different
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