Testing Overview
Two testing phases; Unit and System Integration Testing
- Application Quality Management(AQM, previously known as ALM) is available at https://aqm.mit.edu. VPN is required to access the service.
- AQM Web Client is compatible with most of the recent web browsers running on Windows or macOS.
- OpenText offers an optional client application for accessing AQM. Instructions for setting up the ALM Client Launcher (also compatible with AQM) are available here.
Reporting Issues
Cc: the SP project manager(s)
- Subject Line - please include the following in the subject line:
- "Support pack testing 2025"
- Environment used in testing, e.g. SF2, SH1, SH2
- Brief description (3-5 words) of issue area
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 catalog (stored in ALM/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.
|
|
Testing Progress - System Integration Test
Summary of business unit testing / automated & manual:
https://releaseengineering.mit.edu/sap_support_pack_test_result_summary.html