Test Automation Framework (Selenium with Java) — Minority Report or Allure in Action
--
S01E11 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)
S01E09 — Code Review and Refactoring (Part 1)
S01E10 — Code Review and Refactoring (Part 2)
In the last episode, we’ve finally finished writing our client-side tests. We covered some complex stuff, like Builder Design Pattern, Rest Assured, or Lombok (learn more: S01E10), we have implemented a simple database connector using the JDBC (learn more: S01E08). It seems like we’re prepared for whatever developers will throw at us.
But, there’s a catch — we have automated Test Cases, but the execution still has to be performed manually, and that’s not how it’s supposed to be.
Before jumping straight into implementing our Test Suite into so-called Continous Integration, we have to prepare some kind of a reporting utility, so that we can monitor the execution of our tests and report the results to the development team and “management people”.
Allure is a no-brainer, at least for me, when it comes to end-to-end test automation reporting. It provides a pretty dashboard, and what’s more important — it’s extremely easy to implement.
