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
{{ message }}
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
This test will first ask the user to turn off the machine, then it will ask the user to turn on the machine. After Powering on the machine, if the test already detects the privet mdns service, it will immediately continue with other test suites (e.g. testDeviceRegistrationNotLoggedIn).
In testDeviceRegistrationNotLoggedIn suite, it will ask the user to accept the registration request popup on printer panel but sometimes this popup wont show since the printer is still starting up due to the first test suite scenario (testDeviceOffNoAdvertisePrivet).
I think there should be a prompt after powering on the machine like "Press enter when the machine is in ready state" and only continue the test suite after pressing the enter button at least in testDeviceOffNoAdvertisePrivet suite to avoid the timing issue on slower printer machines.
The text was updated successfully, but these errors were encountered:
This test will first ask the user to turn off the machine, then it will ask the user to turn on the machine. After Powering on the machine, if the test already detects the privet mdns service, it will immediately continue with other test suites (e.g. testDeviceRegistrationNotLoggedIn).
In testDeviceRegistrationNotLoggedIn suite, it will ask the user to accept the registration request popup on printer panel but sometimes this popup wont show since the printer is still starting up due to the first test suite scenario (testDeviceOffNoAdvertisePrivet).
I think there should be a prompt after powering on the machine like "Press enter when the machine is in ready state" and only continue the test suite after pressing the enter button at least in testDeviceOffNoAdvertisePrivet suite to avoid the timing issue on slower printer machines.
The text was updated successfully, but these errors were encountered: