It is important to keep static utilities separate from the Selenium page object and test classes. This reduces duplicate code, allows users to maintain the framework utilities in a central location, and provides all users who use the framework for testing with a set of classes they can readily include in their tests.

The synchronization class is what makes the framework robust. If users do not synchronize the scripts, they will become unreliable, failing on different browsers, mobile devices, and platforms.

The test listeners, reporters, and image capture utilities provide a built-in mechanism for the framework to report the test results of suite runs. Users only have to include these classes in their test or suite file, and they automatically get TestNG results in the console, log, and HTML report formats.

Now that the Selenium driver and utility classes are built, it is time to talk about the Selenium page object classes. The next chapter will take a deep dive into that topic.