30-minute Talk

Writing your first automated check is easy, but it takes effort to make them clean and maintainable

Timetable

12:03 p.m. – 12:03 p.m. Thursday 24th

Audience

Automation engineers who have some experience Testers who want to start automation

Key-Learning

  • Why some checks are more flaky than others
  • How an architecture can help you
  • What kind of architectural decissions you can make
  • How to build a layered architecture
  • What common design pattern exist

Testing is nowadays a crucial part of software development, but if it comes to
good programming practices a lot of teams have some issues to create
sustainable and maintainable tests. Learning the usage of a testing tool is
often not enough for writing those. It is also necessary to create a framework
which abstracts the different concerns.

This talk I want to speak about how a person responsible for automated checks
can create a maintainable and scalable architecture. I will introduce different
patterns which are commonly used in the industry. I am going to explain the
implementation of the page Object pattern and the repository provider pattern
and how you can create a simple DSL which is used in your tests in order to
keep them clean and readable. My examples will be in Java and Espresso, but the
structure is portable for various other solutions like Selenium and Appium.

Related Sessions