This chapter concluded the framework design discussion on how to encapsulate and use test data. The premise of data-driven testing is to store data outside the Selenium page object and test classes. Again, this does in effect reduce the amount of maintenance and code that needs to be written to test a specific feature, by reusing test methods with varied data.
We also covered topics such as positive, negative, boundary, limit testing, dual-drive support, and parallel testing; all extremely important standards to incorporate in a Selenium framework.
In the next chapter, the Selenium Grid Architecture will be discussed and users will design and build a local in-house grid to run the testing on, taking the framework from a local testing platform to a remote testing platform. This will lead the way to using third-party grid platforms such as the Sauce Labs Cloud.
...