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

Issues in DIAL server unit tests #26

Open
Rongo-JL opened this issue Nov 14, 2019 · 1 comment
Open

Issues in DIAL server unit tests #26

Rongo-JL opened this issue Nov 14, 2019 · 1 comment

Comments

@Rongo-JL
Copy link

Hi,

We found some issues in DIAL server unit tests

  1. 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.
  2. 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.
  3. 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.

@Hedsw
Copy link

Hedsw commented Oct 9, 2020

We are the same issue on the 6.2.2 Server response.

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