Social and Technical Learnings from A Project

March 2020 GDS Quality Engineering Sharing for Go Business

Two Challenges:
Social Challenge -> Getting people out of silos to take greater ownership of product quality.
Technical Challenge -> Making test code readable, and easy to reuse (by being standardised and thus easy to find) - we use the Flow-Page Object-Data model.

Transcript

1. GoBusiness Sharing GDS Quality Engineering Chapter 5th March 2020 1 git: @sshinnee
2. Contents 1. Challenges We Faced 2. Overcoming Them 3. Things We Learnt 2 git: @sshinnee
3. Challenges 3 git: @sshinnee
4. The Social Challenges 4 git: @sshinnee
5. Siloed Roles 5 git: @sshinnee
6. 6 https://encrypted-tbn0.gstatic.com/images?q=tbn%3AANd9GcSTD4vXieH202pxLsSMcky9ei6Pf-yBI29k-89c3_EUFQgojl01
7. The Technical Challenges 7 git: @sshinnee
8. Low Fidelity E2E 8 git: @sshinnee
9. 9 https://ak7.picdn.net/shutterstock/videos/5015357/thumb/3.jpg
10. 10 git: @sshinnee
11. Challenges A. Siloed Roles a. Slow Feedback b. Weaker Quality B. Patchy End To End a. Difficult to Maintain b. Low Fidelity 11 git: @sshinnee
12. How We Overcame Them: Challenge 1 12 git: @sshinnee
13. A Testing-Centric Approach 13 git: @sshinnee
14. A Testing-Centric Approach A. Test Cases to be written before Development starts B. Developers to do self-testing before it’s Ready For QA C. Anyone can pick up testing of features D. Testing is a team sport 14 git: @sshinnee
15. Test Cases Before Development - Allows us to realize what we don’t understand about the feature - Clarity on target Why? 15 git: @sshinnee
16. Everyone Tests Why? - Greater Ownership over the Product 16 git: @sshinnee
17. How We Overcame Them: Challenge 2 17 git: @sshinnee
18. Less Is More 18 git: @sshinnee
19. Less is More A. Deletion of Unstable Code B. Flows Rather Than Functionality 19 git: @sshinnee
20. badtests.txt 20 git: @sshinnee
21. Flows, not Functions Why? A. Promotes Reusability B. Promote Readability, not Verbosity or Succinctness a. DAMP not DRY 21 git: @sshinnee
22. Data-PO-Flow How? A. Repetition in Flows, not Functions B. Page Objects to mimic Front-End a. promote Application Understanding b. prevent duplicate code C. Have Best Practices for Standardization 22 git: @sshinnee
23. Code Walkthrough 23 git: @sshinnee
24. Best Practices In Code 1. Strict Model 2. Choose a Convention to Prevent Astonishment 24 git: @sshinnee
25. Less is More A. Deletion of Unstable Code B. Flows Rather Than Functionality a. Promoting Reusability b. Promoting Readability, not Verbosity or Succinctness i. DAMP not DRY C. Data - Page Object - Flow Structure a. Repetition in Flows, not Functions b. Page Objects to mimic Front-End, promote Application Understanding, prevent duplicate code i. We can do reuse this way c. Have Best Practices for Standardization 25 git: @sshinnee
26. Learnings A. Testing is a Team Effort B. Quality is a Team Effort C. Testing Pyramid a. Unit, Integration and E2E tests should complement each other b. E2E is expensive and kept to the necessary minimum D. Flow-based Functional Scripts 26 git: @sshinnee
27. People want to reuse, but don’t know what exists already 27 git: @sshinnee
28. Standardization helps people find functions - new users can add code into the existing structure with ease 28 git: @sshinnee
29. Good Quality comes from a sense of ownership from the team 29 git: @sshinnee
30. 30 https://image.freepik.com/free-vector/factory-robotized-production-line-cartoon_1441-3009.jpg
31. 31 https://i.ebayimg.com/00/s/NDA4WDYxMg==/z/Cm8AAOSwAxpdrtEU/$_20.JPG