How to use toString method of org.testng.junit.JUnit4ConfigurationMethod class

Known Issue : If you keep Junit & TestNG both dependencies in parallel, Then TestNG dependency causes Surefire to ignore JUnit wrapper class.

Solution : There could be multiple way of handling this like we can define 2 execution, each for TestNG & JUnit and disable one as per your need.

Can you please try with this : Please remove any direct/indirect TestNG dependency.

org.testng testng 6.14.3 test

And try to add below one -

io.cucumber cucumber-testng 3.0.0

Also, I would suggest you one more thing to keep your pom.xml clean.

Key Point :

• We shall not mix direct & transitive dependencies specially their versions! Doing so can cause unpredictable outcome.

Cucumber Execution via JUnit

You shall remove cucumber-core, cucumber-java, cucumber-jvm, cucumber-jvm-deps, gherkin as these are transitive dependencies which would get added by Maven when you add below direct (main) dependencies. Just add below 2 and one for testng shared above.

 <dependency>
    <groupId>io.cucumber</groupId>
    <artifactId>cucumber-junit</artifactId>
    <version>3.0.0</version>
</dependency>

<dependency>
    <groupId>io.cucumber</groupId>
    <artifactId>cucumber-picocontainer</artifactId>
    <version>3.0.0</version>
</dependency>

Your @BeforeMethod needs to be part of the group you are running.

You can also use @BeforeMethod(alwaysRun = true) if you don't want to hardcode the value of your group and if you think you will always want to run this method, regardless of the group you are currently running.

If I understand correctly you have to generate Report from all executed TestNG cases.

However, from code which you shared, it is very visible that you will have some trouble with it. You are making a few critical mistakes and result are obvious:

