...
Identified Need | Description | Driver | Dependencies | Project fit | ||
Test Suite | robot test suites executed Consumer driven/broker driven testing framework | |||||
Jenkins Job Flow | ||||||
Autorelease | Trigger daily autorelease job to build all projects together from source | Broker Based Testing | Consumer driven or broker driven testing | |||
Project proposals.[repeat for each project. Note: This is not a complete project proposal skeleton, only sufficient enough for this discussion]
Project 1:Project ID: integration
Project Name:
- Integration
Project Description- Provide
- Provide integration tools and processes for CI/CD of source master and release branches
- Consolidation of common test suites
Scope:
- Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.
...
- the developer will write the test and the integration team provides the framework, but it will be up to individual projects
#question do we test both expected and unexpected inputs
- We should test both.
#question can we consider a consolidation of the test?
- That's the goal of the common integration.
#question do we have a way to leverage localize test environments
- Requires additional work with LF