Which of the following are valid justifications for developers testing their own code during unit testing?(i) Their lack of independence is mitigated by independent testing during system and acceptance testing.(ii) A person with a good understanding of the code can find more defects more quickly using white- box techniques.(iii) Developers have a better understanding of the requirements than testers. (iv) Testers write unnecessary incident reports because they find minor differences between the way in which the system behaves and the way in which it is specified to work.
Answer(s): A
It is unlikely that developers will have a better understanding of the requirements than testers, partly because testers work closely with the user community (and may be drawn from it) and partly because developers seldom work with the complete set of requirements in a medium to large development.Testers may raise incidents related to the difference between user expectations and the specification, but these are not unnecessary. Such issues are more likely to arise at the later stages of testing. Early testing (unit testing) is usually done most effectively by developers with a good understanding of the code and the development environment; they can be more efficient and more effective at this level. Later independent stages of testing offset any disadvantage from the lack of independence at unit testing level.
Which of the following pairs of test tools are likely to be most useful during the test analysis and design stage of the fundamental test process?(i) Test execution tool(ii) Test data preparation tool(iii) Test management tool(iv) Requirements management tool
Answer(s): D
Which of the following is most likely to cause failure in the implementation of a test tool?
Answer(s): C
What benefits do static analysis tools have over test execution tools?
Which of the following principles should be followed when introducing a test tool into an organization?(i) Assessing organizational maturity to establish whether a tool will provide expected benefits. (ii) Requiring a quick payback on the initial investment. (iii) Including a requirement for the tool to be easy to use without having to train unskilled testers. (iv) Identifying and agreeing requirements before evaluating test tools.
Answer(s): B
Assessing organizational maturity (i) is very important when deciding whether to introduce a test tool, as implementing a tool in an immature test organization with poor processes is unlikely to produce any benefits.A quick return on the initial investment (ii) in a test tool is rare. Having a requirement that a tool should be easy to use for untrained and unskilled testers (iii) is generally a false hope. This is comparable with expecting someone who has never driven a car to be able to drive safely and effectively.Agreeing requirements before evaluating tools (iv) is essential. Not to do so would be comparable with building and testing a system without requirements. In conclusion, (i) and (iv) are good principles to follow when introducing a tool and (ii) and (iii) are not.
Post your Comments and Discuss ITIL ISEB-SWT2 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the ISEB-SWT2 content, but please register or login to continue.