Changes between Version 3 and Version 4 of GENIRacksHome/AcceptanceTests/InstageniAcceptanceTestsPlan
- Timestamp:
- 04/12/12 10:54:32 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/AcceptanceTests/InstageniAcceptanceTestsPlan
v3 v4 5 5 = InstaGENI Acceptance Test Plan = 6 6 7 This page captures the GENI Racks Acceptance Test Plan to be executed for the InstaGENI project. Tests in this plan are based on the [ http://groups.geni.net/geni/wiki/GENIRacksHome/InstaGENIUseCases InstaGENI Use Cases] and each test provides a mapping to the [http://groups.geni.net/geni/wiki/GeniRacks GENI Rack Requirements] that it validates. This plan defines tests that cover the following types of requirements: Integration (C), Monitoring(D), Experimenter(G) and Local Aggregate (F) requirements. The [http://trac.gpolab.bbn.com/gcf/wiki/AmApiAcceptanceTests GENI AM API Acceptance tests] suite covers Software (A and B) requirements that are not covered in this plan. This plan covers high-priority functional tests; InstaGENI racks support more functions than those highlighted here.7 This page captures the GENI Racks Acceptance Test Plan to be executed for the InstaGENI project. Tests in this plan are based on the [wiki:GENIRacksHome/InstaGENIUseCases InstaGENI Use Cases] and each test provides a mapping to the [wiki:GeniRacks GENI Rack Requirements] that it validates. This plan defines tests that cover the following types of requirements: Integration (C), Monitoring(D), Experimenter(G) and Local Aggregate (F) requirements. The [http://trac.gpolab.bbn.com/gcf/wiki/AmApiAcceptanceTests GENI AM API Acceptance tests] suite covers Software (A and B) requirements that are not covered in this plan. This plan covers high-priority functional tests; InstaGENI racks support more functions than those highlighted here. 8 8 9 9 The GPO infrastructure team will perform the tests described in this page and the GPO software team will run the software acceptance tests in cooperation with the InstaGENI rack team. The GPO will execute all of this test plan for the first two InstaGENI racks delivered on the GENI network (InstaGENI Utah and BBN). The InstaGENI acceptance test effort will capture findings and unresolved issues, which will be published in an Acceptance Test Report. GENI operations (beginning with the InstaGENI at Utah) will run a shorter version of the acceptance tests for each subsequent site installed. Issues from site installation tests will be tracked in operations tickets. … … 614 614 = Requirements Validation = 615 615 616 This acceptance test plan verified Integration (C), Monitoring (D), Experimenter (G) and Local Aggregate (F) requirements. As part of the test planing process, the GPO Infrastructure group mapped each of the [ http://groups.geni.net/geni/wiki/GeniRacks GENI Rack Requirements] to a set of validation criteria. For a detailed look at the validation criteria see the GENI Racks [wiki:GENIRacksProjects/AcceptanceTestsCriteria Acceptance Criteria] page.616 This acceptance test plan verified Integration (C), Monitoring (D), Experimenter (G) and Local Aggregate (F) requirements. As part of the test planing process, the GPO Infrastructure group mapped each of the [wiki:GeniRacks GENI Rack Requirements] to a set of validation criteria. For a detailed look at the validation criteria see the GENI Racks [wiki:GENIRacksProjects/AcceptanceTestsCriteria Acceptance Criteria] page. 617 617 618 618 This plan does not validate any Software (B) requirements, as they are validated by the GPO Software team's [http://trac.gpolab.bbn.com/gcf/wiki/AmApiAcceptanceTests GENI AM API Acceptance tests] suite. … … 624 624 = Glossary = 625 625 626 Following is a glossary for terminology used in this plan, for additional terminology definition see the [ http://groups.geni.net/geni/wiki/GeniGlossary GENI Glossary] page.626 Following is a glossary for terminology used in this plan, for additional terminology definition see the [wiki:GeniGlossary GENI Glossary] page. 627 627 628 628 * People: