![Test Strategy Discussion ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to AJRA Test Strategy Discussion
Similar to AJRA Test Strategy Discussion (20)
AJRA Test Strategy Discussion
- 11. Test Planning Considerations Test Scope
- 12. Test Planning Considerations Test Scope Targets of Test The Full Set of Integrated Subsystems by Vision A Set of Code Units by Function A Set of Code Units by Association 1x Class or Routine Code N/A N/A A Set of Service Calls by Association 1x Service Contract Service The Full Set of Integrated Reporting Subsystems by Vision A Set of configurations of Reports along with the Report Engine code or applications by Function A Set of configurations of a Report along with the Report Engine code or application by Association 1x Report per medium (display / print/ email, etc.) Report N/A The Full Set of Screens by Vision Application N/A A Set of Screens by Function Integrated Subsystem/ Incremented Application N/A A Set of Screens by Association String 1x Interface 1x Screen / 1x Pop-up Unit Interface Screen
- 13. Test Planning Considerations Test Scope N/A N/A Progression Test (Test Team) (Upon completion) (Form, Function, Content, Security) Progression Test (Test Team) (Upon completion) (Functional Test, Stress Test, Load Test, Security Test) User Interface Test (Test Team) (Upon completion) (Form, Content, Navigation) Application Regression Test (Test Team) (Upon completion), User Acceptance Test (Business) (Upon completion), Parallel Test (Test Team) (Upon completion), Certification Test (Certification Authority) (Upon completion), (Subsets of User Interface Test & Progression Tests, plus other tests as needed.) Regression Test (Test Team) (Every iteration), User Acceptance Test (Business) (Every iteration), (Subsets of User Interface Test & Progression Tests, plus other tests as needed.) N/A N/A Progression Test (Test Team) (Every iteration) (Form, Function, Content, Security) Progression Test (Test Team) (Every iteration) (Functional Test, Stress Test, Load Test, Security Test) User Interface Test (Test Team) (Upon integration) (Form, Content, Navigation) Integrated Subsystem/ Incremented Application String Test (Developer) (Upon development) (Function, Stress, Load (Volume), Security) Unit Test (Developer) (Upon development) (Function, Stress, Load (Volume), Security) Code String Test (Developer) (Upon development) (Function, Security) Unit Test (Developer) (Upon development) (Function, Security) Service String Test (Developer, Business) (Upon development) (Form, Function, Content, Security) Unit Test (Developer, Business) (Upon development) (Form, Function, Content) Report N/A String Test (Developer) (Upon development) (Form, Content, Navigation) String Unit Test (Developer) (Upon development) (Function, Security) Unit Test (Developer) (Upon development) (Form, Content, Navigation) Unit Interface Screen
- 14. Test Planning Considerations IT Business Test Effort Time Test Effort D C T Iteration
- 15. Test Planning Considerations Test Timing Unit Test (Developer) String Test (Developer) 1 Regression Test (Test Team) (Functional Test, Stress Test, Load Test, Security Test, plus others as needed) Progression Test (Test Team) (Upon completion) (Functional Test, Stress Test, Load Test, Security Test) 2 User Acceptance Test (Business) 3 Code Test 1 2 3 1 2 3 Code Test
- 16. Test Planning Considerations Test Timing Unit Test (Developer) String Test (Developer) 1 User Acceptance Test (Business) 3 1 2 3 1 2 3 Regression Test Run Automated Tests (Test Team) (Functional Test, Stress Test, Load Test, Security Test, plus others as needed) Progression Test Add Delta and Run Automated Tests Functional Test, Stress Test, Load Test, Security Test (Test Team) 2 Code Test Code Test
Editor's Notes
- Speaker reads the slide and says… Requirement could be considered, as ‘Testable’ if following characteristics will be met. The state of the system and the data elements that are inputs (e.g., customer number, product number) The condition or action associated with the requirement (e.g., the user enters data, the order is validated, the check amount is deducted) The expected or specified result described in terms of data elements (e.g., customer number must be 8 digit numeric, product quantity must be greater than zero). Give the example of building your house.
- Speaker reads the slide and says… Requirement could be considered, as ‘Testable’ if following characteristics will be met. The state of the system and the data elements that are inputs (e.g., customer number, product number) The condition or action associated with the requirement (e.g., the user enters data, the order is validated, the check amount is deducted) The expected or specified result described in terms of data elements (e.g., customer number must be 8 digit numeric, product quantity must be greater than zero). Give the example of building your house.
- Speaker reads the slide and says… Explain the above characteristics and explain the examples also.
- Speaker reads the slide and says… Explain the above characteristics and explain the examples also.
- Speaker reads the slide and says… Explain the above characteristics and explain the examples also.
- Speaker reads point 1 Point 1 – The ability to identify where the greatest risk lies enables Test Managers to appropriately assign test resource. In addition, if testing time frames are shortened the Test Manager can focus on areas of highest risk. Point 2 – Early identification of non-testable requirements prevents designs type defect from being identified in later test phases Point 3 – Gets the business, developers and tester communicate using a standard deliverable. Since we knew there was a greater possibility of a defect occurring on a particular functionality then it should be no surprise if it actually does happen. Point 4 If there is a Change Control this process (risk assessment) will allow us to make a fair estimation of the level of risk and help us understand what possible people resources could be need to mitigate the risk.