First - its impossible to understand from specification https://usp.technology/specification/index.pdf what error codes the EUT should send in case of an error if you don't know about usp-test documentation https://usp-test.broadband-forum.org.
Also not for all error codes (for example 7018) the test suite exist.
And also I have several questions about the following tests:
- 1.9 Add message with allow partial true, required parameters fail, multiple objects
In the Test Procedure and purpose of the test we make accent about invalid InvalidParameter required parameter.
But in Test Metrics we expect the error from this range- ‘7010’ (‘Unsupported Parameter’), ‘7017’ (‘Object could not be created’), or ‘7026’ (‘Invalid Path’).
I think it's better to make separate test case for invalid required parameter and invalid object path - because one set of input parameters cannot cover all possible errors.
This also applies to other tests - for example where we may send either the wrong parameter key or the wrong value type.
- 1.10 Add message with unique key addressing in path
After the first reading of the test, it is not so obvious that we must already have a controller on the EUT with a unique EndpointID key, which we must know in advance as part of the test. At least this is not mentioned in the test setup.
Therefore, I propose to add a similar sentence to the Test setup - Ensure that at least one Device.LocalAgent.Controller.{i}. object exists on the EUT, and the instance unique key is known by the traffic generator.
First - its impossible to understand from specification https://usp.technology/specification/index.pdf what error codes the EUT should send in case of an error if you don't know about usp-test documentation https://usp-test.broadband-forum.org.
Also not for all error codes (for example 7018) the test suite exist.
And also I have several questions about the following tests:
In the Test Procedure and purpose of the test we make accent about invalid InvalidParameter required parameter.
But in Test Metrics we expect the error from this range- ‘7010’ (‘Unsupported Parameter’), ‘7017’ (‘Object could not be created’), or ‘7026’ (‘Invalid Path’).
I think it's better to make separate test case for invalid required parameter and invalid object path - because one set of input parameters cannot cover all possible errors.
This also applies to other tests - for example where we may send either the wrong parameter key or the wrong value type.
After the first reading of the test, it is not so obvious that we must already have a controller on the EUT with a unique EndpointID key, which we must know in advance as part of the test. At least this is not mentioned in the test setup.
Therefore, I propose to add a similar sentence to the Test setup - Ensure that at least one Device.LocalAgent.Controller.{i}. object exists on the EUT, and the instance unique key is known by the traffic generator.