Archives

This track includes topics related to test automation architecture, continuous integration, agile automation, and what other tasks you need to perform after you have designed your framework and scripted your test cases.

Track Talk: How to Get Automation Included in Your Definition of Done

While most teams appreciate the benefits of automation, it is commonly viewed as too time-consuming to be considered as part of an agile sprint; resulting in automation being done in isolation and typically months after the story has been closed. This can lead to several problems including automation team members being disengaged and missing key […]

Workshop: Cypress 101 – JavaScript Test Automation

Cypress, a JavaScript end-to-end test automation tool, has generated a lot of buzz recently. Many developers prefer Cypress over other test automation tools because of its speed, convenience, and ease of use. In this workshop, we’ll use Cypress to create automated tests. In writing these tests, you’ll learn how to use Cypress to interact with […]

Track Talk: BDD + Gherking – BDD = Happiness

Organizational impacts from DSL (Domain Specific Language) test automation. What if I told you that technology could make your life better, and make you happier. During this talk, I’ll share experiences across different companies of different sizes across various industries. Go over the effects of introducing Gherkin based testing (not BDD), what changed, and what […]

Track Talk: The Automation Firehose – Be Strategic and Tactical

The widespread adoption of test automation has led to numerous challenges that range from development lifecycle integration to simple scripting strategy. Just because a scenario CAN be automated does not mean it SHOULD be automated. Teams that adopt automation often rush to automate everything they can — the automation firehose. For those scenarios that should […]

Track Talk: Designing Your Test to Fail

It’s a fact of life that we often have to write automated UI tests for features that have defects, or that interact with 3rd party APIs that aren’t returning the right responses, or for items that we know aren’t working right. When the team has decided that the behavior isn’t going to be fixed, what’s […]