Selecting and justifying test data questions and answers
Q1. What headings might you use in a Test Plan?
A1. No of test, what type of data you are testing, the data you will use, expected results, actual results, whether the actual results have been compared to the expected results and a comment.
Q2. What is ‘valid data’?
A2. Data that is allowable and won’t throw up an error.
Q3. What is ‘invalid data’?
A3. Data that should be rejected.
Q4. Why do test plans include data on the boundaries of a range?
A4. This is one place where bugs are likely to occur.
Q5. What is meant by a syntax error?
A5. A syntax serror is one where you have broken the strict rules of the programming language.
Q6. What is meant by a logic error?
A6. A logic error is one where the code runs but the result is not what you expected.
Q7. Find out what the name of the testing is called when you design tests on a program that you can actually see the code of.
A7. This is called white box or glass box testing.
Q8. Find out what the name of the testing is called when you design tests on a program that you can't actually see the code of but you know what it should do.
A8. This is called black box testing.
Q9. Why should you always predict the results before running any test?
A9. It is too easy to assume that just because you run a test and get some results, the results are good. You have to be able to check the output from a test against a prediction made before you ran the test, to have something to compare the results against.
Q10. Why should you plan the tests you are going to carry out before you do them?
A10. Testing is a methodical process and can be very time consuming. To write a good plan, you have to cover all bases and this means you have to plan carefully what you are going to test in advance and how you are going to carry out the tests. You don't want to spend valuable time and money carrying out unnecessary tests or duplicating tests. Neither do you want to forget to test critical area. In addition, customers of your software may demand proof that thorough testing has been carried out before accepting a software product from you.