Overview

As and when an item in the list is done, you strike it off, remove it from the list or check the item off with a tick – to mark its completion. Isn’t it all too familiar to us?

However, is that all it can be used for?

Can we use checklists in our IT projects formally (specifically QA) and if yes, when and how? This is what is going to be covered below.

I personally advocate the use of checklists for the following reasons:

It is versatile – can be used for anything

Easy to create/use/maintain

Analyzing results (task progress/completion status) is super easy

Very flexible – you can add or remove items as needed

As is the general practice we will talk about the “Why” and “How” aspects.

Why do we need checklists? : For tracking and assessing completion (or non-completion). To make a note of tasks, so that nothing is overlooked.

How do we create checklists? : Well, this could not be simpler. Simply, write everything down point by point.

Example checklists for QA processes:

As I mentioned above, there are some areas in the QA field where we can effectively put the checklist concept to work and get good results. Two of the areas that we will see today are:

Test readiness review

When to stop testing or Exit criteria checklist

Test Readiness Review:

This is a very common activity that is performed by every QA team to determine whether they have everything they need to proceed into the test execution phase. Also, this is a recurring activity before each cycle of testing in projects that involve multiple cycles. In order to not run into issues after the testing phase begins and realize that we entered the execution phase prematurely, every QA project needs to conduct a review to determine that it has all the inputs necessary for successful testing.

A checklist facilitates this activity perfectly. It lets you make a list of ‘things-needed’ ahead of time and to review each item sequentially. You can even reuse the sheet once created for subsequent test cycles too.

Additional info: Test Readiness Review is generally created and the review is performed by the QA team representative. The results are shared to the PMs and the other team members to signify whether the test team is ready or not to move into the test execution phase.

Team’s access to the application, version controlling tools, test management

Team’s trained

Technical aspects- server1 refreshed or not?

Defect reporting standards are defined

Now, all you have to do with this list is mark done or not done.

Exit Criteria Checklist:

As the name indicates, this is a checklist that aids in the decision making of whether a testing phase/cycle should be stopped or continued.

Since, a defect free product is not possible and we will have to make sure that we test to the best extent possible in the given amount of time – a checklist of the below effect is created to track the most important criteria that needs to be met to deem a testing phase satisfactory.

Exit Criteria

Status

100% Test Scripts executed

Done

95% pass rate of Test Scripts

No open Critical and High severity defects

95% of Medium severity defects have been closed

All remaining defects are either cancelled or documented as Change Requests for a future release

All expected and actual results are captured and documented with the test script

Testing Checklist

Are you going to start a new project for testing? Don’t forget to check this Testing Checklist in each and every step of your Project life cycle. The list is mostly equivalent to Test plan, it will cover all quality assurance and testing standards.

Automation Checklist

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

#1. 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.

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

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

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

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

#6. 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.

Points to note:

The above two are examples to showcase the use of checklists to QA processes, but the usage is not limited to these two areas.

The items in each list are also indicators to give an idea to the readers about what sort of items can be included and tracked – however, the list can be expanded and/or compacted as needed.

We really hope that the above examples have been successful in bringing forward the potential of checklists to QA and IT processes.

So, the next time you are in need for a simple tool that is semi-formal, simple and efficient, we hope we have oriented you towards giving checklists a chance. Sometimes, the simplest solution is the best.

@Bibhu: The exit criteria list and the readiness review list provided in this article are merely examples to showcase 2 very practical situations you can use it in a QA world. If in your case, it makes sense to include the explanation column, by all means you can do so, since checklists are so expandable. I hope that helps….