Break up private functions & search menu bugfix #152
Conversation
… is pressed (team to discuss)
| @manual | ||
| Feature: Selection form allows user migration | ||
|
|
||
| Scenario: Allows "Migrate Profile" Button with domain profile, username and password |
There was a problem hiding this comment.
After selecting the profile and inputting the Username, Migrate Profile was enabled even with password remain unchanged and error icon is still on.
This may confuse some users? Should we set it to the green checkmark as default?
| When a domain profile is selected | ||
| And the "Install JCAgent" checkbox is selected | ||
| And a valid "ConnectKey" is pasted in the text field | ||
| And the "Install JCAgent" checkbox is selected |
There was a problem hiding this comment.
Duplicate. Should be Autobind and valid API key
| Given The selection form is opened | ||
| And a domain (local AD or EntraID) user has logged into the device | ||
| When a domain profile is selected | ||
| And a JumpCloud username text "" is specified in the text box |
There was a problem hiding this comment.
| And a JumpCloud username text "" is specified in the text box | |
| And a null/blank JumpCloud username in the text box |
| And a password is specified | ||
| Then the "Migrate Profile" button should NOT become active and be greyed-out | ||
|
|
||
| Scenario: Disallows "Migrate Profile" Button for JumpCloud Usernames that match the hostname |
There was a problem hiding this comment.
Username textbox should have the error icon if the hostname is inputted
|
|
||
| Feature: JumpCloud Username & AutoBind User Validation | ||
|
|
||
| Scenario: Disallows migration for usernames that are not found in the JumpCloud organization |
There was a problem hiding this comment.
Can we not just disable the Migrate Profile button?
| And the "Migrate Profile" button is pressed | ||
| Then a windows form window should appear and warn: The JumpCloud agent is not installed and to also enter your connectKey | ||
|
|
||
| Scenario: Disallows migration for usernames that are not found in the JumpCloud organization |
There was a problem hiding this comment.
Username inputted is not a JCUser. Got same error message as the test above:
There was a problem hiding this comment.
disregard, form shows the correct message
| And a JumpCloud username that does exist in the JumpCloud Organization is specified in the username text box | ||
| And a valid password is specified in the password text box | ||
| And the "Migrate Profile" button is pressed | ||
| Then a windows form window should appear and note that the specified user has a local account username/ can select OK or Cancel to return to selection form |
There was a problem hiding this comment.
Form window seems to not show the right message as seen with the last 2 tests:
There was a problem hiding this comment.
disregard, form shows the correct message
| And a JumpCloud username who has a localUsername field specified (that matches the local user created for this test) that does exist in the JumpCloud Organization is specified in the username text box | ||
| And a valid password is specified in the password text box | ||
| And the "Migrate Profile" button is pressed | ||
| Then a windows form window should appear and note migration can not continue when the specified user has a localUsername that matches a user that exists on the device |
There was a problem hiding this comment.
disregard, form shows the correct message
| And the new local account's default .txt editor should be set to the same application prior to migration | ||
| And the new local account should have the installed Microsoft Store applications prior to migration available | ||
| And the new local account's start menu/ search application (other UWP) applications should be able to be run | ||
| And the logs for the UWP application should be available in the `C:\Users\someNewUsername\AppData\Local\JumpCloudADMU` directory, including the list of FTA/PTA/UWP apps to set and the log recording the actions the UWP app attempted. |
Issues
What does this solve?
build.ps1Is there anything particularly tricky?
How should this be tested?
Additional tests have been written to validate the changes to the selection form. There are three manual test files to check in this release. A number of items have changed in this release we need to validate those changes with the manual test files:
Screenshots