TestSuite Implementation of RegistryOffice v1.0.0

TestSuite Implementation of RegistryOffice v1.0.0

This release contains testcase collections ,

• for all the of the individual services
• for the individual OAM services
• that checks functionalities of all services and the expected behavior of forwardings across applications
• load file that provides initial configuration information which can be utilized to validate the initial configuration of the server database

Implementation of RegistryOffice v1.0.0

Implementation of RegistryOffice v1.0.0

This release contains,

• implementation of the individual services
• BasicServices incorporated from npm package onf-core-model-ap-bs+1.0.1
• Application pattern framework incorporated from npm package onf-core-model-ap+1.0.1

Open Issues

Report timestamp : Thursday, 17 November 2022 16:32:51
Total run Duration : 55m 25.7s
Average response time : 103 ms
Total assertions : 2762
Total failures : 148
Total skipped test : 0

Consistent Issues :

Categories	count	Rootcause	Issue number / further reference
AssertionError - Expected /v1/bequeath-your-data-and-die - incorrect new-application-name attribute	1	For incorrect application-name , server is not processing the request. This behavior is fine. But the response code should be 400 instead of 204.	RegistryOffice/issues/195
AssertionError - BequeathingDataAndDieCausesForwardings - reference OldRelease/core-model-1-4:control-construct	1	OldRelease IP not configured in the application and resulting in request timeout. Issue will be resolved after including "old-release" information in the embed-yourself callback in registry-office.	RegistryOffice/issues/108
RangeError - BequeathingDataAndDieCausesForwardings - sampling /v1/bequeath-your-data-and-die	1	OldRelease IP not configured in the application and resulting in request timeout. Issue will be resolved after including "old-release" information in the embed-yourself callback in registry-office.	RegistryOffice/issues/108
AssertionError - BequeathingDataAndDieCausesForwardings - sampling /v1/bequeath-your-data-and-die	1	The application request body received is with "undefined" values. Server is not processing the request.	Issue will not be observed after updating testsuite to version 2
AssertionError - Response body completeness - Expected /v1/start-application-in-generic-representation	4	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 - Response body completeness - Expected /v1/list-applications	16	IP address in the testsuite load file and the server side Config file are different. This issue will not be observed after including the fake-ip-address script in both server as well as testsuite load file.	ApplicationPattern/issues/247
AssertionError - Response body completeness - Expected /v1/list-applications-in-generic-representation	12	IP address in the testsuite load file and the server side Config file are different. This issue will not be observed after including the fake-ip-address script in both server as well as testsuite load file.	ApplicationPattern/issues/247
AssertionError - notify-deregistration - subscriber-operation updated? - Expected /core-model-1-4:control-construct	1	When provided in the unexpected format (i.e.) without starting with a version number , the new subscriber-operation is creating a LTP instead of updating the existing operation-client's operation-name.	ApplicationPattern/issues/284
AssertionError - Response body completeness? - Expected /core-model-1-4:control-construct	28	This consists of 3 categories of issues ,9 - mismatch in ltp and fc uuids are not in sync between the one in the testsuite load file and the server side load file. But the issue is because of the local-id : 000 repeated 3 times in the OperationUpdateBroadcast , ServerReplacementBroadcast ForwardingConstruct. 10 - mismatch in the IP address between load file in testsuite and server. Part of fake IP address this will be fixed. 11 - new operation-client creation updating new operations without the proper versioning creates new LTPs instead of updating existing.	mismatch in ltp and fc uuids - RegistryOffice/issues/9 , mismatch in the IP address - ApplicationPattern/issues/247 ,new operation-client creation - 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
Error - Request notified? - reference OamLog/core-model-1-4:control-construct	1
AssertionError - Request notified? - Expected OamLog/v1/list-records-of-application	1
ExecutionAndTraceLog/core-model-1-4:control-construct	32
Expected ExecutionAndTraceLog/v1/list-records-of-flow	49

Specification of RegistryOffice v1.0.0

This release contains:

• High Level Design

  • ServiceList
  • ForwardingList
  • ProfileList

• Detailed Design

  • OAS
  • DATAfile
  • Testcases

of the RegistryOffice 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.)