𝗧𝗲𝘀𝘁 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝗣𝘆𝗿𝗮𝗺𝗶𝗱

This deck was shared in MoT Kuala Lumpur's Meetup #7 on 13th October 2020

𝗔𝗯𝘀𝘁𝗿𝗮𝗰𝘁 𝗼𝗻 "𝗧𝗲𝘀𝘁 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝗣𝘆𝗿𝗮𝗺𝗶𝗱":

Test automation is not something new and has been around for about 20+ years. To get the best out of automated tests for software, there is one key concept - the 𝘁𝗲𝘀𝘁 𝗽𝘆𝗿𝗮𝗺𝗶𝗱. It's a great visual metaphor that depicts different layers of testing and tells us how much testing needs to be applied to each layer.

𝗔𝗯𝗼𝘂𝘁 𝗦𝗽𝗲𝗮𝗸𝗲𝗿:
Pooventhan Supramaniam [QA Test Automation Lead at Appspace]

Pooventhan is an experienced automation tester. Driven by repetitive manual and mundane test efforts, he takes pride in providing the practical approach for complex product testing. As a QA Test Automation Practice Lead in Appspace, his goals include providing extensible automation infrastructure and working closely with QA team members to automate the execution and verification of software products.

Transcript

1. Test Automation Pyramid MoT KL Meetup #7 Speaker: Pooventhan Supramaniam
2. Introduction • As software application undergoes constant changes, testing effort increases. • Test automation introduced and getting common in industries. • ONE key concept to be successful in automation. “Test Pyramid” 2
3. The Pyramid More isolation, runs faster More integration, runs slower 3
4. The Sample Application (High-level structure) 4
5. The Sample Application (Internal structure) 5
6. Unit Tests • Foundation – can range from a single method to an entire class. • Making use of test doubles – mocks and stubs. • Test all public interfaces of a class. • Consider Test Driven Development (TDD). 6
7. Integration Tests • Tests integration of application with all the parts that live outside of application. • Requires actual instance of dependencies to be tested with. Hence, aim to run external dependencies locally. For example: • Local databases • Storage Emulators • Tends to be slower than unit tests and harder to write due to: • More moving parts • Spin up and data preparation • Advantage of giving confidence that application can correctly work with all the external parts. 7
8. End-to-End (E2E) Tests • Verifying application behaviour as a whole. • Tested with deployed instance of services to verify production readiness. • Tends to be slow and flaky. • Testing high-value user interaction with the application (and strictly not for all sorts of edge cases) 8
9. Considerations • Aim to run the automated tests in continuous integration/ continuous delivery pipelines for fast feedback loop. • Try to avoid duplicated tests and consider pushing tests down the pyramid when possible. • Write clean test code. It is as important as production code. 9
10. References • https://martinfowler.com/articles/practical-test-pyramid.html • https://medium.com/@Colin_But/define-testing-strategy-using-the-testing-pyramid- 1dabee37e823 • https://www.browserstack.com/guide/testing-pyramid-for-test-automation 10