Test Automation Framework (Selenium with Java) — Fear or Code Review and Refactoring (Part 1)
--
S01E09 of the Test Automation Framework series about everything you’ll need to set up the nice, simple, yet sophisticated framework.
Covered with clear explanations and pretty illustrations.
Sounds like fun? Cool. Now, please, fasten your seatbelts because you’re here for a ride.
S01E02 — Test Automation Environment and Tools
S01E03 — The First Selenium Test Case
S01E04 — Selenium Foundations Revisited
S01E05 — Page Factory and Elements Related Exceptions
S01E06 — Page Loading Strategies and Waits
S01E07 — Translating JIRA with Selenide (with Exercises)
S01E08 — JIRA, Selenide, Complex SQL, Java Objects with Equals & HashCode (with Exercises)
S01E10 — Code Review and Refactoring (Part 2)
In the previous episode, we’ve finished writing Test Cases for JIRA tickets (credentials to access the JIRA board can be found in the S01E07 — Translating JIRA to Selenide section).
If you couldn’t come up with your solution for the Test Cases, or you’d like to follow the Test Automation Framework tutorial from this episode — feel free to clone the GitHub repository with the code from here: https://github.com/n4bik/test-automation-framework/tree/Magic-ClientTest
In the real world after writing each Test Case you’d commit your changes and push them into a specific git branch. After that, you’d most probably create a Pull Request (if you’re using GitLab) or a Merge Request (if you’re using GitHub) to proceed with merging your code branch to the master/develop (depends on your company’s policies/practices).
