Tag Archives: defects

Should users be involved in testing?

Say you are the manager of an IT project and you have to decide who’s going to perform the testing of the new application developed for the Business unit downstairs. What are your options? How do you keep everybody happy and get what you want at the same time? Continue reading

What’s a good boss?

Oh, man, this is such a “hot” topic! People can talk about this forever!

So I’ve asked a few how would they describe a good boss?

 

Here’s what they say: Continue reading

Will a test tool resolve your problems?

Until recently I thought that having/using a test management tool (like Mercury for example) is the answer to some problems that happen a lot:
– testers don’t have a consistent way of writing test cases
– defect loggers (people other than testers sometime log defects) don’t follow basic rules when describing defects
– project managers don’t keep track of the test execution or defect status
And others. Continue reading

How to log defects using Excel

how-to-log-defects-using-excel

First testing job: three things to give you a head start

Starting a new job can be daunting, you don’t know where to start or how it’s going to be. If this is your first testing job, asking pertinent questions is key. Getting the job is one thing, but keeping it is another. You know how people assess and judge you on the first few days on the job. It’s really important to ask the right questions and be proactive.

Let’s start:

Documentation:  Usually, when you start a job, you will be given documents to read. Nobody expects you to test from the first day.  The Business Requirements and the Functional Specs are the first documents you will be given to read. If you are asked what do you want to start with, ask for these two documents.

Test cases: are there any written by people who were there before you or by your colleagues? You can learn a lot about the application just by reading the test cases. This will also give you an idea about the seniority and skills of your colleagues. Be careful though, often test cases are incorrect or invalid, if the tester who wrote them didn’t understand requirements or application has changed since then. Test cases are kept in folders on a shared drive (if written in Excel) or in a testing tool. You will have to ask where they are.

Defects: ask for the list of defects logged in previous releases. Even if you don’t remember functionality in detail after going through the list, this exercise is useful because it makes you familiar with the application and that’s what you want. Defects are logged and traced using Excel or using a testing tool. Ask the team lead or a colleague where the defects are kept.

So there you go, three things that give you a head start on the job.