QA and testing fundamentals
1. Test Script Development
2. Test Script Execution
3. Commonly asked questions
1. Test Script Development
Why we create integrated test scripts:
*To create one repeatable, step-by-step document(s) that can be used by a group of application testers to test the interfaces and functionality of a computer application.
*These scripts can contain steps for more than one application. It may be a compilation of the chronological step-by-step process on how to test an application from the point of entry to the output, including all the upstream and downstream flows of the application.
What is needed to begin the process:
*Comprehensive technical requirements, and functional design documentation.
*Test cases – the test objectives and conditions that need to be tested.
*Standard test script template.
How integrated scripts are developed:
*Test Analyst(s) who are well-knowledgeable of the application, working together as a team or workgroup whose goal is to develop end-to-end test scripts.
*Analysts (testers, developers, project management) working together to determine the flow of information, which is needed to test the application from entry to exit.
Test planning/procedure:
1)Identify test objectives.
2)Identify test conditions.
3)Based on assessment of test objectives with test conditions, develop test cases.
4)Regular communication with each application expert(s), focusing on each initiative (enhancement or fix), respectively.
5)Document test cases that are planned for testing.
6)Review test cases/scenarios with developers, project management to ensure that they are complete and comprehensive.
7)Review test scripts with developers, project management.
8)If applicable, verify and validate that all upstream and downstream impacts are included and in the correct order chronologically.
9)Develop a test schedule which details script execution on a daily & weekly basis.
2. Test Execution
Purpose:
*To manually (or via an automated test tool) test an application, enhancement, or fix.
What’s needed to begin:
*Test scripts, testing schedule.
Test execution procedure:
1)Organize all integrated test scripts.
2)Execute scripts, as scheduled, during pre-determined testing days (to insure valid testing).
3)Confirm that the expected results are the same as the actual results.
4)Review any application inconsistencies with the existing production incidents, or with application developers.
5)If the defect is outstanding, log it as an issue (or incident).
6)Re-test incidents that have been successfully resolved by the developer.
3. Commonly asked questions about Testing:
1)What is integrated testing?
The goal of systems integrated testing is to confirm that the working applications, or groups of components, can be fully integrated to satisfy functional and technical requirements. Integrated testing may require the participation of multiple applications, some of which may be external to the scope of changes in the project.
Integrated testing tests applications in “production-like” environment and tests technical integration to ensure that all applications have end-to-end connectivity. This is a large phase of testing and consists of full functionality script testing.
2)How are scripts/functions scheduled? Who performs this task?
Scripts should be scheduled as early in the testing process as possible in order to provide time to execute and fix any possible incidents or issues. They also need to be scheduled, taking into consideration the time effort that is required, in priority order. Meaning, scripts that cover high-risk conditions should be tested first. Scheduling scripts should be performed by the Testing Manager in accordance with the Project contact.
3)What is reported in the weekly Test Status meeting?
Test Status meetings are held by the Testing Manager (testing team) and are intended as a vehicle to pass along testing information to project staff and developers. These meetings also address overall testing readiness for the next phase of testing, including current testing completion and identification of failed scripts. Any major issues will be discussed.
4)What if there are outstanding incidents at the end of testing?
Any outstanding incidents at the end of testing will be reviewed and assessed to determine which ones absolutely must be fixed prior to implementation. Only those that would prevent implementation or have a huge customer impact will be fixed and re-tested. All other incidents will be deferred. This means that either a workaround must be implemented or the incident must be fixed in production.
Email me for any additional information.
Return to ProcessIT homepage
