solman defect management training

Project SPIRIT

Solution Manager (SolMan) Defect Management Training

2

Agenda

Test Management in the SolMan

Defect Management in the SolMan

Test Management in SolMan

1. ‘Untested’ -> Test Scenario is yet to be started for execution (default).

2. ‘Being Processed’ -> Test Scenario under process of execution cycle.

3. ‘Error: Retest Required’ -> Test Scenario is having critical or road-blocking issue which requires Retest.

4. ‘Ok’ -> Test Scenario is passed without issues.

5. ‘Ok with Reservations’ ->Test Scenario is passed with high / Medium / Low priority issues which do not impact the completion of Scenario testing with work around.

6. ‘Retest OK’-> Test scenario has been retested after the defects were fixed and passed

3

The Test script status should have one of the following values :-


• Logon to the SolMan and execute the Trans Code Stwb_work.

4

Test Management in SolMan – Test Package

• SolMan Project Name: BAC_V2_1• Test plan : Z_TPL_V2.1_EUROPE_ USER_ACCEPTANCE_TEST_CYCLE• The Tester will see the list of Test Packages assigned to his Work list.• The Test Package will be assigned to the group of the Testers who will be validating

the Test cases present in his Test Packages.

5

• The Tester will see the Test Scripts and it’s current status pertaining to the Scenario.


6

• Download the Test Script present in the Test Package for executing the Scenario by clicking on the Test Case Description icon corresponding to the Scenario


7

• The Test Script document will open up in a different window.• Make a copy of the Test Script on the local drive for updating the various

columns in the Test Script Excel.


8

• At the completion of the Test Scenario execution, click on the Status Icon to update the current overall execution status in the SolMan.


9

• Update the appropriate status of the Test Script execution from the options available as shown below.

10



• Click on the Test Note icon shown below to upload the Integration Test Result Document.

• This is the same Test Script excel which is updated with actual results while test execution.

• Test Script needs to be uploaded daily to have the complete status of the Testing by the Scenario owner.

11


• During the test execution, the defects or issues are to be logged by the one of the testers present in the Scenario testing.

• This can be done on behalf of the person who is testing.• To do this, click on the Messages Tab.

12


• Click on the Create Message icon for the Defect

13

Defect Management in SolMan

The Tester will need to fill the following mandatory defect detail fields while creating a defect

Priority.

System Base.

SAP Components.

Category.

Subject.

Short Text giving the brief about the defect.

Long Text giving the description of the defect.

14


The Priority field is based on the Business criticality.

1. Urgent -> Show-stopper issue, cannot execute the Scenario through the Alternate route(P1)

2. High -> Scenario can be executed through alternative path but it is important Business issue which needs to be addressed immediately(P2)

3. Medium -> Scenario can be executed but it is an issue which needs to be fixed so that the Business Scenario works fine(P3)

4. Low -> Scenario can be executed but it is an issue which represents a ‘nice to have feature’ in the Business workflow(P4)

15


1. Q01 – 100 QA Environment for ECC

2. Q31 – 100 QA Environment for BI

3. Q41 – 100 QA Environment for SCM

4. Q51 – 100 QA Environment for PI

5. Q81 – 100 QA Environment for MDM

6. Q91 – 100 QA Environment for SRM

16

The System Base field is based on the QA Environment used fortesting and where the issue or defect occurred.


• The Category field is based on the Process Track of the Issue.

1. OTC ->Order to Cash.

2. PTP -> Procure to Pay.

3. FTS -> Forecast to Stock.

4. ITF -> Inventory to Fulfill.

5. RTR -> Record to Report.

6. Technical -> Technical Team

17


The Subject field is based on the category of the Issue.

1. Interface -> Interface related issue. 2. Technical ->Technical issue which is

not an error due Development.3. Basis/Infrastructure -> Issue due

Infrastructure configuration.4. Authorization/ Security -> Issue arising

due to improper Authorization. 5. Configuration -> Issue arising due to

improper Configuration.6. Development -> Development or

Coding issue.7. Master Data -> Missing Master data.8. DSR-> Issue arising due to Data

migration problem.9. Clarification -> Issue arising due to

improper documentation and requires clarification.

10. Batch Jobs -> For batch job related issues

11. BI reports -> Issues related to BI reports

18


• On click of the new message icon Create Support Message Window pops up.

19


• The Priority field is based on the Business criticality.

20


• The SystemBase field is populated with the Testing System used during the Testing and where issue was detected.

21


• The Reported by field is populated by default with the name of the Tester who is raising the issue.

• This can be modified by changing the name of any other person if the defect is raised on his behalf.

22


• The Category field is populated with the Process Name where the issue was detected.

• The values are six Process Track fields and one more category ‘Technical’

23


24


• The Short text field should have the short description of the issue. • The Long text field should have the detailed description of the issue.

25

• The Attachments tab present in the Support Message window can be used to upload the Screenshots and other details to the defect which can used to analysis the issue.


26

• Click on the save button as shown below after entering all the mandatory fields in the Message.


27


• On creation of the new message, the message number is visible in the Support Message list for the Test package.

• The Screen will show the list of all Message with their current status raised for a given Test Scenario.

28


• When the new message is created, the message status is ‘New’, which can be moved to the ‘Processor Assigned’ after an appropriate Wipro Dev Team member is assigned to the defect.

• This task of assigning the defect to the appropriate Wipro Team member is done by the Wipro Team Lead to fix the issue.

• Once the defect is assigned to the Wipro Team member it can be put in the ‘In Process’ or ‘Rejected’ state.

• Once the defect is in ‘In Process’ state, the defect can be moved to the ‘Message Rejected’, ‘Sent to SAP’ or ‘Solution Provided’ state.

• While moving the defect in ‘Solution Provided’ state the developer will add his comments i.e. a short description of the resolution for the issue along with the Transport request No generated for the Object.

29

New

Processor Assigned

In process User Action

requiredUser

Replied

Solution Provided Rejected

Confirmed

Solution Rejected

Defect Resolution - flow

solman defect management training

Documents