1. LESSON 01 Hands-on Training Execution
To protect the confidential and proprietary information included in this material, it may not be disclosed or provided to any third parties without the approval of QA TRAINING EXPERTS.

2. What is a Defect?
Blocked Status
Snapshots to prove result – Pass or Fail
Linking Defects
What to do after a Step Fails – Stop or Continue
Updating Test Execution Log
Test Assignment

3. Test Environment Readiness
The Testing Lifecycle
Requirement Analysis
Test Planning
Test Preparation
Test Environment Readiness
Test Execution

4. Test Execution Activities
Once the Test Environment Setup and Test Preparation is completed, Test Execution can begin.

5. Introduction
Test execution is the most important phase of the STLC and also the entire development lifecycle. 
The Reason - every team/team member’s contribution and work gets validated here:
Has the Business Analyst interpreted the requirements correctly?
Has the development team translated the business requirements to functional requirements and eventually to code correctly?
Has the data architect and DBAs designed the right back-end systems?
Test Execution is where all the answers to these questions are found

6. The Test Execution Process
Below are the main activities that you will be responsible for when the application is handed to us for testing.
These activities represent the Test Execution process.
Memorize them. Memorize the order that they occur.
We will be learning each one. One at a time.
Execute Tests and Capture Results
Report Defects
Retest Defects
Retest Failed and Blocked Tests
Regression Test

7. The Test Execution Process
Every company will have different standards and procedures for testing that you must learn and follow.
In order to be successful you must know what you need to know to ask the right questions. This is very important.
Testers ask questions. They ask a lot of questions. They never assume.

8. The Test Execution Process
Kick Off meeting
Sharepoint

9. The Test Execution Process
Once you have each activity memorized when your on a new project all you need to do is ask yourself if you know the what, when, where, how, and who to be successful.
What?
When?
Where?
How?
Who?

10. The Test Execution Process
What to Execute?
When to Execute?
Where to Execute?
How to Execute?
Who?

11. Execute Tests What to Execute?
You need to know how tests are assigned for execution.
Either tests will be assigned directly to you or you choose what to execute.
Tests could be divided up by day, week, individual tester, module, etc.

12. Execute Tests When to Execute?
You need to know when tests are expected to be executed.
Do you have specific tests that you have to execute each day or each week?
Typically the tests in scope for a test cycle are divided by the total number of days in the cycle by the number of testers to determine a per day execution rate.
500 tests / 20 days = 25 PER DAY
25 / 5 testers = 5 per day target

13. Execute Tests Where to Execute?
You need to know where to go to find the tests for execution.
IF USING A TOOL
IF NOT USING A TOOL
Where will they be stored on the network
Shared Document Repository
Which test set in HP ALM
You need to know how to access the test environment.

14. Executing a Test - continued
The beginning
Review the objective of the test
Review the requirement if referenced.
Check to see if there any pre-requisites or dependencies that are required before you can start the test.
For each step:
Perform the action specified in the step description.
Compare the expected result to the actual result.
Determine if the step passes or fails
5.1 If they match - the step is considered as “Passed”.
5.2 If they don’t match - the step is considered as “Failed”.

15. Executing a Test - continued
Passed
5.1 If they match - the step is considered as “Passed”.
Enter “Passed” for the actual result
Some places may require you to show evidence of each
passed step or of the last step to prove that it did pass.
Continue to the next step in the test and repeat 1 to 3

16. Executing a Test – continued
Failed
5.2 If they don’t match - the step is considered as “Failed”.
Enter “Failed” for the actual result and write a short description of the problem.
Take a snapshot of the problem
If using a tool, attach snapshot to the failed step
If using word or excel insert image as an object
Determine if it is a problem with the test case or the AUT.
Report a defect against the application or test case.
Reference the defect ID in the actual result of the failed step.

17. Executing a Test – continued
Stop or Continue
Determine if you can continue the test or if you should stop.
If the defect is not critical or high you should always try to continue executing the test to see if you can flush out any more problems.
If the defect requires a work around where the steps are different then the test case, consult with the Test Lead on how to handle this situation. Snapshot EXAMPLE
If you can continue – repeat steps 1 to 3

18. Executing a Test – continued
All done
Determine if the entire test has “Passed” or “Failed”
If all steps passed successfully then the test has “Passed”
Some places may require you to show evidence of the last step to prove that it did pass.
If one of more steps failed then the test has “Failed”
Saving the test results
If using Excel or Word
You must save the document as per the desired naming convention. Example – George_B_071718_PASSED_Test to verify xxx.doc
Save the document to a place on the network or it to the test lead. (find out the right process)
If using a tool – you are done

