Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SVE Test case 2000 - CoAP POST or CoAP PUT? #574

Open
naveenkumarl89 opened this issue Apr 18, 2024 · 1 comment
Open

SVE Test case 2000 - CoAP POST or CoAP PUT? #574

naveenkumarl89 opened this issue Apr 18, 2024 · 1 comment

Comments

@naveenkumarl89
Copy link

OMA-ETS-LightweightM2M_INT-V1_2-20231003-A:
"6.7.7.1. LightweightM2M-1.1-int-2000" case:
The server must send "CoAP PUT" and "CoAP GET" operations on the "/20/0/4011" resource and receive a response from a client with "2.04 Changed" and "2.05 Content" messages.
The mentioned “/20/0/4011” resource supports only EXECUTE operation and does not support READ or WRITE operations.
So is it “CoAP POST” instead "CoAP PUT" .
Please confirm.

@naveenkumarl89 naveenkumarl89 changed the title Test case 2000 - CoAP POST or CoAP PUT? SVE Test case 2000 - CoAP POST or CoAP PUT? Apr 18, 2024
@sbernard31
Copy link

(I'm not an OMA member)

I also thing there is an issue with this test.

I looked in last OMA-ETS-LightweightM2M_INT-V1_2_1-20240312-C which says :

Test Case Description
Setting the writable Resource LogStart (ID:4011) of Event Log and verifying the triggered actions produce the expected
results

Preconditions
The Client supports the Configuration C.16 as defined in Appendix C
The Client is registered with the Server in indicating the Object ID:20

Test Procedure
A WRITE operation is performed by the Server to update a valid value in the Client in setting the LogStart Resource.
The various Resources of this Event Log Objects MUST be set as expected by the Client.

Normal flow:

  1. A WRITE (CoAP PUT) operation with a valid value is performed by the Server on the LogStart Resource (/20/0/4011)
    of the Event Log Object
  2. The Server READs (CoAP GET) the Event Log Object to get the values of the LogStart (/20/0/4011)

Pass-Criteria

  1. In test step 1, the Server receives the success message "2.04" associated with the WRITE request.
  2. In test step 2, the Server receives the success message "2.05" along with the LogStart Resources values.
  3. In test step2, the queried value of LogStart resource is the same with that in Step1.

But you're right that /20/0/4011 is just an executable resource ...
I looked to all previous version of this object and 4011 was an executable resource from the beginning.

Looking at Appendix C.16 Event Log Configuration 16 :
We can see that a value is expected for this resource and is supposed to be a string (usage of vs) but I can't see any RW string resource in this object... So I Appendix C.16 should probably be fixed too.

{"n":"20/0/4010","v":0 },
{"n":"20/0/4011","vs":"0,100" },
{"n":"20/0/4013","v":3 }
{"n":"20/0/4014","vd":"61-7C-E3-01-C1-11-00-00-05-00-60-18-18-18-0C-00-01-41-06-00-02-00-40-0C-00-00-
00-00"}]

I tried to guess what authors have in mind for this test but I didn't find any clues 😕 (even the test description doesn't help)

Out of topic but an HTML version of OMA-ETS-LightweightM2M_INT with anchor could make easy to refer to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants