Typically, different software testing methods and techniques are applied to fully test a project. Ad-hoc testing, which is characterized as testing with no explicit planning, test designs, or documented test cases, is one of the most widely-used methods in agile projects. Automation testing uses software tools to perform or support test activities such as management, test design, test execution and results checking. Automation testing can be effectively applied to repetitive necessary tasks in a formalized testing process or other tests that are difficult to execute manually. This presentation introduces a strategy by combining these testing approaches to improve the effectiveness of software testing.

1. STC JULY 2014
HOA LE
Apply Automation once
Executing Ad-Hoc Testing

2. Agenda
Ad-hoc Testing
Automation Testing
Apply Automation
once executing Ad-
hoc testing
2

3. What does Ad-hoc Testing
mean?
No Explicit Planning
No Test Design
No Test Case
3

4. When we use it
4
• Limited time
• Supplement to formal tests
• Team having strong product
experience

5. Benefits of Ad-hoc Testing
5
• Find more bugs
• Cover areas where there are lack of test
cases
• Increase confidence software of
product

6. Forms of Ad-hoc Testing
Buddy Testing
6
Pair Testing
Monkey Testing

7. To be Ad-hoc Testing effectively
7
• Have good domain knowledge
• Have good test strategy
• Have good tools

8. Agenda
Ad-hoc Testing
Automation
Testing
Apply Automation
once executing Ad-
hoc testing
8

9. Automation Testing
“Automation testing is the use of tools or
software to perform or support test activities
(management, test design, test execution and
results checking)”
• Characteristics:
 Reliable
 Reusable
 Repeatable
9

10. When we use it
10
• Limited time
• Reuse scripts for large amount of
data
• Execute after function/modules is
stable

11. Benefits of Automation
Testing
11
• Increase coverage
• More powerful and versatile
• Execute performance and load test
easily

12. Common test Automation
Frameworks
12

13. What do we need to have?
 Good programing skills
 Ability to define important data
 Ability to analyze report
13

14. Agenda
Ad-hoc Testing
Automation Testing
Apply Automation
once executing Ad-
hoc testing
14

15. Case Study - A
15
ffgh
Situation: Execute Ad-hoc testing for purchasing some
devices on the web-ecommerce with some steps as
below:
1. Search devices (automation)
2. Selected some devices to order them (automation)
3. Display selected devices successfully (automation)
4. Delete them in database (manual)
5. Research them in site(manual)

16. Case Study - B
16
ffgh
Another Situation: Ad-hoc testing for view the color of
car in cars purchasing website.
1. Search a car (automation)
2. View car information (automation)
3. Change the color for car (360 degree view function in
flash) (automation)
4. Verify whether the color is displayed correctly
(manual)

17. Benefits
 Execute many scenarios in a short time
 Execute scripts on multiple-browsers and
multiple-platforms
 Get the right log for reporting
17

18. Advantages
18
Speed up test cycle
Utilize available test cases and test suites
Increase test coverage
Utilize current automation
framework
Support regression team

19. Disadvantages
19
Take time to debug
Analyze incorrectly report
Be dependent on automation factors

20. Challenges
20
Need programing skills
Need in-depth knowledge of the system
under test
Need strong framework
Need clearly workflow process
Need strong testing skills

21. 21

22. Important Notes
22
• More tasks in each test cycles
• More test coverage criteria
• Have a framework for automation

23. 23

24. References
24
Sathyan Sethu Madhavan, “A Guide For Test Automation”, 19
March 2012
(http://www.thoughtworks.com/insights/articles/guide-test-
automation)
Linda G. Hayes, “The Automated Testing Handbook”, March 1,
2004
(http://www.softwaretestpro.com/itemassets/4772/automatedte
stinghandbook.pdf)
Sanjay Kumar, "Ad-hoc Testing: An important Process of
Software Testing"
(http://qa.siliconindia.com/qa-expert/Adhoc-Testing-An-
important-Process-of-Software-Testing-eid-134.html)

25. © 2014 HCMC Software Testing Club
THANK YOU

26. 26
Email: hoale@hcmc-stc.org
My Blog:
http://howtesting.blogspot.com
/