Automation Checklist

Automation Checklist

If you answer yes to any of these questions, then your test should be seriously considered for automation.

Can the test sequence of actions be defined?

Is it useful to repeat the sequence of actions many times? Examples of this would be Acceptance tests, Compatibility tests, Performance tests, and regression tests.

Is it possible to automate the sequence of actions?
This may determine that automation is not suitable for this sequence of actions.

Is it possible to “semi-automate” a test?
Automating portions of a test can speed up test execution time.

Is the behavior of the software under test the same with automation as without?
This is an important concern for performance testing.

Are you testing non-UI aspects of the program?
Almost all non-UI functions can and should be automated tests.

Do you need to run the same tests on multiple hardware configurations?
Run ad hoc tests (Note: Ideally every bug should have an associated test case. Ad hoc tests are best done manually. You should try to imagine yourself in real-world situations and use your software as your customer would. As bugs are found during ad-hoc testing, new test cases should be created so that they can be reproduced easily and so that regression tests can be performed when you get to the Zero Bug Build phase.) An ad hoc test is a test that is performed manually where the tester attempts to simulate the real-world use of the software product. It is when running ad hoc testing that the most bugs will be found. It should be stressed that automation cannot ever be a substitute for manual testing.

Recommended reading


#1 ff


#2 Deva

hi this is very importent most using off testing team

#3 shantha

This is shantha from chennai.i want some sample check list’if anybody have plz send me
my mail id is

#4 Arun Vats

This is very helpful for starting automation…
good going … all … keep it up …

#5 shibu

its really nice

#6 Salma

I would like to know how to carry out ad hoc testing for the application using test cases and I might sound silly, however i would like to know how can i find more bugs during adhoc testing(as mentioned in the article; ‘It is when running ad hoc testing that the most bugs will be found’) as in my organisation, the more bugs a tester finds in the application the more he/she is considered as a good and active tester.

Dear Vijay, I appreciate your efforts and try to read more from your blog to be a good and effective tester. Thank You and take care:-)

#7 Amit A

Dear Salma, adhoc testing means thinking out of box.Here is some example of a Log in form:-

1.IF you want to test the text field of name, try to enter NUMBERS, SYMBOLS, BLANK SPACE then try to submit the form whats the outcome?
2.In email id field enter number only.
Just go out of limit means adhoc if you need more ask me on

#8 Babloo

Ad-hoc Testing also name as Random Testing/Monkey Testing

It is a type of testing where we don’t refer any kind of documentation like the test cases and find out the bugs.

This has to be done when
1. you got all the module are relatively stable

2. you have done your smoke testing but if you got any creative scenario during smoke testing you can try it and find the bugs but if you got too many creative scenario you can not it down and do it later.

We do adhoc testing because we dont know how people gona use our product and they may find defect by using randomly. So we do ad-hoc testing in order to avoid this.

If we dont do adhoc testing then when people find bugs they will spread bad name about the product so to avoid these we do adhoc testing.

For example, if you are ask to test a ceiling fan, we should try to perform all the random scenarios like
1. test the fan by hanging downward the ground as usual and check whether it works fine or not
2. test the fan by attaching on the wall and check how it works
3. test the fan by turning up-down and check the behavior of the fan.
etc… likewise we can do many testing beyond the test scripts.

Leave a Comment