2 | | = GENI Racks Acceptance Tests = |
| 3 | The GPO has approaches to validate the implementation of the '''[http://groups.geni.net/geni/wiki/GeniRacks GENI Rack Requirements]''': |
| 4 | * [http://trac.gpolab.bbn.com/gcf/wiki/AmApiAcceptanceTests GENI AM API Acceptance Tests] developed by the GPO software group and is to be used by GENI Racks teams to verify compliance to the AM API. |
| 5 | * System Acceptance Plan to validate each GENI Rack solution before broad deployment. |
| 6 | |
| 7 | Please the [http://trac.gpolab.bbn.com/gcf/wiki/AmApiAcceptanceTests GENI AM API Acceptance Tests] page for details on getting and running the the AM API compliance tests. |
| 8 | |
| 9 | The System Acceptance Test Plan validates all major requirements areas for GENI Racks using common acceptance criteria for each validation area: |
| 10 | || || |
| 11 | ||'''Validation planned'''||'''Description'''|| |
| 12 | || || |
| 13 | || Experimenter Acceptance Tests || Validate experimenter requirements are met by Rack|| |
| 14 | || Integration Acceptance Tests || Validate integrated solution meets the GENI Rack requirements || |
| 15 | || Monitoring Acceptance Tests || Validate that monitoring features are production-level || |
| 16 | || Aggregate Owner Acceptance Checklist|| A checklist of items whose existence and access and content is verified || |
| 17 | || Aggregate Owner Acceptance Tests || Validation that GENI Racks are production-ready is initially covered by the Aggregate Owner Acceptance Tests. || |
| 18 | |
| 19 | |
| 20 | =GENI Racks System Acceptance Test Plans == |
| 21 | |
| 22 | Although the acceptance criteria are the same for each of the rack solutions, acceptance test plans were defined for each GENI rack project based on the initial use cases: |
| 23 | |
| 24 | * [wiki:GENIRacksHome/AcceptanceTests/ExogeniAcceptanceTestsPlan ExoGENI System Acceptance Tests] |
| 25 | * [wiki:GENIRacksHome/AcceptanceTests/InstageniAcceptanceTests InstaGENI System Acceptance Tests] |