The document discusses considerations for web testing with Selenium such as things that can be tested versus things that should be tested. It also covers antipatterns to avoid like manual configuration and deployment. The Java ecosystem for testing is presented including tools like Gradle, Cucumber, and AssertJ. Basic design patterns like Page Object and dependency injection are introduced. The document concludes with wrapping up best practices for Selenium tests like productive code and correct implementation of the Page Object pattern.

1. www.spanishtestacademy.co

2. www.spanishtestacademy.co
Web testing with Selenium
Sergio Sacristán

3. www.spanishtestacademy.co
Automated test considerations

4. www.spanishtestacademy.co
Selenium
“The things that we can do”
vs
“The things that we should do”

5. www.spanishtestacademy.co
Selenium
“Component testing”
vs
“Functional testing”

6. www.spanishtestacademy.co
Antipatterns
• Manual configuration
• Manual deployment
• Manual-testing-design
• Micro-testing-design
• Duplicate testing?

7. www.spanishtestacademy.co
Java Ecosystem
• Gradle
• Cucumber
• Config Typesafe
• Serenity / Selenide / Allure …
• AssertJ

8. www.spanishtestacademy.co
Basic design patterns
• Data-Builder
• Page Object
• Facade
• IoC

9. www.spanishtestacademy.co
The code
https://github.com/s2oBCN/test-academy-selenium

10. www.spanishtestacademy.co
To wrap up
• Productive code
• Incremental complexity
• Logs / reports
• Correct implementation of Page Object.

11. www.spanishtestacademy.co
Thanks!
• Questions?