Celadon is an open source Android* software reference stack for the Android community to bring ideas to life while developing on the latest Android release and the latest Intel hardware platforms. The following Intel NUC system has been used to validate regular Celadon releases.
Weekly Validation Phase
The weekly validation cycle includes system functional test execution, compliance testing, and KPI based on the defined features of the quarterly program.
- The test plan is created based on the features in the verify/closed state from the weekly release builds. Software criteria are defined at the start of the program, and execution is completed weekly on each domain until the defined software criteria are met.
- The validation team maps & tracks all the test cases against the defined requirements.
- The Validation team will share the consolidated results based on the ask with details on software completion, requirement coverage, defects and system validation results.
Android Validation In-Scope
Android validation is scoped for the following:
CiC and CiV platforms consist of
- Kaby Lake CiC and Comet Lake CiC Pie
- Kaby Lake CiV Android 10
Functional validation of all end to end defined features in JIRA
Non Functional (Compliance/Performance) - based on customer requests
- Performance KPIs list defined
- Compliance testing
Android Validation Out-Scope
- All unit, white-box, and pre-integration testing is owned by the function domain owners. Domain owners must guarantee component level qualification such as Kernel, Debug & Trace, USB, WIFI, and Bluetooth.
- Hardware component and relevant features
- FuSA Certification
Validation Activities Flow
Test Suite and Defect Tracking
System functional testing is executed in a cumulative manner. The weekly functional test suite is focused on features moved to verify state and is validated on weekly releases.
- Coverage for all the features defined. Validation is conducted on internal builds and issues reported are synced to external JIRA.