User testing for setup interview 2023/03/28 (user MB)
[x] Top priority: When selecting files to test, user was confused about which types of files to include - only files that run the interview, or all necessary files. This seems to be a common confusion. [handled by #210]
[x] Second priority: #211
[ ] Need the project to be on GitHub
[ ] Name of API key in da UI doesn't matter
[ ] Instruct: Pick "no authentication" from the dropdown
[ ] "Otherwise, ask someone who can get..." <- who to ask? Someone with access to the testing account.
[ ] Not terrible, but folks do feel like they need to keep an old API key around. Maybe also - If you accidentally don't copy it, you can just make a new API key. They're a dime a dozen.
[ ] User did not notice '?' next to Server URL label
[ ] "Operations for you in github" -> "to set up the tests with your permissions"? "Permission from you to do set up GitHub tests"? Maybe get rid of this paragraph (why get rid of it? forgot why I wrote this)
[ ] Confusion about if it needs to be your own token in your account - maybe repos have tokens, maybe you need to get an admin token.
[ ] Token - make a totally new token (tried to use a pre-existing docassemble install one with only 'repo' permissions)
[ ] "Is the token name significant?"
[ ] "Is expiration important? None?"
[ ] Link to docs when not making tests automatically should lead to simple example test. (If you hit 'run' it doesn't error.) (not 'interview doesn't have an endpoint' in the sidebar.) (forgotten what this means)
[ ] "If you have enough permissions (are an admin)" - user asks why it matters and confused by link not showing. Maybe conditionally add you can give this to your admin? Add otherwise will get a page not found error?
[ ] "new branch in the GitHub" -> "new branch named automated_testing". (somewhere we're not naming the branch when we could)
[ ] "follow this link to" - have to be signed into GitHub.
[ ] Confusion between workflow and job. (jobs in a workflow)
User testing for setup interview 2023/03/28 (user MB)