Professional Documents
Culture Documents
Test Analyst - Readiness Assessment Exercise
Test Analyst - Readiness Assessment Exercise
Requirements
1. Used as basis/reference for defining test cases for a project
Test Case
2. A set of test inputs, execution conditions, and expected results
developed for a particular objective
Test Planning
3. Activity performed to review requirements and prepare test
cases
System Analyst
4. Responsible for fixing problems found during testing
Negative Testing
5. Type of testing that covers alphanumeric validation and blank
or zero-value entries
Functional Testing
6. Also known as Black-Box Testing
Defect
7. Specific cause of failure of a test
Test Execution
8. Testing using an unacceptable, abnormal, or unexpected
condition or data
Test Analyst
9. Responsible for reporting problems found during testing
White-Box Testing
10. This uses the internal structure of the program to derive the
test cases
Sanity Testing
11. Cursory testing that covers basic functionality to demonstrate
database stability, application connectivity, etc.
Performance Test
12. Testing to verify the load, volume and response times as
defined in the requirements
Page 1
Regression Testing
13. The objective of this is to verify stability of unchanged
functionalities of the software
Testing
14. An organized process of identifying discrepancies between the
expected and the actual results from the use of a system
Test Report
15. Prepared to document test results, statistics and any deviations
from what was planned (as defined in the Test Plan).
C. Identify at least three scenarios that need to be tested to address each requirement
stated. Define any assumptions made, if necessary.
a. Generate one reminder notice for each customer who has an outstanding
balance due and who has not paid within the last 30 days.
Page 2
b. The 30-day period is counted from the day when the customer’s last payment
was received or from the day when the customer was last sent a bill or a
reminder notice.
D. Indicate in the blank provided – “T”, if the requirement is completely testable, and “F”, if
the requirement is flawed. If “F”, identify what the flaw is in the particular requirement,
and list all possible questions that will help clarify the user requirements.
a. The wording of the reminder notice must comply with all pertinent
legal and local regulations.
Page 3
c. The reminder notices must be mailed in purple 7” x 12” envelopes.
Page 4
f. If the bill was never sent to the customer and a reminder notice has been
generated, ensure that the account officer reviews and approves it
before it is sent out.
Page 5