Day #2: Let’s Start Testing

It is now time to start testing. Learning to execute the cases assigned to you is the quickest and most effective way to begin to learn the art of QA and develop your craft.

Let’s Start Testing and Find Bugs

Once code is ready for testing, you will be given a build or have access to a computer that is running the code you are to test. This computer may be a server or it may just be a QA workstation configured for your testing.

Once you are ready, you begin your tests. These earliest of tests may be simply verifying that the application launches in a particular environment. They may entail checking a single, tiny feature. Or you may be required to test many, many features. No matter what the scope or test, your focus begins with…

Follow the instructions. I know that sounds simplistic (and it is) but that really is the main starting point. Follow the instructions detailed in each test; do each step, one step at a time.

Okay, maybe there is a little more to it than that. First, find out what test(s) are assigned to you. Then clarify the testing priorities; what test(s) should you run first, which second, etc.

Know how much time the tests you’ve been assigned are expected to take, if possible (this is the first step in Managing Expectations - covered in detail in the 10 Skills of Elite Testers course).

This is a piece not to be overlooked. If you want to set yourself up for success, you had better first know what is expected of you.

So you get your tests, now what? Now you establish what environment you should be testing in.
• What computer should you be testing on?
• What state should it be in?
• Should you have a fresh factory installation?
• Are there specific programs that should be installed and/or running while you execute your tests?
• Are there any specific testing tools you should be using?

You have your tests and their priorities and know the environment you should test in…now what?

Well, where are you going to enter the results of your testing? Is there a test matrix that you should track your results in? Is there a bug database for entering your test results? A spreadsheet?

You have to capture your results somewhere and it’s best to know this before you jump in and have several bugs to keep track of. Early software releases always have plenty of bugs to get you started! Knowing where you will enter your test results, you are now almost ready to start testing.

The last thing to do (for best results) is to note the time you start testing. This is the first step that you can take to begin measuring. When you can report with certainty how long a test takes to execute, you are able to effectively manage expectations because you have quantified the effort involved with solid numbers. So note the time you start testing and then, note the time you stop testing.

This serves three purposes:
1. Gives you the information to show what you have worked on each day
2. Shows how long the tests actually take to complete, which will help you estimate how long subsequent execution of the same tests will take in the future
3. As you improve your testing, this will show the effect of the efficiencies and improvements you have made. This will become apparent as you compare how long the tests took the first time you ran them against how long they took the 10th or 20th time you ran them. Documenting this improvement will be a key piece of ammunition for you to use when you show off what an amazing tester you have become when the time comes for a raise

Now to start testing, follow the instructions detailed in each test case. This is a simple, yet key, action that begins to separate the average testers from a Quality Assurance Professional. Any test can be run successfully by following clear instructions.

When you start testing, if you notice that the instructions in the test case are not clear, make note of this and update them. Rewrite them so that they are simple, straightforward, and comprehensible to all Quality Assurance personnel.

It is your attention to detail that makes the difference. So be very clear what steps you are to perform, and then execute them meticulously when you start testing.

As you progress through your test cases you will undoubtedly encounter some behavior that is not what is supposed to happen. If you have followed all instructions correctly up to this point, chances are you have found a bug.

Now what do you do? Write it up! Everyone will celebrate! You will be seen as a genius and the accolades will be lauded upon you!! Your boss must now feel the need to give you a raise!

But wait…not so fast. Before you get that raise, you probably should know what to do with that bug.

Tune in tomorrow for Day #3 where we will look at the steps to take once you have found a bug.