Technologies - TestNG Framework - Annotation attributes

-

 

Annotation Attributes - methods of annotations

Attributes are keywords that modify the annotation's function.

 

alwaysrun:
                If set to true, this test method will always be run even if it depends on a method that failed.

dataProvider
  The name of the data provider for this test method.

dataProviderClass
          The class where to look for the data provider. If not specified, the data provider will be looked on the class of the current test method or one of its base classes. If this attribute is specified, the data provider method needs to be static on the specified class.

dependsOnGroups
  The list of groups this method depends on.

dependsOnMethods
           The list of methods this method depends -Non dependent @test will be executed in Ascii order followed by dependent tests - when a single test is

dependent on multiple tests then attribute syntax will be as follows (dependsOnMethod={"methods1","method2"})


description
  The description for this method.

enabled
  Whether methods on this class/method are enabled.

expectedExceptions
         The list of exceptions that a test method is expected to throw. If no exception or a different than one on this list is thrown, this test will be marked a failure.

groups
  The list of groups this class/method belongs to.

priority
         The priority for this test method. Lower priorities will be scheduled first [-ve values also considered]- default priority is '0' - if priority is same, execution is based on Ascii order of the Tests 

timeOut
         The maximum number of milliseconds this test should take.

invocationCount 

          Executes same Test case multiple times sequentially with same set of data - default invocation count is '1'.

 

threadPoolSize 
          Used along with invocationCount - helps to execute same Test case @Test in parallel instead of sequential execution.

 

invocationTimeOut

          Used along with invocationCount - Validates Timeout of entire invocation count - throws "threadTimeOut" exception if exceeds TimeOut provided - Timeout mentioned in milliSeconds.

 

timeOut

         Validates the timeout of @Test annotation - considers each iteration of Test case for the specified timeout - throws "threadTimeOut" exception if exceeds TimeOut provided 

 

successPercentage

         Inorder to check the stability of the test based on the condition - successPercentage

 


Simple Example:

@Test(description = "This a new test", timeOut = 20000, priority = -200, dependsOnMethods = "test1", groups ="tutorial")
   public void test2(){
        ...

   }

 

Comments

Post a Comment

Popular posts from this blog

QA's approach 2 Java - Understanding Static context

-
Image
            Static Members Flow Class members In java application we are defining objects for communication.Every Object is represented as a model(class). Hence, java application is the combination of classes. And every class in java application is allowed to define following members. 1) static members 2) non-static members Static members flow using JVM architecture : Java class supports definition of 4 static members. 1) static main method 2) static block 3) static variable 4) static method Static main method Example class Demo { //empty..... } How to Compile & Execute a simple Java program? 1) Save the program in "d-drive" with name Demo.java 2) Open command prompt, navigate to the path where the java program is stored 3) Compilation: cmd/> javac Demo.java Demo.class file will be generated. 4) Execution:  cmd/>java Demo Error : main method not found... main method : 1) It is static method, hence...
Read more

QA's approach 2 Java - Collections Framework & Generics Introduction

-
Image
Why Collections & why is it called a Framework? First Question: Why Collections? Collections are used to overcome problems with variables, arrays, classes like size problem, type problem, non existence of predefined operations/methods, etc. To get a Overview of the above discussed problems, click on this link What is a Framework? Its a semi-finished re-usable application, providing some low level services, which can be customized according to our requirement.  Second Question: Why is it called a Framework? Collection API is available in util package & its called a Framework for the reason that, java programmers were not restricted to just utilize the existing classes making them final but was allowed to expand on top of the exiting classes inheriting them. Collections framework gives a clear example of when to use Interface & abstract class Classification of Collection Framework: In Collection Framework all the classes are classified into 3 cat...
Read more

Technologies - Log4J - Create Log4j Configuration File - Where ? How ? What ?

-
  Typical Steps involved in Creating Log4j Configuration file Configure the root logger - What to Log - info/debug/error/fatal messages Configure individual loggers (if needed). Specify appenders -- Where to Log -- in File/Console, etc Specify message layout/Pattern -- How to Log - format to log the message Configuring a Layout PatternLayout lets you determine how data is extracted from log events and formatted for output based on a conversion pattern. Conversion patterns act as placeholders for data that appears in each log event.  For example, let’s break down a PatternLayout commonly used in Log4j: <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/> %d{HH:mm:ss.SSS} formats the date in terms of hours, minutes, seconds, and milliseconds. %t displays the Logger’s current thread. %level displays the severity of the log event. %logger displays the name of the Logger. %m displays the event’s message. Finally, %n adds a new line for the next e...
Read more