Testing Overview
Two testing phases; Unit and System Integration Testing
Quality Center (QC) - Central Repository for all test cases
Issue tracking will take place in RT (see attached RT Tutorial for instruction for reporting an issue)
Benefits of pursuing this approach:
- We will be able to delay the development freeze by 8 days compared to last year
- Reduce the testing cycle by 2 days
- Minimize weekend and holiday work
Testing Phases
Unit Test |
System Integration Test |
- Core team: IS&T Technical & Functional responsibility
- Covers discrete critical transactions and programs
- Goal is to identify glaring catastrophic failures through simple execution of transactions and programs.
- Scripts optional
- List of what was tested is required
- Ensure frequently executed reports and transactions are tested
|
- Core team: Combined IS&T and Business Testers
- Scripts required using current and updated script catalogue (stored in QC)
- Include discrete transactions and programs and/or end-to-end scenarios. End-to-end scenarios must cover discrete tests of critical functions
- Validation consists of validating test results rather than just identifying catastrophic failures
- Cover all critical scenarios or transactions. Also targets functionality and processes that are more likely to be affected by the system updates such as highly customized functions or those which have been affected by prior updates.
- Ensure frequently executed reports and transactions are tested.
|
|
New Automation Requests should be sent to: istqa@mit.edu