This project is read-only.
!Assess the test basis
To establish the testability of the test basis. Testability here means completeness, consistency, accessibility and translatability into test cases.

Converting the test basis
In some cases, the test basis is not directly suitable for the selected test design technique, and an extra conversion operation has to be carried out. For example, a data cycle test requires a CRUD matrix and the decision tables technique requires decision tables. If these are not available, they can sometimes be derived from the available type of test basis. Apart from the question of whether the chosen test design technique is the right one (for sometimes there is little choice), there is also the question of who should perform this conversion. Ideally, it should be the designers. However, if the testers are the only ones requesting this addition, there is little chance of the designers taking it upon themselves. The other possibility is that the testers do it themselves. In this, they should take care that they only convert and do not add any information. In the latter case, they would be adding to the design themselves, and that is not the testers’ job.

The test basis is assessed using evaluation techniques and the previously created checklist(s) to obtain insight into the applicability of the established test strategy and related test design techniques. If it appears that the test basis falls short, it is of course important to report this to the supplier of the test basis via the client as quickly as possible. This party can then take responsibility for clarifying and/or filling in the gaps.

Techniques Checklist for assessing the test basis (product from section 6.5.2). Evaluation techniques (Chapter 15). Tools Defect management tool.

Assessing the test basis in VSTS

bug reporting <font color="


Last edited Nov 7, 2009 at 7:03 AM by ClemensReijnen, version 3


No comments yet.