Support test Core-metadata ver 4.0.1

[kayielt]

I encountered an issue while running the core-metadata automated tests. This is the test report. Could you please advise on how to resolve this issue when running functional tests?
binh@binh ~/T/e/T/u/s/docker ((v4.0))> sh run-tests.sh functional-test false core-metadata no-deployment
report.html

[cloudxxx8]

Please provide the full steps about how you ran the tests.
We are not able to diagnose anything from a screenshot.

[SavantEVO]

First: I cloned the EdgeX Go source code, then checked out version v4.0.1. I customized the build to change the default MessageBus topic from edgex/... to SmartPole/... by modifying the BaseTopic configuration.

Second: I want to test my customized core-metadata service using the automated tests cloned from edgex-taf. I checkout version 4.0.1 then I ran the following command:

sh run-tests.sh functional-test false core-metadata no-deployment
This is result
deploy-base.html
core-metadata-test.html

[cloudxxx8]

I believe there are some changes you need to do in edgex-taf to make sure the test is executed against your customized build.
The first thing in run-test.sh is to get the docker-compose file from edgex-compose
Also, the automation tests currently doesn't support NATS as message bus, because some test script need to subscribe topics to get the data.

@cherrycl Could you provide a direction of how to customize the edgex-taf to test their environment?

[cherrycl]

May I know which services you have deployed? Some services, such as device-virtual, are required for TAF testing.

[SavantEVO]

This is my service currently running. Could you give me some ideas or advice?

[cherrycl]

After reviewing the report and your service list, I have identified two primary issues:

1. Device Creation Failure

   • No device-virtual deployed
   • Get "No REST protocol defined" error. This is unexpected since the device-rest service is already present in your list.

   Please verify that the services have started correctly.

2. Configuration Update Failures
   Several test cases related to configuration updates (e.g., ErrProfileCommandDELETE004) are failing.

   The test attempts to set Writable/ProfileChange/StrictDeviceProfileChanges to true, which should cause the Delete ProfileCommand request to be rejected.

   The rejection is not occurring. This suggests that either the configuration update was unsuccessful or the change did not take effect in real-time as expected.