Change Request Management scenario: Working examples “Test” phase
This blog covers the Test phase as part of the working case initiated in SDN blog: Change Request Management scenario: Working examples.
Here you will find also the possible actions and statuses of normal and urgent corrections, when you are in this MC phase.
In this phase:
Release of regular corrections is not possible anymore (code freeze).
During the test phase, errors are detected in the test systems, and are reported to the relevant developers by means of test messages. The developers correct these errors. If all test messages have been closed, the maintenance cycle proceeds to the emergency correction phase.
Urgent corrections can be used as in the previous phase.
Unfinished developments will not be included in the actual test and go-live, they can be included in the next test phase.
This is the suggested test for the set of corrections in this phase:
Correction | User Status | Action | Final User Status | Details |
SDMJ 8000001049 | Created |
|
|
|
SDMJ 8000001046 | In Development |
|
|
|
SDMJ 8000001051 | In Development |
|
| Created SMMK900664 but left empty |
SDMJ 8000001053 | In Development |
|
| SMMK900666, task released |
SDMJ 8000001055 | To be Tested | Confirm Successful Test | Consolidated | SMMK900668, TOC SMMK900680 imported in SMM:200, but not released automatically in this phase, the release is done via task list and also the import to SMM:200 |
SDMJ 8000001057 | Withdrawn |
|
|
|
SDMJ 8000001059 | Consolidated |
|
| SMMK900681, TOC SMMK900683 created and exported Imported in SMM:200 TOC and after SMMK900681 |
SDMJ 8000001061 | Consolidated |
|
| SMMK900684, TOC SMMK900686 and SMMK900687 created and exported Imported in SMM:200 TOC and after SMMK900684 |
SDMJ 8000001063 | Created |
|
|
|
SDMJ 8000001065 | Created |
|
|
|
SDHF 8000001067 | Created |
|
|
|
SDHF 8000001069 | Withdrawn |
|
|
|
SDHF 8000001071 | In Development |
|
| created SMMK900670 but left empty, H000000398 |
SDHF 8000001073 | In Development |
|
| SMMK900672, task released H000000399 |
SDHF 8000001075 | To be tested |
|
| SMMK900674, H000000400, imported in SMM:200, and in SMM:300 import buffer |
SDHF 8000001077 | Successfully Tested |
|
| SMMK900676, H000000401, imported in SMM:200 |
SDHF 8000001079 | Completed |
|
| SMMK900678, H000000402, imported in SMM:300 |
SDHF 8000001091 | Authorized for Import |
|
| SMMK900688, H000000411 "Select Transport Request to be Released" popup for SMMK900688 appears, select it. Import into system SMM :200 |
In this phase you have to test your changes in SMM:200 and create a Test message in case you need to make any correction in these changes, to create a Test Message you can do it from a document if you have included this type of transaction in Extras--> Settings
I click in Test message:
I assigned it to our MC.
Correction | User Status | Action | Final User Status | Details |
SDTM 8000001092 | Created | Take "In Process" | In Process |
|
| In Process | Create Transport Request |
| SMMK900690 |
| In Process | Release Transport Request |
| "Select transport release" popup appears |
| In Process | Pass to "Retest" | To be Retested | IT OPERATOR go to task list to import the TR to SMM:200 |
| To be Retested | Confirm Correction | Confirmed | The tester role cannot be the same as the developer role, see pg 898 from Solution Manager Documentation for EhP1 This TR will get imported into SMM:300 after in Go-Live phase when executing the "Import Transport Request (Background)" in SMM:300 |
With these correction statuses I change the phase to from "Test" to "Emergency Correction":
There are 7 warnings:
Normal Correction 8000001046 still has status 'In Development'
Normal Correction 8000001049 still has status 'Created'
Normal Correction 8000001051 still has status 'In Development'
Normal Correction 8000001053 still has status 'In Development'
Normal Correction 8000001063 still has status 'Created'
Normal Correction 8000001065 still has status 'Created'
Note: In TEST phase don't work at all with your SDMJ corrections, only with SDHF corrections and with SDTM test messages.
Next phase in SDN Blog: Change Request Management scenario: Working examples “Emergency Correction” phase
