“As we embrace faster release cycles, testing has become a bottleneck. Yes, we have embraced automation as the way forward. We have a huge regression suite and therefore a big backlog for automation, a tough balance to speed up and yet maintain the fast paced release rhythm. What can I do?” Automated tests are great to monitor a system’s health. Rather than just use regression as the candidate for automation, key flows that signify the pulse of a system's health are superior, don’t you think? And, this won’t create a huge backlog for automation, right? Most often I have seen automation embraced as the solution to speed up testing. Conceptually correct it is, the problem is - what makes it worth the while to automate? Automated tests have to be in sync with the product and are therefore not a one time effort. Choosing the right ones implies, it needs to be at the level of user flow, and be a clear indicator of health. Unless test scenarios are well structured and organised, choosing the right ones will turn out to be difficult, and ultimately weigh you down. It then becomes a pursuit of catching up with automation rather than making it work for you. The goal is not 100% automation, it really is no leakage of defects. Automated tests are really ‘checks’ that assess key paths for good health (correctness) while intelligent human tests are focused on finding issues(robustness). A harmonious balance between these two enables clean code to be delivered without being weighed down by automation. If you are “weighed down by automation“, then you may find our SmartQA consulting (stagsoftware.com/smartqa) interesting, where we unshackle your practice so that you can exploit technology.

1. 1

2. "Testing seems to be a bottleneck to faster release cycles.
We have embraced automation,
our huge regression suite is a big backlog now.
It is tough to speed up and keep up with release rhythm.
What can I do?”
asked a Senior Engineering Manager

3. 3
Do you have a large regression suite?
Is it weighing down your QA automation?

4. 4
PRODUCT
backlog
This drives our business,
constantly increases.
Let us take a look at the BACKLOGs

5. 5
PRODUCT
backlog
TECH DEBT
backlog
This drives our business,
constantly increases.
This happens,
we strive to reduce.
Let us take a look at the BACKLOGs

6. 6
PRODUCT
backlog
TECH DEBT
backlog
AUTOMATION
backlog
This drives our business,
constantly increases.
This happens,
we strive to reduce.
Certainly, we don’t
need this one!
Let us take a look at the BACKLOGs

7. 7
To assess good health
we check key parameters of
various body systems
periodically.
So what can we do? Let us turn to Biology.

8. 8
Assess
(1) Health of system
(2) Impact of change
Applying this idea to a software system
FUNCTIONALITY PERFORMANCE MIGRATION …
SYSTEM
To assess specific aspects
periodically, we automate.

9. 9
Assess
(1) Health of system
(2) Impact of change
Applying this idea to a software system
Basic health first, then impact of change
FUNCTIONALITY PERFORMANCE MIGRATION …
SYSTEM
To assess specific aspects
periodically, we automate.

10. Weighed down by automation?
Automate these first.
SYSTEM(QA) TEST SCENARIOS
indicates pulse
of GOOD HEALTH
1
assess impact
of CHANGE (REGRESSION)
2
Then automate these.
look for issues in
areas/aspects
3

11. Weighed down by automation?
Automate these first.
SYSTEM(QA) TEST SCENARIOS
indicates pulse
of GOOD HEALTH
1
assess impact
of CHANGE (REGRESSION)
2
Then automate these.
look for issues in
areas/aspects
3
Architect and organise scenarios well,
to choose key flows by (1) & (2) for specific aspects.

12. Weighed down by automation?
Do heavy lifting, smartly.
Automate these first.
SYSTEM(QA) TEST SCENARIOS
indicates pulse
of GOOD HEALTH
1
assess impact
of CHANGE (REGRESSION)
2
Then automate these.
look for issues in
areas/aspects
3
Architect and organise scenarios well,
to choose key flows by (1) & (2) for specific aspects.

13. It is not a pursuit of catching up with automation,
rather it is making it work for you.

14. Goal is not 100% automation,
it really is no leakage of defects.
It is not a pursuit of catching up with automation,
rather it is making it work for you.

15. Goal is not 100% automation,
it really is no leakage of defects.
Automated tests check for health(correctness),
while human test looks for issues(robustness).
Balance both harmoniously.
It is not a pursuit of catching up with automation,
rather it is making it work for you.

16. stagsoftware.com
Home of SmartQA.
Do LESS.Accomplish MORE.
Brilliant thinking, diligent action and adept tooling
to deliver clean code rapidly and cost effectively.
Check out our SmartQA Practice consulting.
stagsoftware.com/smartqa
“Weighed down by automation?”
Unshackle your practice so that you can exploit technology.