19. Execute Tests What to Execute
You need to know how tests are assigned for execution.
When to Execute
You need to know when tests are expected to be executed.
Where to Execute
You need to know where to go to find the tests for execution.
You need to know how to access the test environment.
How to Execute
If using excel or word
Where should you put tests that are finished? Save or ?
Naming conventions when saving complete test
Is there a log that you must update with execution results.
Should you be capturing a snapshot to prove pass?
Should you reference the defect id in the actual result field?
Should you reference the defect id anywhere else?
Who to Execute

20. Execute Tests How to Execute?
Do you need to provide evidence that a step in a test passed?
Stop or Continue?
Is there a Test management tool?
How is test execution tracked? Execution Log?
Using Excel or Word
naming convention to name document when completed?
What to do with completed test? Save where? ?
Procedure for adding snapshots? Tool for snapshots?
Logging test results and linked defects? Execution Log?

21. The Test Execution Process
Execute Tests and Capture Results
Report Defects
Retest Defects
Retest Failed and Blocked Tests
Regression Test

22. Where to Report Defects? Who to Report Defects to
What?
When?
Where to Report Defects?
How to Report Defects
Who to Report Defects to

23. Report Defects What - NA When to Report Defects - NA
Where to Report Defects
Tool, template, DB, or combination.
How to Report Defects
What are the required fields?
Defect lifecycle
Defect flows – rejected, fix/ready for retest,
Defect statuses
Defect severities
Defect turn around times
If using a tool - What should the defect be linked with? Instance, run, step, etc.
Update execution log and/or defect log
Who to Report Defects
Who should you report defects to

24. The Test Execution Process
Execute Tests and Capture Results
Report Defects
Retest Defects
Retest Failed and Blocked Tests
Regression Test

25. Where to Retest Defects?
Execute Tests
What?
When to Retest Defects?
Where to Retest Defects?
How to Retest Defects?
Who?

26. What? - NA
When to Retest for Defects?
When the defect has been assigned back to you and is status is ready to retest.
Where? - NA
How to Retest for Defects?
Follow steps to reproduce to verify if the defect is fixed.
Add comment stating “tested, verified problem resolved, can be closed.”
Request defect to be closed.
Who to Retest for Defects?

27. The Test Execution Process
Execute Tests and Capture Results
Report Defects
Retest Defects
Retest Failed and Blocked Tests
Regression Test

28. Execute Tests What to Retest for Failed and Blocked Tests?
When to Retest Failed and Blocked Tests?
Where to Retest Failed and Blocked Tests?
How to Retest Failed and Blocked Tests?
Who to Retest Failed and Blocked Tests?

29. Retest Failed and Blocked Tests
What - NA
When to Retest Failed and Blocked Tests
When requested by the QA Lead
Start of a new test cycle
Where - NA
How to Retest Failed and Blocked Tests
Review all defects that have been fixed and are ready to retest
Retest defects and request that they be closed.
Update execution log and defect log
asdfasdfasdf
Who - NA

30. The Test Execution Process
Execute Tests and Capture Results
Report Defects
Retest Defects
Retest Failed and Blocked Tests
Regression Test

31. Execute Tests What to Regression Test? When to Regression Test?
Where to Regression Test?
How to Regression Test?
How to Regression Test?

32. Execute Tests What to Regression Test Passed tests
If last phase – core functionality, high priority requirements, business critical functionality, closed critical defects
When to Regression Test
During each Test cycle
Last phase before UAT
Where - NA
How - NA
Who to Regression Test

34. Practice Items Step Name Step Description Expected Result
Actual Result
Step 1
Open Internet Explorer and go to
The yahoo homepage should be displayed.
PASSED
Step 2
Click on the link labeled "Sign up" to get to the registration page.
The Yahoo Registration should be visible.
FAILED
The Yahoo Registration was not visible. Message reading “Page not Found” was displayed .
DEFECT 27
Step 3
Complete the registration without selecting Gender.
An error message should be displayed reading "This information is required" and the registration should not have been able to complete without gender.

35. Practice Items Step Name Step Description Expected Result
Actual Result
Step 1
Open Internet Explorer and go to
The yahoo homepage should be displayed.
PASSED
Step 2
Click on the link labeled "Sign up" to get to the registration page.
The Yahoo Registration should be visible.
Step 3
Complete the registration without selecting Gender.
An error message should be displayed reading "This information is required" and the registration should not have been able to complete without gender.
FAILED
Registration was successful with selecting gender
Defect 101