The document summarizes best practices for test automation, including: - Unit tests should be automated as the first step and follow naming conventions. - Integration and performance tests require grouping, isolation, and handling test data issues. - UI tests can be automated with Selenium and integrated into the build pipeline. - Automated test data, code, and plan generation may be useful once a project's structure stabilizes. - Automation aims to provide transparency, improve skills, and reduce manual work over time through a smarter approach.

1. Hien Nguyen @AgileVietnam #MonthlyMeetup Aug 2015

2. § Agile testing manifesto
§ Our project & approach
§ Automation test with continous integration
§ Pitfalls & best practices
2

4. 4

5. Collaborative ownership
Detached objectivity
Targeted automation
Widespread anti-regression
Defect prevention
Defect detection
Exploratory testing
Predetermined scripting
over
5Source: Anand Bagmar – ThoughtWorks

6. Connect
with 3rd
party
systems
Internal
use
Tool
(Website)
6

7. test, test,test…
Automate as most as possible
TEAM responsibility for BUILT-IN quality
7

8. less repeatable works =
more VALUE
Testing mindset trainer
Test plan & execution
manager
Rollout gateway
8

9. Automation
Deployment
Integration
Test
9

10. Unit
• Single
module
Integration
• Cross
modules
• Contact data
layer
Performance
• Scalable
environment
UI
• Simple UI
operations
10

11. 11Source: ThoughtWorks

12. § MUST HAVE & first step in automation testing chain
§ Best practices:
§ Naming convention
§ Batch
12

13. § Best practices
§ Grouping
§ Isolation
§ Keep it simple
§ Issues: Test data
§ Pre-defined data
§ Generated data
13

14. § Best practices
§ Test scripts under source control
§ Solution:
§ Octopus deployment
§ Website:IIS
§ Clients as run-once Windows service à invoke Jmeter
§ Scalable clients with Hyper-V
§ Trigger:
§ After integration test
§ Deployment
§ Test server
§ Clients
14

15. 15
Hyper-V
TeamCity Octopus
pull
deploy

16. § Best practices:
§ Keep it simple
§ Not (too) complex test case
§ Naming convention
§ Solution:
§ Selenium test code
§ Integrate to build pipeline
16

17. § Automated test data / code / plan.. generation?
§ Indication:
§ When project’s structure is being stable for some sprints
§ Modules’ structures look similar
§ Test code structures look similar
§ But please careful
§ We need manual works to maintain the automated works
§ Today it reduces work but tomorrow…
17

19. Our objectives
§ Transparent: Team can real-time know project status
§ Improvement: Team can improve mindset and (testing, coding) skills
§ Fewer manual works, fewer people, fewer breaks…by smarter way J
19

20. § Cost reduction, ROI increase
§ No longer or not frequently maintain needs
§ (Too) love UI or system tests
§ Only QA responsibility for automation test
20

21. Need
• objectives
• team
Implement
• as soon as
possible
• more unit test,
less UI test
• team
Continuous
• refactor
• execute
Don’t
• need to test
everything
• worry to
disable tests
SOMETIMES
Remember
• You have
MANUAL
works for
AUTOMATED
works
• Trade-off
21

22. Automation test is not a tool that let us work from Monday to Thursday and let the
machine do repeatable works in Friday. It’s a method to let us work from Monday to
Friday safety by knowing our issues and preventing bugs everyday.
We have to do the manual works for automated test, includes the testing for it. So
more automated testing could be done, more manual work need to be done.
The total cost usually doesn’t change. But whenever we want to execute large set of
test cases in a short time, we can – that we normally cannot do by using people.
22

23. § We are hiring a tester for mobile team @Planday
23

24. 24

25. 25
Certified ScrumMaster®
September 21-22, 2015
Hanoi
Certified Scrum Product Owner®
September 21-22, 2015
Ho Chi Minh city