How to use newXmlSuiteUsing method of org.testng.xml.internal.XmlSuiteUtils class

One thing I haven't yet seen mentioned is that one of the reasons behind this design decision is historical.

Before test cases where marked by annotations, they were analysed by JUnit via reflection - all public void methods, the name of which started with test, and that didn't have any arguments, were considered test cases that were run by the framework.

Had these methods allowed to also return a value, you could not have created a public helper method starting with test that calculated a value commonly used in some tests, or the framework runner would have tried to run it.

You should have made them private anyway I guess.

Additionally, this was also the high time of "a method name that starts with a verb should do something" (rather than calculate something).

I found the same error in appium as below

java.lang.NullPointerException
    at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:882)
    at io.appium.java_client.TouchAction.<init>(TouchAction.java:52)

Cause-: Because I have initialised driver in child and parent class both as below.

Child class

public class AirAsia extends Base {
@SuppressWarnings("rawtypes")
  private AndroidDriver driver;

/*
 * Sign up Page Elements
 */

@AndroidFindBy(xpath = "//*[@text='Flights']")
private MobileElement flights;}

Base Class

    public class Base {

@SuppressWarnings("rawtypes")
public AppiumDriver driver;

/*
 * General App Elements
 */

@AndroidFindBy(xpath = "//androidx.appcompat.app.ActionBar.Tab[@content-desc=\"Home\"]/android.widget.TextView")
public MobileElement home;}

Solution-:

So now you remove the driver initialisation from child class as below Child class

    public class AirAsia extends Base {
@SuppressWarnings("rawtypes")
  private AndroidDriver driver;

/*
 * Sign up Page Elements
 */

@AndroidFindBy(xpath = "//*[@text='Flights']")
private MobileElement flights;}

Hope it will help all to solve such type of errors in both Selenium and Appium using Java or any language. Just don't have to initialise driver if you are extending parent class and if yo have initialise driver in base or parent class.

I found a solution, though I think it is not the best. Instead of set method selectors at suite level you should set method selectors at test level, i.e., IAlterSuiteListener implementation (CustomAlterSuiteListener.java file) will be:

package com.sample.testflow;

import java.util.Collections;
import java.util.List;

import org.testng.IAlterSuiteListener;
import org.testng.xml.XmlMethodSelector;
import org.testng.xml.XmlSuite;
import org.testng.xml.XmlTest;

public class CustomAlterSuiteListener implements IAlterSuiteListener {

    @Override
    public void alter(List<XmlSuite> suites) {
        XmlMethodSelector xmlMethodSelector = new XmlMethodSelector();
        xmlMethodSelector.setClassName("com.sample.testflow.CustomMethodSelectors");
        xmlMethodSelector.setPriority(0);

        XmlSuite suite = suites.get(0);
        XmlTest xmlTest = suite.getTests().get(0);
        xmlTest.setMethodSelectors(Collections.singletonList(xmlMethodSelector));
    }
}

You are passing paramter <parameter name="Visit" value="123456"/> in your .xml file and you directly running your TestNG class. So it's not getting that parameter while compiling .

So you need to run your xml suite to provide a valid parameter to your TestNG class.

This is a typical example where a mock framework, such as Mockito, can help you:

public class TestClass {
  @Mock
  private ObjectMapper objectMapper;

  @InjectMocks
  private EventTransformer eventTransformer;

  @BeforeMethod
  public void setUp() {
    eventTransformer = new EventTransformerImpl();
    MockitoAnnotations.initMocks(this);
  }  
}

Here, @Mock and @InjectMocks are parts of the Mockito framework. The magic happens in MockitoAnnotations.initMocks(this) which will scan this, which in this case is TestClass, for these annotations. Mockito initializes objectMapper as a mock, and injects it into eventTransformer. You can then use Mockito to decide how objectMapper should behave.

You can read more about Mockito here.

Also, @BeforeMethod is a TestNG method, analogue with JUnits @Before.

However, many people prefer constructor injection, as proposed by davidxxx. This will make it clearer which dependencies EventTransformerImpl has, and forces it to be initialized with the correct dependencies. By doing this, there is no need to "magically" (I guess Mockito uses reflection under the hood) inject the dependencies, simply initialize the class to be tested by calling the constructor.

