Test Automation Framework (Selenium with Java) — Awakening or the First Selenium Test Case

S01E03 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.

S01E01 — What To Automate?

S01E02 — Test Automation Environment and Tools

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)

S01E11 — Allure in Action

First of all — what is Maven? Referring to the official website:

Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project’s build, reporting and documentation from a central piece of information.

What does it mean in reality? It’s a one-file — pom.xml — that makes it simple to build your project (which means your app’s version, title, description, dependencies, and their versions, etc.).

So, for instance — you are the new employee at the Hoax Company Inc., and you’re onboarding. Despite all the coaching, safety training, and bureaucracy — you need to set up the Java Test Project to start providing value to your company.

You’ve got your brand new MacBook and your buddy (a person designated to personally take care of the new employee’s onboarding) tells you that you have to install all the 100 *.jar files that are being used to run the Java Test Project. Also, there are…