The following test cases for a Library Management System are available to test changes made to the functions and data structures associated with borrowers
1. Add a new borrower to the system
2. Update a borrower's data
3. Remove a borrower from the system
4. Loan a book to a borrower
5. Return a book from a borrower
6. Reserve a book for a borrower
7. Send "reservation ready" message to a borrower
Which of the following test sequences represents a possible use case? (a test sequence always start with test #1)
Which ONE of the following statements does NOT describe how testing contributes to higher quality?
Which TWO of the following test tools would be classified as test execution tools? [K2]
a. Test data preparation tools
b. Test harness
c. Review tools
d. Test comparators
e. Configuration management tools
Which of the following is a valid reason for writing test cases based on experience and intuition? [K1]
From the following list, which of the following apply to experience-based techniques? [K2]
a. Test cases are derived from a model of the problem to be solved or the software
b. Test cases are derived from the knowledge of the testers
c. The knowledge of testers, developers and users is used to drive testing
d. The internal structure of the code is used to derive test cases
Before an invoice can be created, an account is required. Before an account can be set up, an account user is required (in order to set up the account). The software is delivered with a master user only, who can only create other types of users. The following test cases have been written to test the high-level structure of the software
a. Create an invoice
b. Amend an invoice
c. Process an invoice (send to customer)
d. Delete an invoice
e. Create an account
f. Create an account user
g. Amend an account user
h. Delete an account user
i. Amend an account
j. Delete an account
Which of the following test procedures would enable all tests to be run? [K3]
Which of the following statements about use-case testing are most accurate?
(i)In a use-case diagram an actor represents a type of user.
(ii)Use-cases are the most common test basis for unit testing.
(iii)A use-case describes interactions between actors.
(iv)An actor is always a human user that interacts with the system.
(v)Test cases can be based on use-case scenarios.
(vi)Use-case testing will often identify gaps not found by testing individual components.
It is recommended to perform exhaustive tests for covering all combinations of inputs and preconditions.
