The document discusses various automation testing tools and strategies for testing monolithic and microservice architectures. It provides an overview of tools like Selenium, Cypress, JMeter, and Nightwatch and compares their capabilities for front-end and back-end testing, maintainability, and integration with continuous integration pipelines. It also discusses best practices for testing microservice architectures like testing services independently, using contracts, and embracing an iterative approach.

1. My slides are / will be available for you at:
AutoFails
Shekhar Ramphal

3. Getting from A to B
Quality software and to Production
The journey

4. Maintainability / Scalability / Reusability / Readability …
Cross browser
Visual compares
Mobile compatibility
Functional tests
User experience
Backend access (APIs / Web services / DBs)
CI / Scheduled
Reporting
Automation framework buzz words

5. Swiss army knife
All in one
Tooling

6. Licensing
Limited users
Setup overhead
Support limited to provider
Front end
Slow
Record playback
Versioning?
CI?
QTP

7. Record playback
Expert to keep up maintenance
Customizing
Free
Slow
Firefox limited
CI?
Selenium IDE

8. Selenium webdriver
Readable code by scenario
Ruby
BDD?
Free
Expert to debug and maintain
Back end calls
Slow
CI integration
Capybara / cucumber

9. Browser why?
Record playback? unusable
Expert to debug and maintain
Raw HTTP requests
Super fast
Optimized parallelization
CI integration
Jmeter

10. Free - Selenium webdriver setup
POM model
Parallel testing
Quick onboarding
Easy configuration
Easy maintained
JS code
Slow
CI integration
Nightwatch JS

11. Testability
Monoliths
100 problems in 1 place
Microservice
1 problem in 100 places
Each with own challenges
What’s the right choice?

12. Unit testing (lots of it)
Test micro services as a standalone product
Mocked dependencies
Environment verification
Smoke testing in selenium
API integration tests
Sync
Async
Bottom up approach

13. Testable pieces
As granular as possible
How micro is a microservice?
Understand dependencies and integration points
Design and adhere to contracts
Rigid standards
Split the application

14. Does one thing well
Pick your battles
Low hanging fruit
Embrace change (long / short goals)
Data control
Confidence
Upskill and implement
Tool for the job

15. Testers access to code
Devs access to testcases
Automation lives close to app code
Everyone tests
Everyone codes
Everyone automates
Value is in the testcases
Take away