How to use setParameters method of org.testng.Interface ITestResult class

There is no correspondence between TestNG @Test annotation and your completable future. The problem is in your tast.get() method. It should be blocking running threads until all completable futures are finished.

I use Completable Future in my tests and never ever I ever got into a problem with TestNG.

The problem is one of your future's finishes, and you return to the test method instead of waiting for all the futures. You should combine all your futures with thenApplyAsync() or compose() because your Future is final you are waiting only for one future. Plus you should not use CompletbleFuture.Any() because it returns to execution when the first future is complete.

Just delete the automatically created TestNG Run/Debug Configuration (Run | Edit Configurations... action) in Run Configurations dialog for the project. Then you will again have the option to choose test framework.

UPD: Since 2017.3 version there is suggest.all.run.configurations.from.context property which you can set (Help | Edit Custom Properties action) to true, then IDE will show you all the configurations that are available for current context.

There's a difinition for @BeforeClass :

@BeforeClass
Run before all the tests in a class

And @FindBy is "executed" each time that you'll call the class.

Actually your @FindBy is called before the @BeforeClass so it won't work.

What i can suggest to you is to keep the @FindBy but let's start to use the PageObject pattern.

You keep your test's page and you create another class for your objects like :

public class PageObject{
  @FindBy(id = "j_idt5:nome")
  private WebElement inputNome;

  @FindBy(id = "j_idt5:idade")
  private WebElement inputIdade;

  // getters
  public WebElement getInputNome(){
    return inputNome;
  }

  public WebElement getInputIdade(){
    return inputIdade;
  }

  // add some tools for your objects like wait etc
} 

Your SeleniumTest'll looks like that :

@Page
PageObject testpage;

@Test(priority = 0)
public void digitarTexto() {

  WebElement inputNome = testpage.getInputNome();
  WebElement inputIdade = testpage.getInputIdade();

  inputNome.sendKeys("Diego");
  inputIdade.sendKeys("29");
}
// etc

If you're going to use this tell me what's up.

Disclaimer: I'm a TestNG contributor.

We replaced Maven by Gradle some releases ago, and we didn't find a way to define optional dependencies. Now it should be fixed since: https://github.com/cbeust/testng/pull/844

That explains why, with some releases, you can see JUnit as direct dependency of TestNG. But it is not the expected behavior and you can exclude it from the classpath without problem (if you don't need it to run some JUnit tests).

The static metamodel classes are populated when hibernate is loaded. So, either you configure hibernate context in your test or you populate the attributes manually before the method execution. In you code, you could do:

@Test
public void doIt() {
    BookingSystem_.code = new SingularAttributeMock<BookingSystem, Integer>();
    bookingService.saveBooking(booking);
  }
}

The class SingularAttributeMock can be created custom-made in order to use it in your tests. You can also use any other implementation of the SingularAttribute class.

public class SingularAttributeMock<X, Y> implements SingularAttribute<X, Y> {
   //Overriding methods of SingularAttribute...
}

Like you said, just use this flag to turn off the default reports. The exact name depends on whether you're using the command line, ant or maven. Look this string up in the documentation that is relevant to you.

You need to make the following changes.

The reason being, driver is not in the scope of validuserpass test.

Define WebDriver driver at class level i.e., before the setup method.

public class FirstTestNGFile {
   WebDriver driver;

   @BeforeTest
   public void setup() {
      driver = new ChromeDriver();
      //Add the remaining statements as it is

   }

   //Add your test methods as it is


}

Easiest solution would be, add the below lines in surefire plugin.

<suiteXmlFiles>
    <!-- pass testng.xml files as argument from command line -->
    <suiteXmlFile>${suiteXmlFile}</suiteXmlFile>
</suiteXmlFiles>

And run your xml file as below,

mvn clean test -Dsurefire.suiteXmlFiles=/path/to/testng.xml

Yup, there is a nice way to do the same test over and over again, just with some other dataset. The solution is "@RunWith(Parameterized.class)" - link to javadoc. I'm assuming you're using JUnit 4 - but TestNG also has such functionality from what I remember.

The code you'll need to write will look somewhat like this:

 @RunWith(Parameterized.class)
 public class FibonacciTest {
        @Parameters
        public static Collection<Object[]> data() {
                return Arrays.asList(new Object[][] {
                                Fibonacci,
                                { { 0, 0 }, { 1, 1 }, { 2, 1 }, { 3, 2 }, { 4, 3 }, { 5, 5 },
                                                { 6, 8 } } });
        }

        private int fInput;

        private int fExpected;

        public FibonacciTest(int input, int expected) {
                fInput= input;
                fExpected= expected;
        }

        @Test
        public void test(@HeresHowYouGetValue Type value) {
                assertAnswerKey(new Object[][] {
                                Fibonacci,
                                { { 0, 0 }, { 1, 1 }, { 2, 1 }, { 3, 2 }, { 4, 3 }, { 5, 5 },
                                                { 6, 8 } } });
                assertEquals(fExpected, Fibonacci.compute(fInput));
        }
 }