Soumya Mukherjee started their career as a developer and then moved to QA. They love working on complex problems and are the creator of multiple QA products and author of automation books. They are also a co-founder of consulting, product, and certification companies and have led large QA transformations. Their expertise includes reducing QA cycle time and release engineering.

1. Fail to Rise
Automation & DevOps Stories
Soumya Mukherjee

2. Started my career as a Developer and then moved to QA
Love to work on complex problem statements
Creator of multiple QA products
Author of couple of automation books
Co-founder of a consulting company, product company & a certification company
Lead large QA transformation programs in investment banks
Expertise in reducing QA cycle time & Release Engineering
Loves to work for the Community & Open Source projects
Father of a lovely Daughter
About me
You can reach me on
bit.ly/twsoumya
bit.ly/lnsoumya

3. All my stories are linked with the
Delivery & Learning associated
with it

4. Java was my
primary coding
language but the
first production
level job was in
.NET

5. Continuous Learning

6. Exhaustive
Testdata was
prepared for all
combinations of
fields in the
application

7. Optimal Test Data
(test your field atleast once)

8. Poor code
coverage

9. Most of the production defects
come because of your uncovered
code
(Code instrumentation)

10. Automation
Scripts are only
executed in Local

11. Entire pack should run once a
week to ascertain stability
(scripts that runs always on local
are flaky)

12. In organizations
each team make
their own
framework
(tightly coupled)

13. Abstract Framework from
Implementation

14. In organizations
each team use
different tool for
automation

15. Standardize Tools & Frameworks
(end to end run)

16. No idea who all
are creating &
executing the test
scripts
(multiple browsers / platforms)

17. Central Logging & Reporting

18. 1000 API tests
run 4 hours OR
1000 UI tests run
for 2 days
(multiple browsers / platforms)

19. Classic Problem - Scaling
Distribution of tests across containers, Dependency Management

20. Sequential
execution of tests
in the pipeline
(Api, UI, Perf, Security)

21. Parallelism Problem
No one stops to parallelize
Intelligent probes & checks are
required to manage pipeline

22. High build time
of the project
(45 min build/commit)

23. Build the code in chunks
Don't compile the pre-compiled

24. Building
containers each
time, porting the
code & store the
containers in
ECR

25. Underlying container not
changing deploy in the same
container (IAC)

26. No
Containerization
&
Headless
execution

27. Containerization save system
resources
&
Headless execution are faster

28. Thank you
bit.ly/twsoumya
bit.ly/lnsoumya