Your class could look something like this (here using Spring's @Autowired annotation):

public class EventTransformerImpl implements EventTransformer {

  private ObjectMapper objectMapper;

  @Autowired
  public EventTransformerImpl(ObjectMapper objectMapper) {
    this.objectMapper = objectMapper;
  }

  private String convertParametersToJson(NotificationConfig config) {
    String parametersAsJson = null;
    try {
      parametersAsJson = objectMapper.writeValueAsString(config.getOrdinaryParameters());
    } catch (IOException e) {
      logger.info("There was a problem in writing json:" + config.getParameters(), e);
      parametersAsJson = null;
    }
    return parametersAsJson;
  }
}

This will be less error prone, because with @InjectMocks, Mockito will silently ignore the injection if it fails, while calling a constructor gives the test class full control of the initialization of the test.

In Run from testNg.xml directly -By default in maven project html reports get created into test-output folder

In case we run from pom.xml using surefire plugin - Reports will get created into target\surefire-reports.

There are two problems to solve here. Firstly, we need some code that will take a screenshot and secondly, we need to get that code to run when a test fails.

Taking a screenshot is pretty easy in Selenium using the TakesScreenshot interface. So you'll need something like:

TakesScreenshot ts = (TakesScreenshot)driver;
byte[] image = ts.getScreenshotAs(OutputType.BYTES);

try {
  File screenshot = new File("/some/path/myscreenshot.png");
  FileOutputStream fos = new FileOutputStream(screenshot);
  fos.write(image);
  fos.close();
} catch (IOException ex) {
  fail("Failed to write screenshot");
}

Depending on the driver you're using you might need to use the Augmenter class too.

Running code when tests fail is going to depend on the test framework you use, not on Selenium. For example, if you're using TestNG you can write an instance of ITestListener to listen to the results of your tests and take a screenshot when one fails.

Using @Autowired will make spring automatically inject a matching bean into that field. Thus it is no longer required to define the "consultaDeutes" bean in the xml. If you'd like to use the xml definition, I believe you should define a setter for each property that you are trying to inject, eg: serveiTip, serveiGpt.

Using @Autowired in your test might require 2 additional annotation on the definition of your test class:

@ContextConfiguration(value = "/myContext.xml")
//@RunWith(SpringJUnit4ClassRunner.class) This is JUnit specific
@ActiveProfiles("dev")
public class TestCompareService {
    @Autowired(required = true)
    protected ITipService serveiTip;
    ....
}

I actually made a mistake pasting the @RunWith annotation specific for JUnit. For TestNG you can lookup this link. Apologies

1. should i use maven-surefire-plugin and do a heavy cleanup in the test package?
2. is it any way to tell hudson (not in pom.xml of the project being built) to run specific unit tests and ignore others?

If you just want to run unit tests in a single-module project, you can do

mvn test

That will run all maven lifecycle phases up to test, including compile and test-compile (as you can see in built-in lifecycle bindings, the surefire:test goal is executed in phase test). Now if you want to restrict the unit tests that are executed, you can configure the surefire:test plugin execution with the test parameter:

mvn test -Dtest=Funky*Test

(This will execute all test classes that start with Funky and end with Test)

Unfortunately, the command line configuration is limited, if you want multiple includes and excludes you will have to do some XML configuration. I'd suggest to use a dedicated profile for hudson:

<profiles>
    <profile>
        <id>hudson</id>
        <build>
            <plugins>
                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-surefire-plugin</artifactId>
                    <version>2.6</version>
                    <configuration>
                        <includes>
                            <include>**/TestA.java</include>
                            <include>**/Funky*Test.java</include>
                            <include>**/Test**.java</include>
                        </includes>
                        <excludes>
                            <!-- overrides above include -->
                            <exclude>**/TestButNotMe.java</exclude>
                        </excludes>
                    </configuration>
                </plugin>
            </plugins>
        </build>
    </profile>
</profiles>

Now you can let your hudson call maven like this:

mvn -Phudson test