8 Considerations in developing Testing methodologies
Objective – provide framework for developing test tactics
- Acquire and study the test strategy
- Determine the type of development project
- Determine the type of Software system
- Determine the project scope
- Identify the tactical risks
- Determine when testing should occur
- Build the system test plan
- Build the Unit test plan
Testing Challenges (myths?)
- Testing is not essential for delivery
- Testing is often un-structured, ill-defined and hence subjective
- Testing is often not managed
- Testing itself is error-prone
- Testing is expensive
- You can not test quality into the software
Testing Participants
- Software customer
- Software user
- Software developer
- Software tester
- Information service management
- Service management
- Auditor
Misconceptions about testing
- Testing finds errors and hence appears place the blame for those errors on the development organization. This leads “Us versus Them” attitude among the groups
- Anyone can test and no particular set of skills are required
- Testers can test for quality at the end of development project
No comments:
Post a Comment