You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
launchApplicationInRunningStateWithPayload:
-> In 6.2.2 Server response, the table shows the return code should be 200 OK if the application is running and the new provided argument passed to the running application successfully. However, the test expects 201 Created.
launchApplicationInRunningStateWithNoPayload:
-> If the application is running and the message body is empty, the dial server should return 200 OK in the table in 6.2.2. But the test expects 201 Created as well.
sleepTheSystemWithNoKeyWhenItIsRequired
-> Once the device sleeps, the test code doesn't wake it up for the later test cases by sending a magic packet through WoL/WoW. Therefore, the later test case can't be run because the device is sleeping.
Could we have your idea about these issues?
Thank you.
The text was updated successfully, but these errors were encountered:
Hi,
We found some issues in DIAL server unit tests
-> In 6.2.2 Server response, the table shows the return code should be 200 OK if the application is running and the new provided argument passed to the running application successfully. However, the test expects 201 Created.
-> If the application is running and the message body is empty, the dial server should return 200 OK in the table in 6.2.2. But the test expects 201 Created as well.
-> Once the device sleeps, the test code doesn't wake it up for the later test cases by sending a magic packet through WoL/WoW. Therefore, the later test case can't be run because the device is sleeping.
Could we have your idea about these issues?
Thank you.
The text was updated successfully, but these errors were encountered: