Scribd
Upload
205 views5 pages

Negative Testing Requirements Performance Test Test Execution White-Box Testing Sanity Test Test Case Defect Functional Testing Test Planning

This document contains a readiness assessment exercise for a test analyst position. It includes multiple choice and true/false questions about test case development, requirements, and testing terms. Scenarios are provided to test loan reminder notice requirements, and requirements are identified as testable or flawed. The exercise evaluates knowledge of testing fundamentals.

Uploaded by

Rob Velasco
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
205 views5 pages

Negative Testing Requirements Performance Test Test Execution White-Box Testing Sanity Test Test Case Defect Functional Testing Test Planning

This document contains a readiness assessment exercise for a test analyst position. It includes multiple choice and true/false questions about test case development, requirements, and testing terms. Scenarios are provided to test loan reminder notice requirements, and requirements are identified as testable or flawed. The exercise evaluates knowledge of testing fundamentals.

Uploaded by

Rob Velasco
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Test Analyst – Readiness Assessment Exercise

Name : Rob Russell A. Velasco Date : 10/07/2021

A. Choose the correct answer from the options provided.

Negative Testing Black-box Testing Requirements Edit Test


Performance Test Project Planning Test Execution White-box Testing
Sanity Test Test Case Defect Design
Test Analyst Functional Testing Testing Test Report
Regression Testing Unit Test Test Planning Systems Analyst

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
Developer
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 Testing
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

14. An organized process of identifying discrepancies between the


expected and the actual results from the use of a system

15. Prepared to document test results, statistics and any deviations


from what was planned (as defined in the Test Plan).

B. Consider the following requirement for a loan system:


“Print a reminder notice for borrowers who have not paid for 30 days.”
What additional information do we need for this requirement in order to build an
acceptable set of test cases for it? Identify at least three items.

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.

b. Ensure that the notice is generated and sent out promptly.

Page 3
c. The reminder notices must be mailed in purple 7” x 12” envelopes.

d. For customers who are exempted from receiving reminder notices,


ensure that two notices are generated.

e. A reminder notice is generated only if the customer has an outstanding


balance due on the day the reminder is to be generated. The
outstanding balance is the net total amount owed by the customer on
any day.

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.

g. The software for the reminder notice must be programmed as three


software modules, named X1, X2 and Y1.

Page 5

You might also like