WGISS-37 Meeting Tuesday April 15 th 2014, 1:00PM CWIC-Smart and CWIC-Start Testing Calin Duma Doug Newman

Agenda CWIC-Start and CWIC-Smart testing approach Why the need for GCMD and CWIC static instances Expectations for static GCMD and CWIC Benefits to GCMD/CWIC and clients URLs of interest 2

CWIC-Start and CWIC-Smart Testing Approach Ruby on Rails web applications Test Driven Development (TDD) and Behavior Driven Development (BDD) using rspec Unit, Continuous-Integration, Partner-Integration automated tests Partner-Integration relies on static CWIC and GCMD Selenium Front-end UI tests interact with local application instance which is configured with static GCMD and CWIC endpoints 3

Why the need for static instances Initial testing used DEV or TEST instances of GCMD and CWIC – Search GCMD for pre-selected datasets and verify response correctness – Search CWIC for pre-selected granules in datasets of interest and verify CWIC response correctness Problems with the above approach: – GCMD dataset inventory is not static – GCMD and CWIC dataset synchronization is not real- time and results in out-of sync datasets GCMD and CWIC static instances with a total of 29 datasets (NASA 14, INPE 7, GHRSST 6 USGS 6) address the issues 4

Expectations for static GCMD and CWIC 5 Availability – Must be the same as PROD and TEST instances – CWIC-Start runs automated tests during development and before deployments Functionality – Full production functionality must be available – Static collection / granule inventory ensure consistent responses and client expectations Performance – Significantly smaller inventory ensures significantly faster responses – CWIC simulates the provider interaction Communication – Uncoordinated changes to static instances will cause significant disruptions and automated client test suite rework AND break the CWIC-Smart and CWIC-Start automated builds – Changes (functional, inventory, availability) to static instances must be discussed and tested beforehand

Benefits to CWIC / GCMD and clients 6 Increased team collaboration and timely feedback – Joint accountability and issue resolution – Coordinated approaches to changes in interfaces / behavior allow for best impact assessment on existing clients Consistent tests executed by CWIC-Start client – Both Success and Error scenarios are executed – Complement internal unit and CI tests – Static instances can serve as pre alpha / beta testing vehicles

URLs of interest 7  GCMD CSW static instance  CWIC CSW static instance  OpenSearch instances coming soon