When a tester executes a test and observes behaviour that differs from the specification, this is called a: a) defect b) error c) failure d) mistake e) fault Which of the following best describes regression testing? v) Testing to ensure unchanged areas still work w) Testing after a fix x) Testing after environment changes y) Testing after code refactoring z) Testing only at the end of the project a) v, w & y are true b) v & w are true c) v, w, x & y are true d) w & z are true e) all are true Which of the following is NOT included in IEEE 829 test documentation? a) Test summary report b) Test design specification c) Test incident report d) Test risk assessment e) Test log Testing should be stopped when: a) All planned tests are executed b) The exit criteria have been met c) No more defects are being found d) Time runs out e) Both b and c ...
ISTQB Dumps For Software Testing - Part 4
Questions:
How would you define a good test?
Answers:
A good test is one that can potentially find a fault in the system. If this test does not find a fault then it will give us a certain amount of confidence. Tests must also be efficient – we should not have tests which all do the same thing.
For example, a test should be able to run without dependencies. So running Test A shouldn't be hindered by Test B executions. Also, if Test C contains a duplication of Test B it might not be necessary to Test it too.
For example, a test should be able to run without dependencies. So running Test A shouldn't be hindered by Test B executions. Also, if Test C contains a duplication of Test B it might not be necessary to Test it too.
Just to expand on the answer. "A Good Test" will always have some minor faults. The important thing is there is no major faults which conflict with the operation set out in the requirements in the specification.
ReplyDelete