Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Issues and Decisions
# | Description | Notes | Decision |
---|---|---|---|
1 | Where to include which CSIT test | ||
2 | How to include the cps-core services available to the client docker-compose | See alternatives in table below |
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.
...
# | 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 |
|
|
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 |
|
|
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. |
CPS Temporal | |||
2.1 | Health Check |
| New |
2.2 | Create an anchor history |
| New |
2.3 | Delete the data node to add it to history |
| New |
CPS-NCMP-DMI_PLUGIN | |||
3.1 | Health Check |
| New |
3.2 | Model-Sync, Write & read data using datastore PassTrough |
| New |