You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Testing Overview

  • Two testing phases; Unit and System Integration Testing
  • ALM - Application Lifecycle Management (formerly Quality Center) - Central Repository for all test cases
    https://testcenter.mit.edu:8443/qcbin/start_a.jsp   (use IE only)
  • Quick Test Professional (QTP) - Test automation tool (see attached list below)
  • Issue tracking will take place in RT (see attached RT Tutorial for instruction for reporting an issue)

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 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.
  • SH2 Atlas link:

    https://atlas-test.mit.edu/atlas/Main.action?tab=home&sapSystemId=SH2

 

New Automation Requests should be sent to: istqa@mit.edu

  File Modified
No files shared here yet.

  • No labels