Documente Academic
Documente Profesional
Documente Cultură
An example of these kinds of thinking is found in a fable called The Kings Challenge
By Everett and McLeod Jr., 2007 and Kaner et. al, 2002
By Everett and McLeod Jr., 2007 and Kaner et. al, 2002
What kinds of tester thinking did the third wizard exercise in solving the kings puzzle?
By Everett and McLeod Jr., 2007 and Kaner et. al, 2002
By Everett and McLeod Jr., 2007 and Kaner et. al, 2002
Each of these objectives can be validated without trying to break the car or redesign it. Each of these objectives are personal and you need to prioritize them to in final your final decision
These testing approaches are referred to by common terminology in the testing industry
examine = static testing
(observe, read, review without driving the car)
The manufacturer is responsible to build a new car which satisfies all the requirements
New requirements, more understandable test objectives The auto design tester is responsible to validate the current state of the new car against its requirements
If the new car doesnt initially meet the requirements, then its the designer, not the tester who must improve the design for full compliance After the design changes are done, the tester needs to revalidate the revised design against the requirements
Design, test, correct, retest cycle continues until the new car meets its requirements and is completed before the car is manufactured Requirements are essential for testing validation at every stage of developing a new car
By Everett and McLeod Jr., 2007
Specifications (blue prints or models) are the designers interpretation of the requirements on how the design can be manufactured When specifications are validated against the requirements, all the subsequent physical car assembly validation can be performed against the specifications
If the risk factors are well known and quantifiable, its possible that testing can reduce the probability of the risk occurrence
By Everett and McLeod Jr., 2007
Test planning highlights the risk areas such that the largest possible percentage of the test schedule and effort (both positive and negative testing) are allocated to reduce that risk Testing does not completely eliminate the risk since there are always more scenarios to test than the allotted time and resources to complete the tests
Tester must complete as many of the negative test items in the plan with the remaining the testing budget after positive testing and risk testing are completed
By Everett and McLeod Jr., 2007
References
P. Ammann and Jeff Offutt, Introduction to software testing, Cambridge University Press, 2008 G. D. Everett and R. McLeod Jr., Software Testing, Wiley InterScience, 2007 C. Kaner, J. Bach, B. Pettichort, Lessons learned in software testing, Wiley Computer Publishing, Addison-Wesley, 2002, pp. 286