06. 2025 SP Testing

Two testing phases; Unit and System Integration Testing
ALM is available at https://alm.mit.edu Testers looking to access ALM must use Microsoft Edge browser in IE compatibility mode. They may need to add https://alm.mit.edu to their list of Trusted Sites in Internet Options.
- Instructions for accessing ALM by ALM Client Launcher (recommended) or Microsoft Edge are here: https://wikis.mit.edu/confluence/x/vQGsDg
- Instructions for IE mode in Edge and for adding to the Trusted Sites list are here: http://kb.mit.edu/confluence/x/NafHCQ
Quick Test Professional (QTP) - Test automation tool (see attached list below)
Reporting Issues
- Issues should be emailed to application-support@mit.edu.
- Cc: the SP project manager(s)
- Subject Line - please include the following in the subject line:
  - "Support pack testing 2024"
  - Environment used in testing, e.g. SF2, SH1, SH2
  - Brief description (3-5 words) of issue area

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.

Summary of business unit testing / automated & manual: