How to use getFileName method of org.testng.reporters.EmailableReporter class

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.

Solved. Main problem was to override TestNG lifecycle + save maven test management. So I started to dig TestNG source code and came to next solution:

1. Extend IExecutionListener which will store needed data (queue) as a public static final member.
2. Same interface IExecutionListener participates in TestNG lifecycle: it has lifecycle callbacks onExecutionStart and onExecutionFinish. First one were used to populate queue with credentials from file, and second one is to ease GC work - clean this queue.
3. Populated queue was used inside of init method annotated with @BeforeMethod. Note: do not store value from queue as a plain member as you'll face overwriting of this member from different threads that performs tests from same class but different tests. Use ThreadLocal to provide thread isolation of this variable.
4. Special data structure that serves good for my case is BlockingQueue (in LinkedBlockingQueue implementation) with take and put as getter/setter.
5. Also do not forget to add your custom listener to your xml

This class will be called from the test case like this TestStatus.mark('testName', result, 'message you want to log') result is a boolean

class TestStatus(unittest.TestCase):

    def __init__(self):
        super(TestStatus, self).__init__()

    def mark(self, testName, result, resultMessage):
        testName = testName.lower()
        try:
            if result:
                self.log.info("Verification successful :: " + resultMessage)
            else:
                # If the test fails,
                # this calls screenshot method from util class
                self.util.screenShot("FAIL" + mapKey)
                self.log.info("Verification failed :: " + resultMessage)
        except:
            self.log.info("### Exception Occurred !!!")
            traceback.print_stack()

This is a sample test case in the test case class:

def test_accountSignup(self):
    # Generate a username and password to use in the test case
    userName = self.util.getUniqueName()
    password = self.util.getUniqueName()
    # You can ignore this, this is calling a method
    # signup from the account page (page object model)
    self.accounts.signup(userName, password)
    # This call is also from the page object, 
    # it checks if the sign up was successful
    # it returns a boolean
    result = isSignUpSuccessful()
    # test_status object was created in the setUp method
    #
    self.test_status.mark("test_accountSignup", result,
                               "Signup was successful")

The workaround mentioned in this link works fine with me

All you need to do is to add the following block of code to build.gradle file:

configurations {
   testCompile
}

I couldn't figure out how exactly you could get the JUnit 4 running with all of your dependencies, but I did notice that you're dependency on the TestNG Unitils artifact was what was causing the problem.

Note that in order to get my test working, I had to remove the repositories, the plugins other than the compiler and surefire, and the apache rampart dependencies.

The three changes I made in order to get a sample JUnit 4 test case running were:

• Remove the junitArtifactName element from the surefire configuration
• Moved the junit artifact from the dependencyManagement section to the dependency section
• Remove the unitils-testng artifact from the dependencies. You have it listed as a having a type of pom, which makes even less sense.

Note that the unitils-core is also of type pom, which doesn't make much sense.

You must use PowerMockito.spy() instead of Mockito.spy()!

Try to import static org.powermock.api.mockito.PowerMockito.spy;

What logging framework is used ? I would provide custom config file to it instead of setting it via API. I think java.util.logging is used, my choice would be jul--over-slf4j + slf4j-api + logback-classic, then set loggers and appenders in logback's config file.

We have developed a simple executable to generate a docx file from Allure results, with option to generate a pdf file using some third-party libraries:

https://github.com/typhoon-hil/allure-docx

Yes, it is possible but the version of TestNG that allow using interface methods in tests is not released yet. You need to download it from this repository.

If you use Maven you can specify additional repository in your pom.xml:

<repository>
    <id>testng</id>
    <name>testng</name>
    <url>https://oss.sonatype.org/content/repositories/snapshots</url>
</repository>

And then add TestNG dependency:

<dependency>
    <groupId>org.testng</groupId>
    <artifactId>testng</artifactId>
    <version>6.11.1-SNAPSHOT</version>
</dependency>

Example:

package test;

import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Test;

public class DummyTest implements ITest {

    @BeforeMethod
    public void beforeTest() {
        System.out.println("before from class");
    }

    @Test
    public void test1() {
        System.out.println("I am test1");
    }
}

and ITest interface

package test;

import org.testng.annotations.BeforeMethod;

public interface ITest {

    @BeforeMethod
    default void beforeDefaultInterface() {
        System.out.println("before from default interface method");
    }
    @BeforeMethod
    static void beforeStaticInterface() {
        System.out.println("before from static interface method");
    }
}

The output of the test above will be:

    before from default interface method
    before from static interface method
    before from class
    I am test1