• For generating reports with TestNG I will suggest grabbing information about test execution from TestNG listener. Something like:

  public final class TestNGListener extends TestListenerAdapter implements IInvokedMethodListener, ISuiteListener {
  
  @Override
  public void onStart(ITestContext context) {
      Logger.info(buildMessage(Logger.PREFIX_TEST_STARTED, context.getName()));
  }
  
  @Override
  public void onFinish(ITestContext context) {
      Logger.info(buildMessage(Logger.PREFIX_TEST_FINISHED, context.getName()));
  }
  
  @Override
  public void onTestStart(ITestResult result) {
      Logger.info(buildMessage(Logger.PREFIX_METHOD_STARTED, getMethodName(result)));
  }
  
  @Override
  public void onTestSuccess(ITestResult result) {
      Logger.info(buildMessage(Logger.PREFIX_METHOD_SUCCESS, getMethodName(result)));
      processTestResult(result);
  }
  
  @Override
  public void onTestFailure(ITestResult result) {
      Logger.info(buildMessage(Logger.PREFIX_METHOD_FAILED, getMethodName(result)));
  }
  

• You can't do everything in one method! You broke Single Responsibility Principle. Your createInstanceReport() is doing all jobs (setting report details, set system info, attach an executed test case to report) at one place. You have to redesign this logic to some logical separate operations. After redesigning your problem with the next line:

Reporting.extentReports.set(extentReports)

Could successfully disappear.

• You have to consider a case, why you need to use exactly Extent, Reports Version 3. TestNG has test reports from the box. They are poor but they are presented out of the box. If you want just to improve it a little bit you could use ReportNG over TestNG.

It is quite easy to configure: Configuring ReportNG with TestNG for HTML Reports.

It isn't maintained, but it makes TestNG reports really eye candy and understandable.

Anyway, my suggestion is to use TestNGListener for getting info about test cases execution. And read more about good programming practice.

You need to call EasyMock.replay(mock) before calling the method under test. After calling the method under test you can call EasyMock.verify(mock) to verify the mock is called.

Next you need to add another expect call with the "title" argument since you call it twice.

Code:

EasyMock.expect(mockMessageResourse.getMessage("title")).andReturn("title");    
EasyMock.expect(mockMessageResourse.getMessage("ClassB.title")).andReturn("someTitle");
EasyMock.replay(mockMessageResourse);
clientMessages = new ClientMessages(mockMessageResourse);

classToTest = new ClassB();

Assert.assertEquals("someTitle" , classToTest.getDisplayName());
EasyMock.verify(mockMessageResourse);

Because you defined dependsOnMethods for TestCaseSecond and TestCaseThird. It takes priority over priority attribute. From testng Dependencies with annotations

All the methods you depend on must have run and succeeded for you to run

TestCaseFourth has the highest priority (3) without dependency -> it runs first.

TestCaseOne() has the next highest priority (4) without dependency -> it runs second

TestCaseSecond() has the highest priority with all dependencies met (TestCaseOne ran) -> it runs third

TestCaseThird() has the highest priority with all dependencies met (TestCaseSecond ran) -> it runs fourth

Cucumber can inject Scenario object into your hook method. So you can just do something like this:

@After
public void doAfter(Scenario scenario){
    if(scenario.getStatus() == Status.PASSED){
        // Do whatever you should
    }
}

So the code inside would not execute if your scenario has completed with any different status.

Basically, you can't remotely fail a test the way you want. Your idea about interrupting the threads is pretty much the right thing to do, except I'd avoid interruption and instead post an event to, say, a LinkedBlockingQueue which you poll at the end of the test to see if it is empty or not.

If you want to avoid doing this in every test method, you can add the check in a method annotated with @AfterMethod.

Something like this:

public class YourTest {

 private LinkedBlockingQueue<String> errors;

 @BeforeMethod
 public void setUp() {
   errors = new LinkedBlockingQueue<>();
 }

 private void checkLogsForErrors(){
   // This is the method run in a separate thread.
   for (String line: iterateOverLogEntries()) {
     if (isError(line)) errors.add(line);
   }
 }

 @AfterMethod
 public void tearDown() {
   try {
     String error = errors.poll(100, TimeUnit.MILLISECONDS);
     fail("Found error: " + error);
   } catch (InterruptedException e){
     // No errors, great!
   }
 }

}

Edit: Oh, right, immediately. Why not run the test code itself in a separate thread and have the original thread just waiting for either an error signal from the log watcher, or a success signal from the test?

There is no such a good idea to have following scenario :

for (WebElement element : webDriver.findElements(locator.getBy())){
  element.click();
}

Why? Because there is no guarantee that the element.click(); will have no effect on other found elements, so the DOM may be changed, so hence the StaleElementReferenceException.

It is better to use the following scenario :

int numberOfElementsFound = getNumberOfElementsFound(locator);
for (int pos = 0; pos < numberOfElementsFound; pos++) {
  getElementWithIndex(locator, pos).click();
}

This is better because you will always take the WebElement refreshed, even the previous click had some effects on it.

EDIT : Example added

  public int getNumberOfElementsFound(By by) {
    return webDriver.findElements(by).size();
  }

  public WebElement getElementWithIndex(By by, int pos) {
    return webDriver.findElements(by).get(pos);
  }

Hope to be enough.

I don't have experience using TestNg, but I run Selenium testing through maven in docker with the below configuration:

docker-compose.yml (this will allow you to connect to a separate selenium docker container)

  image: selenium/standalone-firefox
  volumes:
    - /dev/shm:/dev/shm
  ports:
    - "4444:4444"
  expose:
    - 4444

maven_container:
  build: . # uses Dockerfile
  links:
    - remote-webdriver

  volumes:
    - <your local volume>:<container volume>
  stdin_open: true
  tty: true
  entrypoint: /bin/sh

In your pom.xml in the "maven_container" be sure to include the selenium dependency (see below).

<dependency>
    <groupId>org.seleniumhq.selenium</groupId>
    <artifactId>selenium-java</artifactId>
    <version>${selenium.version}</version>
</dependency>

Finally, the docker image for the "maven_container". Notice we need to copy our local pom.xml over the generic pom.xml generated if we want to run mvn build, etc. before mounting volumes in docker-compose.

FROM zenika/alpine-maven
RUN apk update \
    && apk add ca-certificates wget \
    && update-ca-certificates

RUN apk add vim

RUN mvn archetype:generate -B \
    -DarchetypeGroupId=net.alchim31.maven -DarchetypeArtifactId=<intended artifact ID> -DarchetypeVersion=1.7 \
    -DgroupId=com.myproject -DartifactId=MyProject -Dversion=0.1-SNAPSHOT -Dpackage=com.scalascrape
WORKDIR /usr/src/app/MyProject
RUN rm pom.xml
COPY pom.xml .

Notice! you will have to wait on the selenium server to boot before you connect to it. This is an important consideration if you want to run your tests with the docker-compose up command.