MIT SAP Test Request Form Field Definitions

Fields with “(ti)” designation means the information will be used to update the Test Issue Tracking System.

Authorizations – the roles, custom menus, transactions or aliases that testers must be authorized to use. Requires notification to r3-accts of pending test event.

Business Area (ti) – the Institute’s business area owning/implementing the development. Acquire information for the business area matrix, business area abbreviation, process owner destined to approve transports, the business area coordinator (backup to process owner), as well as test issue tracking information.

Business Coordinator – the person who backups up the process owner, assumes the role of resolving business process or test issues and is the backup production transport approver.

Business Process Owner(s) – the business area’s director, manager or stakeholder who will signoff on the test and project development and become the primary production transport approver.

Comments – other test information such as test preparation dates. The type of preparation needed of tables, cases, master data, and etcetera.

Dependencies – other development that may be affected, environment preparations, other business areas that participate in the business process, are dependent on some aspect of the output, may be needed to validate or perform a step in the test process.

Is Application/Transaction - Web, Gui or Both – will tests be required in the SAPgui, the web or both. Is the development a new business application or a series of transactions?
Note: web development necessitates three test types: functional, usability and accessibility.

Is Impact: Institute-wide, Business Area(s) or Both – the development will be used by a majority of the Institute’s employees, by a specific business area staff, or used by both.
This helps determine the type of tester we must solicit. For example, ESS would be Institute-wide, Research Billing would be Business Area (Sponsored Research) and Journal Vouchers would be Both.

Issue Lead (ti) – the person managing the test issues and working with the developers and quality assurance analyst.

Lead Developer (ti) – the person leading the abap or web developers regarding the application development. This person assumes the test issue role of responsible person for test issues.

Project Lead – Name of person leading the project team

Project Name (ti) – Project Intersection Communication Name

Production Target Date – when is this development due in the Production environment (month and year); for example, end of month October 2003.

Proposed Test Dates – the test dates for announcements, calendars, reservations, and solicitation of testers.

Purpose of Project – a brief description the business process development within SAP and whether this is new development, another phase of an approved project, or a redesign effort. For example: development for Human Resources business process to allow employees to make personal tax exemption changes via a web screen.

Test Environment –the SAP environment to be used for the test.

Test Goal – briefly describe the test’s purpose, expectations and objectives. During the meeting this discussion encompasses high risks and the acceptance criterion. For example, test that a big daily feed file will process, stop and restart if the program is interrupted.

Test Location – physical place where the majority of the test will occur. Reservations are required for all locations, except business areas.
W89 – for integration and some project tests, especially when isolation or multiple platforms/operating systems are needed
W92 – HR-Payroll project room is available for project tests
Other – business area, N42 Test Lab, NE49 Training Center, ATIC lab or another campus location

Test Type(s) – identify the type of test the development requires. (Examples: functional, integration, infrastructure, usability, accessibility or a customized test methodology.)

Trainer – the person creating and performing the training sessions.