This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
CalmHome
>
DefectScenario
(01 Sep 2009,
SteveSpeicher
)
(raw view)
-- Main.CarolynPampino - 05 Dec 2008 ---+ Defect Scenario This scenario identifies the resources that are related to a defect. ---++ Scenario Here is the scenario without roles. 1 A build is <a target="_blank" href="QmHome" title="QmHome">deployed</a> to a configured <a target="_blank" href="QmHome" title="QmHome">test machine</a> (physical or virtual) 1 <p>A [[QmHome][test]] is executed </p> * Test fails (continue) * Test passes (if verifying a defect, close it. Otherwise stop) 1 A <a target="_blank" href="CmResourceDefinitionsV1" title="CM Resource Definitions">defect</a> is submitted (Change Request type=defect) 1 <p><a target="_blank" href="CmResourceDefinitionsV1" title="CM Resource Definitions">Defect</a> is triaged</p> * Fix defect (continue) * Don't fix it (stop) 1 A <a target="_blank" href="ScmHome" title="SCM Home">change set</a> is delivered to fix the defect 1 <p>The build executes. </p> * Build passes (continue) * Build fails (stop) 1 The build ID captures the build status & identifies links to additional information about the build (location of the physical bits, the Bill Of Materials). 1 Team members are notified. (feeds, monitoring the build id etc) * The build ID is referenced along with the BOM to determine what changes are included in the build * Start at 1 *Pre-conditions:* * The test configuration is defined. The test machine is 'configured' correctly. * A build definition exists (build scripts, build machines, any automation to occur etc.) * The scenario assumes this is a funded software development project with the scenario occuring in the context of the project. *Post-conditions* * Defect record is closed, contains history of what build it was 'found in' and what build it was 'fixed in' * Test execution passes. * Source code contains the fix. *Alternatives:* Defect found in production. Steps are very similar, however the triage process is likely to be different and identification of production resources are needed--- e.g. found in this application running on this configuration in production. Defect found by user in the field. Again, similar, but the system will have less control over the deployment, configuration, machine resources. Likely defect is triaged to the 'next version' of the application. ---++ Resources <img width="625" alt="Resources related to a Defect" src="http://open-services.net/pub/Main/DefectScenario/Defect.gif" title="Resources related to a Defect" height="380" />
Attachments
Attachments
Topic attachments
I
Attachment
Action
Size
Date
Who
Comment
gif
Defect.gif
manage
10.8 K
05 Dec 2008 - 21:19
CarolynPampino
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r7
<
r6
<
r5
<
r4
<
r3
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r7 - 01 Sep 2009 - 20:05:49 -
SteveSpeicher
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use
Ideas, requests, problems regarding this site?
Send feedback