[go: up one dir, main page]
Scribd
Upload
216 views9 pages

Process Flow - Defect Management

Uploaded by

Santhosh Kumar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
216 views9 pages

Process Flow - Defect Management

Uploaded by

Santhosh Kumar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Process Flow – Defect Management

Process Engineering Group


May 4th 2011

© 2010 Steelwedge Software, Inc. Confidential. 1


Bugzilla
PSSA Ticket
Ticket

QA
Dev Fix
Verification

QA Build to
Testing Client
© 2010 Steelwedge Software, Inc. Confidential. 2
QA Client
PSSA Bugzilla Dev Fix QA Test
Verify Build

1. Client will log the issues by mentioning the problem.

2. Client can also mention the same via a email and SPOC will log in PSSA.

3. SPOC needs to check if the Issue is due to configuration or a real bug.

4. If it’s a Configuration then need to make necessary changes and update client.

5. If Its a Issue then post the same in Bugzilla with details as required and agreed.

6. SPOC should post the issue with complete details on how to replicate the issue.

© 2010 Steelwedge Software, Inc. Confidential. 3


QA Client
PSSA Bugzilla Dev Fix QA Test
Verify Build

1. Client SPOC will post PSSA Issue into Bugzilla with PSSA reference Id.

2. SPOC would mention the steps of replicating the issue.

3. SPOC would be required to mention the URL of client (UAT) build.

4. SPOC need to attach his screen shot of Defect replicate

© 2010 Steelwedge Software, Inc. Confidential. 4


QA Client
PSSA Bugzilla Dev Fix QA Test
Verify Build

1. QA assigned member need to check if the posted Issues is Known.

2. If It’s a known issue then QA member need to initiate a FIX.

3. If It’s NOT a Known Issue then QA need to re-verify on Client and Core Build.

4. If Client version is older than current then QA member need to test on current build.

5. If Posted Issue is resolved on current build then same need to be mentioned to Dev
for service pack.

6. If Issue is replicable in core then QA need to mention Impacted modules / features.

7. QA need to check if any other customer was live on same build and check if Issue is
replicable, If yes Mention the same in Bugzilla for other client FIX.

© 2010 Steelwedge Software, Inc. Confidential. 5


QA Client
PSSA Bugzilla Dev Fix QA Test
Verify Build

1. Based on QA steps Dev will Fix the Issue.

2. Dev will perform Unit testing covering the Impacted modules .

3. Dev will deploy the build to QA .

4. Post QA , Dev will make Service pack and deploy to Client UAT .

5. If another client has the same Issue, Dev would arrange Service Pack to other client
also .

© 2010 Steelwedge Software, Inc. Confidential. 6


QA Client
PSSA Bugzilla Dev Fix QA Test
Verify Build

1. QA assigned member need to check Fix and close as required.

2. QA member would test the impacted module.

3. If Client version is older than current then QA member need to test on current build.

4. QA will test the Fix on Client UAT (Optional if SPOC will perform on UAT).

5. QA would be required to test on all client (Optional).

© 2010 Steelwedge Software, Inc. Confidential. 7


QA Client
PSSA Bugzilla Dev Fix QA Test
Verify Build

Need to finalize by Murali on the process on how build will be


deployed to various client

© 2010 Steelwedge Software, Inc. Confidential. 8


Thank You!

© 2010 Steelwedge Software, Inc. Confidential. 9

You might also like