Build Test Plan and Execute on the Source System
Build Test Plan and Execute on the Source System
144
The migration process and tools are designed for the target system to perform the same functionality as the source system.
To that end, it is recommended that you build a test plan and execute on the source system, with the results recorded as a reference. The test plan should include goals, data set used, action and results data, and output from the View Submitted Task (VST) and system logs. The results on the target system should be the same as on source system with the following exceptions:
- Changes in functionality in the Symantec IGA core products as documented in the release notes of the target system and any interim versions between the source and the target systems.
- Changes in the underlining OS, supported database or Java versions.
To provide best results, the test plan baseline should be created in the production environment, and the migration process should use the production system as the source system.
Given is a sample test plan.
Item | Description | Notes |
|---|---|---|
Use Case / Test Case ID | A unique ID for the Use Case / Test Case | Reference design / SIS use case ID, if available |
Description | Goal of the use case | Short (one or two paragraphs) |
Actors | Participants in the use case | Include
|
Prerequisites | What actions or actors are required for Use Case / Test Case | |
Main Walkthrough | List the steps of the use case |
|
Variations Walkthrough | List possible variations (if any) for the use case |
|
Example Test Plan Results
:Use Case / Test Case ID | Variation | Result |
|---|---|---|
UC-01 Contractor Onboarding | <none> | |
UC-02 Employee Onboarding | Pre hire | |
UC-02 Employee Onboarding | Same day |