Scribd Logo
Upload

Welcome to Scribd!

  • 966 views

    SolMan Defect Management Training

    Uploaded by

    bogusbogus45
    The document provides an overview of test management and defect management in SolMan. It describes the process for executing test cases, updating test statuses, and logging defects. Key steps include executing test scripts, updating statuses to "Ok" or "Retest Required", creating defects with priority, system, and description, and moving defects through statuses like "New", "In Process", and "Solution Provided".

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd

    SolMan Defect Management Training

    Uploaded by

    bogusbogus45
    966 views30 pages
    The document provides an overview of test management and defect management in SolMan. It describes the process for executing test cases, updating test statuses, and logging defects. Key steps include executing test scripts, updating statuses to "Ok" or "Retest Required", creating defects with priority, system, and description, and moving defects through statuses like "New", "In Process", and "Solution Provided".

    Original Description:

    SolMan Defect Management Training

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document provides an overview of test management and defect management in SolMan. It describes the process for executing test cases, updating test statuses, and logging defects. Key steps include executing test scripts, updating statuses to "Ok" or "Retest Required", creating defects with priority, system, and description, and moving defects through statuses like "New", "In Process", and "Solution Provided".

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    966 views30 pages

    SolMan Defect Management Training

    Uploaded by

    bogusbogus45
    The document provides an overview of test management and defect management in SolMan. It describes the process for executing test cases, updating test statuses, and logging defects. Key steps include executing test scripts, updating statuses to "Ok" or "Retest Required", creating defects with priority, system, and description, and moving defects through statuses like "New", "In Process", and "Solution Provided".

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 30
    At a glance
    Powered by AI
    The document discusses test management and defect management processes in SolMan. It covers test script statuses, logging defects, and defect resolution workflows.

    The test script can have statuses like Untested, Being Processed, Error: Retest Required, Ok, Ok with Reservations, and Retest OK depending on the test execution results.

    To log a defect in SolMan, the tester clicks on the Messages tab and fills out the Create Support Message window with details like priority, system tested on, description, attachments, and saves it.

    Project SPIRIT

    Solution Manager (SolMan) Defect Management Training

    Agenda
    Test Management in the SolMan Defect Management in the SolMan

    Test Management in SolMan


    The Test script status should have one of the following values :1. 2. 3. Untested -> Test Scenario is yet to be started for execution (default). Being Processed -> Test Scenario under process of execution cycle. Error: Retest Required -> Test Scenario is having critical or roadblocking issue which requires Retest. Ok -> Test Scenario is passed without issues. 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. Retest OK-> Test scenario has been retested after the defects were fixed and passed

    4. 5.

    6.

    Test Management in SolMan


    Logon to the SolMan and execute the Trans Code Stwb_work.

    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.

    Test Management in SolMan


    The Tester will see the Test Scripts and its current status pertaining to the Scenario.

    Test Management in SolMan


    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

    Test Management in SolMan


    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.

    Test Management in SolMan


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

    Test Management in SolMan


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

    10

    Test Management in SolMan


    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

    Test Management in SolMan


    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

    Test Management in SolMan


    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

    Defect Management in SolMan


    The Priority field is based on the Business criticality.
    1. 2. 3. 4. Urgent -> Show-stopper issue, cannot execute the Scenario through the Alternate route(P1) High -> Scenario can be executed through alternative path but it is important Business issue which needs to be addressed immediately(P2) Medium -> Scenario can be executed but it is an issue which needs to be fixed so that the Business Scenario works fine(P3) Low -> Scenario can be executed but it is an issue which represents a nice to have feature in the Business workflow(P4)

    15

    Defect Management in SolMan


    The System Base field is based on the QA Environment used for testing and where the issue or defect occurred.
    1.
    2. 3. 4. 5. 6.

    Q01 100 QA Environment for ECC


    Q31 100 QA Environment for BI Q41 100 QA Environment for SCM Q51 100 QA Environment for PI Q81 100 QA Environment for MDM Q91 100 QA Environment for SRM

    16

    Defect Management in SolMan


    The Category field is based on the Process Track of the Issue. 1. 2. 3. 4. 5. 6. OTC ->Order to Cash. PTP -> Procure to Pay. FTS -> Forecast to Stock. ITF -> Inventory to Fulfill. RTR -> Record to Report. Technical -> Technical Team

    17

    Defect Management in SolMan


    The Subject field is based on the category of the Issue.
    1. 2. Interface -> Interface related issue. 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

    Defect Management in SolMan


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

    19

    Defect Management in SolMan


    The Priority field is based on the Business criticality.

    20

    Defect Management in SolMan


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

    21

    Defect Management in SolMan


    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

    Defect Management in SolMan


    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

    Defect Management in SolMan

    24

    Defect Management in SolMan


    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

    Defect Management in SolMan


    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

    Defect Management in SolMan


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

    27

    Defect Management in SolMan


    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

    Defect Management in SolMan


    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

    Defect Resolution - flow

    Processor Assigned

    In process

    User Action required

    User Replied

    New

    Rejected

    Solution Provided

    Solution Rejected

    Confirmed

    You might also like