org.easetech.easytest.runner
Class DataDrivenTestRunner

java.lang.Object
  org.junit.runner.Runner
      org.junit.runners.ParentRunner<org.junit.runner.Runner>
          org.junit.runners.Suite
              org.easetech.easytest.runner.BaseSuite
                  org.easetech.easytest.runner.DataDrivenTestRunner

All Implemented Interfaces:

org.junit.runner.Describable, org.junit.runner.manipulation.Filterable, org.junit.runner.manipulation.Sortable

public class DataDrivenTestRunner
extends BaseSuite

An implementation of Suite that encapsulates the DataDrivenTestRunner.EasyTestRunner in order to provide users with clear indication of which test method is run and what is the input test data that the method is run with. For example, when a user runs the test method with name : getTestData with the following test data:

• "libraryId=1 and itemId=2"
• "libraryId=2456 and itemId=789"


then, DataDrivenTestRunner, will provide the details of the executing test method in the JUnit supported IDEs like this:
• getTestData{libraryId=1 ,itemId=2}
• getTestData{libraryId=2456 ,itemId=789}


This gives user the clear picture of which test was run with which input test data. For details on the actual Runner implementation, see DataDrivenTestRunner.EasyTestRunner

Author:

Anuj Kumar

Nested Class Summary

class

DataDrivenTestRunner.EasyTestRunner A BlockJUnit4ClassRunner Runner implementation that adds support of input parameters as part of the Test annotation.

Nested classes/interfaces inherited from class org.junit.runners.Suite

org.junit.runners.Suite.SuiteClasses

Field Summary

protected static org.slf4j.Logger

PARAM_LOG An instance of logger associated with the test framework.

Fields inherited from class org.easetech.easytest.runner.BaseSuite

methodsWithData, methodsWithNoData, runners, writableData

Constructor Summary

DataDrivenTestRunner(Class<?> klass)
Construct a new DataDrivenTest.

Method Summary

Methods inherited from class org.easetech.easytest.runner.BaseSuite

getChildren, registerConverter, withAfterClasses, withBeforeClasses

Methods inherited from class org.junit.runners.Suite

describeChild, emptySuite, runChild

Methods inherited from class org.junit.runners.ParentRunner

childrenInvoker, classBlock, classRules, collectInitializationErrors, filter, getDescription, getName, getRunnerAnnotations, getTestClass, run, runLeaf, setScheduler, sort, validatePublicVoidNoArgMethods

Methods inherited from class org.junit.runner.Runner

testCount

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

PARAM_LOG

protected static final org.slf4j.Logger PARAM_LOG

An instance of logger associated with the test framework.

Constructor Detail

DataDrivenTestRunner

public DataDrivenTestRunner(Class<?> klass)
                     throws org.junit.runners.model.InitializationError

Construct a new DataDrivenTest. During construction, we will load the test data, and then we will create a list of DataDrivenTestRunner.EasyTestRunner. The algorithm is as follows:


• STEP 1: Load the test data. This will also do the check whether there exists a DataLoader annotation at the class level
• Iterate over each method.
  For each method:
  1. If method has DataLoader annotation, it means that there is test data associated with the test method.
     In such a case add the method to the methodsWithData List.
  2. If method does not have a DataLoader annotation, then:
     1. Check if there already exists data for the method. This is possible as the data could have been loaded at the class level.
        
     2. If the data for the given method exists, add the method to the methodsWithData List.
     3. If the data does not exists for the given test method, put it aside in a list of unused methods,
  Iteration over each method ends.
  Finally create an instance of DataDrivenTestRunner.EasyTestRunner and make it use all the different types of methods we identified.
  We need to identify methods with data and methods with no data primarily to group the test methods together as well as to efficiently create new test methods for each method that has test data associated with it. This whole process will happen for each of the test class that is part of the Suite.

  Parameters:

  klass - the test class

  Throws:

  org.junit.runners.model.InitializationError - if an initializationError occurs