Section 1
- Producing the Right Feedback When Failing
- Summary
- Going headless
- This is where we have been slightly clever
- The plugin runs in the TEST_COMPILE phase by default.
- Downloading the WebDriver binaries automatically
- Let's try it out. First of all, let's check that everything still works like it used to:
- We have then written a couple of new methods.
- There is quite a lot going on here. First of all, we have added some new variables:
- There are no silver bullets
- Opera
- Safari
- Internet Explorer
- Chrome
- Firefox
- Multiple browser support
- There are no silver bullets
- The rst addition to our code is a synchronized list where we can store all our instances of WebDriverThread.
- First of all, we will try and deal with our session problem.
- Let's spin up our test again using the following command:
- This is a small class that will hold a pool of driver objects.
- ext, we need to create a class called DriverFactory.java
- We are going to now build a project structure that looks like this:
- It is important to note that there is no guarantee in which order tests will be run.
- TestNG supports parallel threads out-of-the-box
- Parallel tests with TestNG
- Running your tests in parallel
- Building our test project with Apache Maven
- Making it easy for developers to run tests
- Creating a Fast Feedback Loop