How to use setSplitClassAndPackageNames method of org.testng.reporters.XMLReporterConfig class

IMHO, yes they are still relevant.

With EJB3, you can test you EJB either like regular POJO, or as managed bean using an embedded EJB container.

Same for JPA, you can either embed a JPA implementation for your test and use an in-memory database, or you can mock the data layer completely.

For my last EJB project I had written a bit of glue code to test the EJB because embedded EJB container were not mature enough, but now I would go for an embedded EJB container + JUnit.

A few resources

• Blog post: How to unit test EJB 3 in 0.8 seconds
• SO question: Good unit testing resource for EJB

But there are many others easily findable

Allure has built-in aggregation functionality, just put two allure results bundles in one folder and use it as a source for your report. You will get report with two suites in it.

Once way I found is:

@Test(invocationCount = 100)

Your test annotations does not belongs to TestNG.

Replace

@Before with @BeforeTest 
@After with @AfterTest 
@Test should point TestNG library

If you're using the API, your main class is no longer a TestNG test class, just a regular Java class, so it's not surprising that Surefire no longer sees it as a test.

You can use java code record your Test video, for this code to run you also need to add jar file to your project : Reference : Road to automation

@BeforeSuite
        public void startRecording() throws Exception {    

           GraphicsConfiguration gc = GraphicsEnvironment
                   .getLocalGraphicsEnvironment()
                   .getDefaultScreenDevice()
                   .getDefaultConfiguration();

               this.screenRecorder = new ScreenRecorder(gc,
                   new Format(MediaTypeKey, MediaType.FILE, MimeTypeKey, MIME_AVI),
                   new Format(MediaTypeKey, MediaType.VIDEO, EncodingKey, ENCODING_AVI_TECHSMITH_SCREEN_CAPTURE,
                        CompressorNameKey, ENCODING_AVI_TECHSMITH_SCREEN_CAPTURE,
                        DepthKey, 24, FrameRateKey, Rational.valueOf(15),
                        QualityKey, 1.0f,
                        KeyFrameIntervalKey, 15 * 60),
                   new Format(MediaTypeKey, MediaType.VIDEO, EncodingKey, "black",
                        FrameRateKey, Rational.valueOf(30)),
                   null);
       this.screenRecorder.start();

    }

    @AfterSuite
    public void stopRecording() throws Exception {
      this.screenRecorder.stop();
    }

The maven-surefire-plugin, as of today, does not have full support of JUnit 5. There is an open issue about adding this support in SUREFIRE-1206.

As such, you need to use a custom provider. One has already been developed by the JUnit team; from the user guide, you need to add the junit-platform-surefire-provider provider and the TestEngine implementation for the new API:

<build>
  <plugins>        
    <plugin>
      <artifactId>maven-surefire-plugin</artifactId>
      <!-- latest version (2.20.1) does not work well with JUnit5 -->
      <version>2.19.1</version>
      <dependencies>
        <dependency>
          <groupId>org.junit.platform</groupId>
          <artifactId>junit-platform-surefire-provider</artifactId>
          <version>1.0.3</version>
        </dependency>
        <dependency>
          <groupId>org.junit.jupiter</groupId>
          <artifactId>junit-jupiter-engine</artifactId>
          <version>5.0.3</version>
        </dependency>
      </dependencies>
    </plugin>
  </plugins>
</build>

Also, be sure to declare the junit-jupiter-api dependency with a scope of test:

<dependencies>
  <dependency>
    <groupId>org.junit.jupiter</groupId>
    <artifactId>junit-jupiter-api</artifactId>
    <version>5.0.3</version>
    <scope>test</scope>
  </dependency>
</dependencies>

Change parallel="instances" to parallel="methods" which will execute the methods of TestRunner1 and TestRunner2 parallely but TestRunner2 will be executed after completion of TestRunner1

required change :-

<test name="Excel Test" parallel="methods">
    <classes>
         <class name="com.selenium.engine.TestRunner1"> </class>
    </classes>
</test>
<test name="Excel Test 1" parallel="methods">
    <classes>
         <class name="com.selenium.engine.TestRunner2"> </class>
    </classes>
</test>

• parallel="methods": TestNG will run all your test methods in separate threads. Dependent methods will also run in separate threads but they will respect the order that you specified.

• parallel="tests": TestNG will run all the methods in the same tag in the same thread, but each tag will be in a separate thread. This allows you to group all your classes that are not thread safe in the same and guarantee they will all run in the same thread while taking advantage of TestNG using as many threads as possible to run your tests.

• parallel="classes": TestNG will run all the methods in the same class in the same thread, but each class will be run in a separate thread.

• parallel="instances": TestNG will run all the methods in the same instance in the same thread, but two methods on two different instances will be running in different threads.

Reference :-
TestNG Documentation on Parallel running

1. @BeforeClass methods are invoked after test class instantiation.
2. Exceptions in constructor will just abort TestNG test execution and no report will be created. Whereas exceptions in @BeforeClass will be displayed in resulting report and class test methods will be skipped (This behaviour can be tweaked using -configfailurepolicy TestNG parameter).