We know that most organizations today are integrating at least some test automation into their CI/CD pipelines. Most start with unit testing – which, while a great place to start, can't give you the level of confidence you need to safely deploy into production.
In this webinar, we'll talk about what other types of testing you should be integrating into the CI/CD pipeline to make test automation more valuable – as well as how to develop an integrated approach using Agile test management. We'll also share best practices for avoiding some of the most common anti-patterns we've identified that make it difficult to scale beyond the unit level. You will learn:
How to get more value out of test automation and minimize the number of defects identified late in the delivery cycle
How to avoid common anti-patterns related to collaboration, test data management, testing in the cloud and more
Best practices for scaling and managing test automation across a diverse toolset using Agile test management
8. The #1 barrier to DevOps transformation
8
What impedes the delivery
of innovative software?
Source: Gitlab, Global Developer Report, 2019
9. Common Pitfalls
9
a. Testing gets squeezed
b. Test Data gets too little thought
c. Selecting the right technique
d. Testing cloud-native architecture
e. Automation hits a glass ceiling
10. Testing gets squeezed
10
Agile teams need to make testing a priority in order to optimize their pipeline. A strong
handle on testing allows for fast feedback loops, quick safe releases and ultimately
more throughput.
11. Test Data gets too little thought
11
Production Data is good for many things, but it can also be a real hindrance for testing.
Create or alter data and systems to allow for more efficient testing. Powerful ways to
shape data the way your test requires maximizes your automation potential and
increases your coverage for edge cases.
12. Selecting the right technique
12
The right blend of testing techniques is key. While automation is very important, exploratory testing and
different automation ideas (unit-, regression-, integration, acceptance) via different entry points (Code,
API, UI) need to be carefully considered and applied.
13. Testing cloud-native architecture
13
Cloud native demands a new kind of tests. Infrastructure properties like elasticity are essential to
provide a service and therefore former non-functional tests like load tests become functional.
14. Automation hits a glass ceiling
14
Automation can get extensive in favor of minimizing manual pipeline holdups. Assessing automation
inventory frequently and syncing it with application functionality is critical (e.g. BDD).
Parallel/Multithreaded automation and environment management is a must to reduce duration.
16. 16
• Seamless agile testing by providing manual
and automated test traceability to Jira issues,
bugs, and releases in real-time.
• Shift quality left with open source and
commercial test automation management, test
script scheduling, and support for BDD.
• Power Agile and DevOps workflows through
out-of-the-box integrations with the most
popular development tools (e.g. Jenkins,
Bamboo).
Agile Test Management Tricentis qTest