testng | TestNG testing framework | Testing library

You can add the parameters from the code using @BeforeSuite method along with ITestContext as an argument(which would be automatically injected by testng). No need to change the main method.

Before suite method would be run before any test method is executed.

You need to define a default constructor for TestsPage. (Not just for the base class) TestNG tries to create an object of the test class by the following methods:

Loops all constructors:

1. Checks if any constructor is defined with @Parameters
2. Check if any constructor annotated with @Factory.

If there are no such constructors then:

1. At last it checks to create the test class using a default constructor.

So currently your code fails the above three criteria. Hence the exception.

Try adding a default constructor and it would work.

You can add alwaysRun = true in @AfterClass annotation. like @AfterClass(alwaysRun=true).

If your test classes are independent of each other then it is good to use separate session for each test class. In this case you have to write @AfterClass method in each of test class to close individual session.

The basic problem with your code is that you have parameterised your constructor.

TestNG ONLY knows how to invoke the default constructor (no arguments constructor). In your case, you have a parameterised constructor that seems to accept a WebDriver driver instance and TestNG does not know how to instantiate this.

The easiest fix to get past this problem would be to do the following:

1. Remove the parameterised constructor and just stick to default constructor.
2. Employ an approach which abstracts out the WebDriver logic which your tests can basically invoke to get a WebDriver instance.
3. Also please try to seggregate page object classes and test classes. (Your current class AnalizesiPreturi violates this expectation)

Sometime back I built a library called autospawn which uses an annotation driven approach for browser instance management.

You can refer to https://github.com/RationaleEmotions/autospawn#how-to-use-testng

Alternatively you can make use of TestNG listeners using which you can instantiate webdriver instance and make it available via a ThreadLocal instance.

For more details please refer to my blog post https://rationaleemotions.com/parallel_webdriver_executions_using_testng/

You'd need to accept the defined parameters as argument in you test case and then use them.

That is because dataProviders accept object[] as well. You can not use it for matrix data type but it is supported.

so if you have something like this :

this is caused by too old spring-boot-gradle-plugin. It is using property which was removed in Gradle 7. I'm checking the history and you would probably need at least version 2.2.2.RELEASE.

I believe the fix has been done as part of Gradle 6 compatibility (see Release Notes)

I haven't tested that 2.2.2.RELEASE will fix that for sure just guessing based on code changes in the plugin. We are on 2.3.x and that works.

Setup attribute is used to provide a common set of functions that are performed just before each test method is called. You can also get the Method name from TestContext.CurrentContext.Test.MethodName. There are also other properties on Test like Arguments or FullName depending on what you need.

This issue was resolved after I installed Eclipse Oxygen. Turns out it was plugin issue in the eclipse build that I had.