AIP-2 Test, Integration and Demonstration

This page is under development (12 Feb 2009)

This page describes these topics for AIP-2 testing, integration and demonstration

• Overall Test Integration and Demo Plan
• Unit Testing in two phases
• Integrated Testing of Scenarios
• Demonstration Capture and Publication

Overall Test Integration and Demo Plan

An Overall Plan for AIP-2 Test and Demonstration has been agreed by the AIP-2 Participants.

The main elements of the plan are:

1. All resources are Registered: Services and Clients
2. The Testing at service level is Organized around Technology Use Cases
   First, Services indicate they are ready in response to near term call
   Then, Clients initiate and lead testing
   Concentrate testing in two intensive periods.
3. The testing at the demo level is organized around SBA Scenarios
   Build on the use case testing
4. The Demonstrations will be Captured and distributed via multiple methods. 

The main schedule milestones are

• Unit Test phase #1 in February 2009
• Unit Test phase #2 in March 2009
• Integrated scenario testing in April 2009
• Scenario Demo Capture in late April 2009

Unit Testing Plan

Major elements of Unit Test:

• Unit Testing based on AIP-2 Use Cases
• Call for components to be tested will be announced broadly
• Preparation for testing
• All components to complete Use Cases #1 - Register, #2 - Deploy
• Some components may want to exercise Use Case #9 - Test service
• Some components may exercise use case #8 - Deploy workflow
• Clients to initiate testing after servers complete preparation
• Use Cases 3, 4, 5, 6, 7

The main steps of Unit testing are:

Unit testing is organized using the AIP Use Cases (UC),

1. Component providers register their services (UC01), deploy those services (UC02), and optionally utilize the testing services (UC09)
2. Component providers list their components in the AIP-2 Interchange Matrix
3. Client providers test against the listed services focusing on UC03, UC04, UC05, UC06, UC08.
4. Client and server providers resovle any issues identified in testing using the AIP-2 Test Log

For component providers with services to be tested in unit test phase 1, please complete steps 1 and 2 by February 21st. 

Workflow of unit testing in AIP-2

1. Component providers indicate their components are ready to be tested by listing the clients and servers on the AIP Interchange Matrix
2. Clients initiate testing against the servers with two possible results:
1. Everything works, client records that the test is complete and successful in the AIP Test Log - end
2. Testing identifies some issue which is recorded in the AIP Test Log - go to next step
3. Server provider reviews test record with two possible choices: 
1. Provider determines that change cannot be made and updates AIP Test Log - end
2. Provider takes action to change service and updates AIP Test Log - go to next step
4. Client repeats testing
1. Successful retest, no further action,update of AIP Test Log - end
2. Testing identifies an issue, test record extended in AIP Test Log, go to previous step

Preliminary list of Clients for Unit Testing:

• GEO Web Portals: Compusult, ESA, ESRI
• Community Portals: Air Quality (Wash U), Disasters, Biodiversity (IP3) portal, Northrop Grumman portal for disasters
• Application Clients: Titan (ERDAS) for disasters.   

 Scenario Testing

Scenario Testing is based upon the Scenarios developed by the AIP-2 Community Working Groups

The Scenarios are dependent upon the use cases. A matrix shows the relationship between Scenarios to Use Cases

Demonstration Capture and Publication

• Capture workshop May 4-5 Stresa, Italy. Detailed agenda available here
• AIP-1 Videos are here
• PPT template is available here
• Guidelines
• Camtasia Studio 6 preferred (but Camtasia 5 works as well) for Windows
• Camtasia 6 does better job at editing audio separately from video
• Camtasia 6 better at importing and exporting standard MOV files
• For MAC, try IShowU; For Linux, try RecordMyDesktop or xvidcap
• Resolution: 1024 x 768
• Frame rate: Capture at 30 frames per second
• Video format: .MOV or .WMV