Changes between Version 6 and Version 7 of GENIRacksHome/AcceptanceTests/OpenGENIAcceptanceTestsPlan

Timestamp:

05/23/14 15:00:46 (10 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIRacksHome/AcceptanceTests/OpenGENIAcceptanceTestsPlan

@@ -394 +394 @@
 [[Image(GRAMMultiSiteOpenFlowAcceptanceTest-actual.jpg)]]
 
-''Evaluation Note:'' Test case is described for the original test case, actual procedure will be captures as part of test details available from the [https://superior.bbn.com/trac/bbn-rack/wiki/AcceptanceTestStatus Acceptance Test Status] page.
+''Evaluation Note:'' Test case is described for the original test case, actual procedure will be captures as part of test details available from the Acceptance Test Status page.
 
 
@@ -479 +479 @@
 [[Image(GRAMClickRouterAcceptanceTest-actual.jpg)]]
 
-''Evaluation Note:'' Test case is described for the original test case, actual procedure will be captures as part of test details available from the [https://superior.bbn.com/trac/bbn-rack/wiki/AcceptanceTestStatus Acceptance Test Status] page. The test case will be run within one rack.
+''Evaluation Note:'' Test case is described for the original test case, actual procedure will be captures as part of test details available from the Acceptance Test Status page. The test case will be run within one rack.
 
 
@@ -670 +670 @@
 == Issue Tracking ==
  1. All issues discovered in acceptance testing regardless of priority are to be tracked in a bug tracking system.
- 2. The bug tracking system to be used is the [https://superior.bbn.com/trac/bbn-rack/query?status=accepted&status=assigned&status=new&status=reopened&component=test  OpenGENI trac] using the "test" component.
+ 2. The bug tracking system to be used is the [https://superior.bbn.com/trac/bbn-rack/query?status=accepted&status=assigned&status=new&status=reopened&component=test  Internal GRAM trac] using the "test" component.
  3. All types of issues encountered (documentation error, software bug, missing features, missing documentation, etc.) are to tracked.
  4. All unresolved issues will be reviewed and published at the end of the acceptance test as part of the acceptance test report.
@@ -677 +677 @@
  1. A periodic status update will be generated, as the acceptance test plan is being executed, or as needed.
  2. Periodic (once per-day) status update will be posted to the rack team mail list (gram-dev@bbn.com).
- 3. Upon acceptance test completion, all findings and unresolved issue will be captured in an [https://superior.bbn.com/trac/bbn-rack/wiki/AcceptanceTestReport Acceptance Test Report].
+ 3. Upon acceptance test completion, all findings and unresolved issue will be captured in an Acceptance Test Report.
  4. Supporting  configuration and RSpecs used in testing will be part of the acceptance test report or checked into a specified repository.