Releases: openBackhaul/ApplicationLayerTopology
Implementation of ApplicationLayerTopology v1.0.0
Implementation of ApplicationLayerTopology v1.0.0
This release contains,
- implementation of the individual services
- BasicServices and ApplicationPattern specifically implemented for this application
Open Issues
Report timestamp : Friday, 25 November 2022 13:57:36
Total run Duration : 44m 38s
Average response time : 151ms
Total assertions : 4942
Individual Service failures : 143
Basic Service failures : 159
Total failures : 302
Total skipped test : 0
The following table doesnt provide details for the failures in the BasicServices because in version 2 implementation , the generic ApplicationPattern and BasicServices npm package will replace the existing one.
Consistent Issues :
Categories | count | Rootcause | Issue number / further reference |
---|---|---|---|
AssertionError - Response body completeness - Expected /v1/start-application-in-generic-representation | 5 | The datatype "String" changed from capital "S" to small "s" in the version 2 specification. This change is implemented in the server side. And in the version 2 of testsuite this will be included. | Issue will not be observed after updating testsuite to version 2 |
AssertionError - client created? - Expected /core-model-1-4:control-construct | 2 | local id should be in string and not in integer. | This will be resolved in version 2 after making the application to use the ap npm package |
AssertionError - CC client deleted? - reference /v1/list-applications | 1 | Current logic listing the list of application based on the entry available in the network-control-domain/control-construct list entries. | ApplicationLayerTopology/issues/147 |
AssertionError - /v1/update-all-ltps-and-fcs | 9 | "originator" header is considered to validate whether a incoming application is already regarded. This logic needs to be changed. Provided the details in the associated link mention in the next column. | ApplicationLayerTopology/issues/146 |
AssertionError - Service Idempotent? - Expected /v1/update-ltp - service idempotent? | 21 | Same rootcause as above | ApplicationLayerTopology/issues/146 |
AssertionError - Service Idempotent? - Expected /v1/delete-ltp-and-dependents - service idempotent? | 8 | Same rootcause as above | ApplicationLayerTopology/issues/146 |
AssertionError - Service Idempotent? - Expected /v1/update-fc - service idempotent? | 4 | Same rootcause as above | ApplicationLayerTopology/issues/146 |
AssertionError - Service Idempotent? - Expected /v1/update-fc-port - service idempotent? | 4 | Same rootcause as above | ApplicationLayerTopology/issues/146 |
AssertionError - Service Idempotent? - Expected /v1/delete-fc-port - service idempotent? | 4 | Same rootcause as above | ApplicationLayerTopology/issues/146 |
AssertionError - Response body completeness - Expected /v1/list-operation-clients-reacting-on-operation-server | 1 | Two entried created for the /v1/list-ltps-and-fcs for the EATL application. Couldn’t able to reproduce this scenario manually in local. | |
AssertionError - subscriber-operation updated? - Expected/check /core-model-1-4:control-construct | 2 | new operation client is getting created instead of updating existing operaiton client. Issue will be resolved in release 2 | ApplicationPattern/issues/284 |
Inconsistent Issues :
The following issues are inconsistent and will be fixed after supporting ElasticSearch in the EaTL and OL application ApplicationPattern/issues/357,
Categories | count |
---|---|
ExecutionAndTraceLog/core-model-1-4:control-construct | 48 |
Expected ExecutionAndTraceLog/v1/list-records-of-flow | 32 |
Consequent failure due to response-time of control-construct is more than the request-timeout | 2 |
Specification of ApplicationLayerTopology v1.0.0
This release contains:
-
High Level Design
- ServiceList
- ForwardingList
- ProfileList
-
Detailed Design
- OAS
- DATAfile
- Testcases
of the ApplicationLayerTopology Specification v1.0.0 as it will be used for the first version of the TinyApplicationController.
(Since merging into main branch and tagging the release label has been delayed, listed specifications are already containing elements, which will be part of the v2.0.0 implementation.)