...
Identified Need | Description | Driver | Dependencies | Project fit |
| Test Suite | robot test suites executed | |||
| 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]
...
- Identify baseline code (if any)
Meeting Notes:
#info
...
helen
...
says
...
presents
...
Slidedeck:
...
System
...
Integration
...
and
...
Testing
#info
...
helen
...
says
...
integration
...
team
...
is
...
a
...
helper
...
project.
...
Not
...
have
...
authority
...
to
...
be
...
gatekeeper.
#info
...
we
...
use
...
necus,
...
docker,
...
slack,
...
bitgeria,
...
swagger
#info helen says for open-o, created many test cases
...
- We trigger unit level testing triggered automatically by Jenkins at build time
#question In the microsservice, the broker based testing is getting more popular.
- consumer driven, broker driven
#question who builds the test?
- the developer will write the test and the integration team provides the framework, but it will be up to individual projects