QA EXAM

I. TYPES OF TESTING (17pts)

Instructions: Identify what type of testing is being described
1. Type of test/s that focuses on the smallest testable parts of an application - Unit testing
2. Type of test/s that ensures no existing functionality is broken due to the latest changes – Regression Testing
3. Type of test/s that focuses on the user requirements or acceptance criteria - Acceptance Testing
4. Type of test/s that focuses on individual software modules being combined and tested as a group – Integration Testing
5. Type of test/s that focuses on the complete, integrated system to evaluate compliance with user requirements – System
Testing
6. Type of test/s that focuses on crucial functionalities before a more rigorous testing is done – Smoke Testing/Sanity Testing
7. Type of test/s that focuses on latest changes/fixes before a more rigorous testing is done – Defect Testing
8. Type of test/s that focuses on the speed or effectiveness of an application – Performance Testing
9. Type of test/s that puts normal up to peak level demand on an application and measures response time – Load Testing
10. Type of test/s that measures an application’s response time over a significant amount of time – Volume Testing
11. Type of test/s that measures the breaking points or safe usage limits of an application – Stress Testing
12. Type of test/s that simulates user actions in an application, usually done by the end-users - User Acceptance Testing
13. Type of test/s that focuses on protecting data, maintaining confidentiality and integrity of the system – Security Testing
14. Type of test/s that focuses on attacking a system with the intention of finding vulnerabilities, potentially gaining access to
its functionality and data – Penetration Testing
15. Type of test/s that focuses on invalid input or unexpected user behaviour - Destructive Testing/Negative Testing
16. Type of test/s that has visibility of the internal structures of an application – White-box Testing
17. Type of test/s that lacks visibility of the internal structures of an application - Black-box Testing

II. DEFECT SEVERITY VS PRIORITY (6pts)

Instructions: Fill-in the blanks with either "High" or "Low"
1. Customers are being notified twice after a successful transaction. Several complaints were received. This defect should be
considered High severity and Low priority.
2. An online banking application cannot connect to the user database. This defect should be considered _High severity and
High priority.
3. Entering future dates when viewing transaction history causes the application to crash. This defect should be considered
Low severity and Low priority.

Page 1 of 7
III. TESTING PROCESS (5pts)
In a release, let’s assume we have 5 change requests and 2 developers and the following sample illustration demonstrates how a
waterfall process looks like:

--- release timeline ---

CR #1
CR #2
Build & Test
CR #3
Deploy Execution
CR #4
CR #5

Make a similar sample illustration, but this time demonstrating an AGILE process.

--- release timeline ---

CR #1
CR #2
Build & Test
CR #3
Deploy Execution
CR #4
CR #5

Page 2 of 7
IV. TEST CASE CREATION (5pts)
Given this login screen of an online banking application, briefly list down the 5 most critical test scenarios you can think of.

1. Validate that error message will be displayed when User name entered is incorrect.
2. Validate that error message will be displayed when password entered is incorrect
3. Validate that user account will be locked when exceeding the number of attempts in logging in
4. Validate that user will successfully logged in to application when the correct username and password is entered.
5. Validate that the Log on button is working.

Page 3 of 7
 V. Critical Thinking Part 1
(Multiple Choice)

Question #1:
Given the validation script below:

Which implementation of the keyword Verify that the Name is Saved Correctly will generate a PASS result? A

Question #2:
Given this script:

When the test is executed, what is the value of ${car} when it reaches the Log step. B

A. DeLorean DMC-12
B. Volkswagon Beetle
C. DeLorean DMC-12 Volkswagon Beetle
D. Set Variable

Page 4 of 7
Question #3
Given this script:

Which implementation of the keyword Fill Up Fruit Basket will generate a PASS result? C

Question #4
Given x = 1, what will the script below return? A

If x > 1:
x = x + 1
else if x < 1:
x = x + 2
else:
x = x + 3

return x

A. 1

B. 2

C. 3

D. 4

Page 5 of 7
VI. Critical Thinking Part 2

Problem # 1:
Shown below is an automation script from the test automation tool we are using. The feature we are testing is the Login
Module. As you can see, we’ve completed the first script for the test case Valid Login for you.

Your task is to complete the second test scenario Invalid Username/Password Combination. Build the test script from
what you can infer from the first test script.

1 *** Test Cases ***

2 Invalid Login
3 Open TRADERS Home
4 Enter Username enchong
5 Enter Password welcome1
6 Click the Login Button
7 Verify that User does not successfully Logged In.

Problem # 2
Here is an example of our test script for validation.
Your task is to complete the test script by filling in the missing parts as represented by cell numbers 1 to 7.

Page 6 of 7
1. Should be Equal as String
2. ${resultset[0][1]}
3. Should be Equal to Int
4. ${resultset[0][2]}
5. Should be Equal as String
6. Should be Equal as String
7. ${resultset[0][5]}

Page 7 of 7