How to use getPrefix method of org.testng.reporters.jq.IgnoredMethodsPanel class

From what you wrote it seems that you are creating browser (instantiating WebDriver) before entire test suite and then execute all the tests using the same browser instance. Although it results with faster execution time it also introduces problems like the one you are having right now.

I would suggest creating a new instance of the browser before executing each test class (or even test method). In such case you can safely use driver.quit() in your @AfterClass method. Restarting browser every test will make your tests much more stable.

EDIT comments on your newly added code

• the way you are instantiating WebDriver is not correct. If you have several test classes you will end up with multiple browser windows opened before any test is executed
• you annotated one method with both @Test and @BeforeClass - this will cause the method to be executed twice in a row

The way it should (more or less) looks like is

public class MyTest {
   protected WebDriver driver;

   @BeforeClass   //I would even suggest to use @BeforeMethod but that's up to you
   public void setUp() {
      driver = new FirefoxDriver();
      //other instantiations and assignments if necessary
   }

   @Test
   public void login() {
      driver.get("http://watever.com");
      //do whatever
   }

   @Test
   public void someOtherTest() {
      //do something else
   }

   @AfterClass   //or @AfterMethod
   public void tearDown() {
      driver.quit();
   }
}

From the TestNG documentation:

A @Test method specifies its Data Provider with the dataProvider attribute. This name must correspond to a method on the same class annotated with @DataProvider(name="...") with a matching name.

So you have to bind your data provider method to test method by name:

@DataProvider(name = "data")
public Object[][] getExcelRows() throws InvalidFormatException, IOException {
   ...
}

and

@Test(dataProvider = "data")
public void testAddPlaceApi(HashMap<Object, Object> requestMap) throws IOException {
   ...
}

This happening because you are trying to create constructors in stepdefination file without putting picocontainer dependency. Its an dependency injection framework for cucumber

Either remove the constructor or add below dependency in POM

<!-- https://mvnrepository.com/artifact/info.cukes/cucumber-picocontainer -->
<dependency>
    <groupId>info.cukes</groupId>
    <artifactId>cucumber-picocontainer</artifactId>
    <version>1.2.5</version>
    <scope>test</scope>
</dependency>

You can remove <scope>test</scope> tag if do not want to limit the transitivity of a dependency

If you want take screen shots for failed test cases with test class name use below code segment.

The assertEquals(Collection<?> actual, Collection<?> expected) documentation says:

Asserts that two collections contain the same elements in the same order. If they do not, an AssertionError is thrown.

Thus the content of the collections will be compared which, in case both the collections are empty, are equal.

If those are testng tests, then you can download the eclipse plugin for TestNG and right click and run them as test class. Testng plugin here

If you want to run the command line way of maven, you would need the maven plugin for eclipse from here Then you can right click your project and you should see an option of Run As -> Maven Test. You would need to set relevant arguments in the surefire plugin of pom or use run configuration to specify parameters like you did in -Dtest

I would suggest the testng plugin which would be simpler to just select the class and run the class or a single case or a package even.

Catching exceptions on test assertions is a bad practice, they are asserts for a reason. What you want to do is implement custom ITestListener and define required logic in onTestFailure(ITestResult result) method, code in this method will be executed if case will fail.

You need to run this with PowerMockRunner

eg.

@RunWith(PowerMockRunner.class)
@PrepareForTest({ ExampleEnumerable.class})
@Test(groups = {"LoadableBuilderTestGroup"})
public class LoadableBuilderTest {
    private ExampleEnumerable mockEnumerable;

    @BeforeMethod
    public void setUp() {
        mockEnumerable = mock(ExampleEnumerable.class);
    }
}

I got the glitch!!

The problem is with the annotation

@Test(groups = { "TestA" }, dependsOnGroups = { "setUp" })

Basically your error message is trying to say that there is no @Test method with groupname as setUp!! Coming to your question, the solution is to modify annotation for the test method as below

 @Test(groups = { "TestA" })

And in the support method modify the annotation

  @BeforeGroups (groups = {"TestA"})

I ran a sample example with this set up

public class TestSupport {

    @BeforeGroups(groups = { "sample","sample1" })
    public void beforeTest() {
        System.out.println("Before test");
    }

    @AfterGroups(groups = { "sample","sample1" })
    public void afterTest() {
        System.out.println("after test");
    }

}

and with my Test class as

public class TestClassA {

    @Test(groups = { "sample" })
    public void superTestA() {
        System.out.println("This is the actual test");
    }

    @Test(groups = { "sample" })
    public void superTestB() {
        System.out.println("This is the another test under sample group");
    }

    @Test(groups = { "sample1" })
    public void superTest() {
        System.out.println("This is another test");
    }
}

and my testng.xml as shown below

<test name="sampletest" >
     <groups>
        <run>
            <include name="sample" />
            <include name="sample1" />

        </run>
    </groups>
    <classes>
        <class name="test.global.testng.TestClassA"/>
        <class name="test.global.testng.TestSupport"/>
    </classes>

  </test>

Now this is how the test runs: beforeGroups-> superTestA/superTestB ->afterGroups and beforeGroups-> superTest -> afterGroups and closes off