You are performing a review of your colleague's test cases based on the following test basis document:

The Test Cases are as follows:
TC1. Success - valid 'User Name' and 'Password'; Customer Menu displayed TC2. Failure - 'User Name' field has blank entry; Error Number 12 displayed TC3. Failure - 'User Id' entered does not exist on database (i.e. unregistered user); Error Number 23 displayed TC4. Failure - 'Password' entered does not match user's password on database; Error Number 24 displayed You are guided by the following checklist in your review:
C1. There must be one test case to cover success
C2. There must be one test case for each error path (e.g. validation failure) C3. Each test case must use terminology consistent with the test basis document (field names, error numbering, etc.) Record a separate defect for each missing test case (checklist items C1 and C2) and for each test case that does not meet checklist item C3.
How many defects should you record?

Which of the following apply to System Testing?
a) May satisfy legal requirements.
b) Can use system specifications as a test basis.
c) Often the responsibility of business users.
d) Main goal is to establish confidence.
e) Should focus on the communication between systems.

Which of the following options BEST explains the pesticide paradox principle of testing?

During the development of a software change for a system, the developer makes a mistake in his work, which leads to a fault in the code. Unfortunately, the fault is not found by software testing and is released into live.
What is the DEFINITE consequence of this mistake?