Before creating the web tests, I used the Selenium library, implemented the Page Object Model, utilized stable x-paths, and adhered to Java best practices to enhance readability and maintenance. Once I was finished, I tried to determine what test cases were WORTH automating. I took into consideration what features were the most used or important. The most important for this project were the features that impeded a user from login or logout. Therefore, those features required to be tested the most and ensure that they worked after every update. Automating the testing for these features would save time for engineers and improve quality.

Finally, I was able to start creating web tests using TestNG. As depicted in the images to the right, I included annotations on my web tests for descriptions, tags, data providers, and linking test cases. The descriptions provide details about each test and the tags are used for grouping tests to create test suites such as Regression testing. The test cases inside Zebrunner (test management system) have a unique ID which was necessary to link the tests and provide better traceability. Also, you will notice that a few tests have data providers to execute the same test but with different data.

Each test employs either a hard or soft assert to validate various aspects of a page, whether it involves confirming the correct alert message or detecting an incorrect title. I intended to create tests that simulate or follow the same steps that a user would take.