As teams embrace DevOps, quality becomes a bottleneck for rapid development and delivery. Traditional QA practices of functional testing release candidates are not cutting it in this new era of lightning fast development. Teams are finding that they need to test early and often to rapidly surface error during development to reach continuous delivery. Learn how to implement E2E testing at the earliest stages of development: from initial code commit, to pull requests with ephemeral environments, and high confidence merges. This practice optimizes DevOps software development by enabling developers to solve issues earlier, proactively update tests (so they don’t break later) and become even more productive. Join mabl software engineer Joe Lust to hear how the mabl team puts these ideas into practice daily and how it has benefited their team and product. Additionally, you will learn about: Impact of DevOps on testing Benefits of testing earlier in development Best practices of how mabl does this at mabl

1. The Key to DevOps?
Testing Early in the Pipeline

2. Welcome
Joe Lust
Software Engineer
mabl

3. “Development cycles are getting
shorter and new features are coming
faster than ever…There simply isn’t
enough time to test.”
- Fortune 250 QA Leader

4. DevOps is disrupting software testing
Change happens infrequently
Weeks or months to write tests
Weeks to execute tests
Pre-DevOps
Change is constant
Hours to write tests
Minutes to execute tests
DevOps

5. Outdated testing tools and processes can’t keep up
Testing
Development Ops

6. Poll question
How often does your team deploy?

7. 2
80 releases every week
The new normal

8. Compute requirements
50
scripts
3
scenarios
(average
8
browser
variations
3
targets
3
deploys runs/day
10,800
runs/day
7
mins/run compute hours/day
Tests add up quickly
A simple case - web testing

9. ...But it’s bursty concurrency
Concurrency needed over the course of a day - by test window

10. “While test automation is not new, past automation
approaches have not helped app dev teams keep up with
increased demands of modern delivery.”
- The Forrester WaveTM
for Continuous Functional Test Automation Suites,
Q2 2020

12. The era of intelligent testing is here
12
✔ Tests run in the cloud
✔ Tests are easy to create
✔ Tests adapt seamlessly to change
✔ Tests produce insightful output
✔ Testing solutions are part of CI/CD pipeline

13. Shift-left enables continuous testing
No time for defects and broken tests in DevOps
Code PR Master QA Staging Prod
AttentiontoQuality
Shift-Left Model Traditional Model

14. Benefits to testing earlier in the pipeline

15. The benefits of testing earlier in development
Saving
money
Better team
collaboration
Saving
time

16. Save time and increase test coverage
MaestroQA Case Study

17. Poll question
What do you think the relative cost of a bug in
production is?

18. Relative time and cost to fix bugs throughout development

19. Create a culture of quality
■ Integrated release process
■ Effective communication
■ Joint issue tracking
The value of collaboration?
More efficient teams that move faster.

20. Go to the source: shift quality left
Minimize business impacting bugs by shifting quality testing to the left

21. How mabl does shift-left testing

22. Shift-left workflow with mabl
Local Branch
Environment
Preview
Environment
QA
Environment
Prod
Environment
Proposed Changes Master

23. Shift-left workflow with mabl
Local Branch
Environment
QA
Environment
Prod
Environment
Start testing
here
Preview
Environment

24. mabl CLI (Command Line Interface)
A command-line tool that allows
users to create, edit and run
tests without ever opening
the mabl UI
■ Stay in your workflow
■ Ensure code changes don’t
introduce new issues

25. Branching
Branches helps users make
isolated changes to a test without
affecting the master version of
that test.
■ Version control
■ Ensure your changes work
■ Snapshotting

26. Headless runner
As part of the mabl CLI, it allows users
to easily run and debug tests on their
local machine, including support for
headless mode
■ Get lightning fast feedback
■ Save time while reducing risk
■ These local tests are FREE to run

27. Jest unit test runner
Write mabl UI tests as standard
Javascript/Typescript unit tests
■ Run mabl tests w/ your unit tests
■ Easily run from your IDE
■ Store test setup in source control

28. Shift-left workflow with mabl
Local Branch
Environment
Preview
Environment
Test here
QA
Environment
Prod
Environment

29. Preview environments
■ On demand, short live environments
■ Used to validate changes and deployments
■ No/minimal impact if broken
▲ Single use
■ Also known as:
▲ Review app
▲ Ephemeral environments

30. Harness Your Preview Environments
■ Run your end to end automation against the preview
■ Link your merge requests to the preview
■ Test merges to main before you merge

31. 31#GitLabCommit
Slide option 1 of 2
This seems like a
completely innocuous
MR, especially if you
don’t speak CSS.

32. 32#GitLabCommit
Slide option 1 of 2
But what if we could
SEE the changes in a
Preview Environment?

33. 33#GitLabCommit
Slide option 1 of 2
Oh, no! This certainly
isn’t what I meant to
approve!

34. Shift-left workflow with mabl
Local Branch
Environment
Preview
Environment
QA
Environment
Prod
Environment
Test here
Proposed Changes Master
Test here

35. Test early.
Test often.
Test everywhere.

36. Intelligent Test Automation for Your
Entire Team
Reliable Tests:
Easily create and maintain
automated UI tests
Unified Platform:
Increase test coverage across
your applications with a single
platform
Comprehensive Results:
Gain actionable insights across
the entire development lifecycle
Customer-Centric Testing:
Create end-to-end tests from
your end user’s perspective

37. Questions?
Learn more at mabl.com