...
# | Description | Notes | Decision |
---|---|---|---|
1 | Where to include which CSIT test | As CPS has many components and the components interact with each other, the concern on where what test should be included arises. | |
2 | How to include the cps-core services available to the client docker-compose | See alternatives in table below | |
3 | Which images to be used for the CSIT Integration test | As per the team discussion, we discussed on the preference to use the latest image of the component to be tested. Any dependency to be used for the CSIT should be the most recent and stable stage release image. |
Integration Test
Integration tests are used to check how each service works with other services and with external components. They are not concerned with the behavior of each service internally, but focus instead on the communication between services. They can also be used to test external components like databases.
...
- CPS Temporal CSIT test will cover CPS-Core+, CPS Temporal and Event Bus (DMaap) Kafka integration
- DMI Plugin Test will cover Simulator, SDNC,DMI Plugin, NCMP and CPS Core integration
...
# | Description | Notes | Pros | Cons |
---|---|---|---|---|
1 | Each component contains its own docker-compose file listing all the services required for the integration test. Eg : cps-temporal docker-compose would have services from cps-temporal as well as cps-core | As all the services are included in the docker-compose of cps-temporal, CSIT test setup could directly trigger : docker-compose up |
|
|
2 | Each component contains its own docker-compose file with the services required for stand alone testing. Eg: cps-temporal docker-compose only containing services cps-temporal, timescaledb, zoopkeeper and kafka. | As cps-temporal is a client using cps-core, include steps to fetch the docker-compose of cps-core in the cps-temporal setup.sh file in CSIT as shown below: git clone https://github.com/onap/cps.git Combine the docker-compose of cps-temporal and cps while executing 'docker-compose up' docker-compose -f docker-compose.yml -f ../cps/docker-compose/docker-compose.yml up Subsequent files override and add to their predecessors. For the CSIT test cps-temporal docker-compose could override the properties specified in cps-core docker-compose. Eg : if the notification.data-updated.enabled=false by default in cps-core docker-compose. By adding the below code in cps-temporal, these values could be overriden cps-and-ncmp: |
|
|
3 | Create a repo for all the common artifacts like the CSIT, documents. Sub modules could be created for different components inside CSIT to include both the docker-compose and test plan. | Eg: cps-temporal CSIT would combine the docker-compose of cps-temporal and cps-core while executing 'docker-compose up' as below : docker-compose -f docker-compose.yml -f ../cps/docker-compose.yml up |
|
|
The CSIT test for cps-core is executed by jobs : cps-review-verification-maven-master and cps-merge-verification-maven-master.
New CI jobs will have to be created for cps-temporal and dmi-plugin (Ref : ci-management/cps-csit.yaml at master · onap/ci-management (github.com))
Selection of Image for CSIT test:
S No | CSIT component | Image | Decision |
---|---|---|---|
1 | cps-core | cps-and-ncmp | latest |
2. | cps-temporal | cps-temporal | latest |
cps-and-ncmp | most recent stage released stable version | ||
3 | (onap) dmi-plugin | ncmp-dmi-plugin | latest |
cps-and-ncmp | most recent stage released stable version |
Test Plan:
S No | Scenario | Steps | Status |
---|---|---|---|
CPS | |||
1.1 | Health Check |
| Done |
1.2 | CPS Admin Details Insert |
| To Be Updated Get Anchor test to be included in the existing test. |
1.3 | CPS Data Node Insert, Update and Delete |
| To Be Updated Only Steps# 1 and 2 are included in the existing test. Need to all others to the existing test plan. Done |
CPS Temporal | |||
2.1 | Health Check |
| New |
2.2 | Get anchor history |
| New |
ONAP DMI PLUGIN | |||
3.1 | Health Check |
| New |
3.2 | Model-Sync, Write & read data using datastore PassTrough |
| New |
...