Docs: improvements for manual testing

[thekaveman]

Closes #3600

What this PR does

• Refactors the existing Manual Tests page into a series of sub-pages:
  • Getting started
  • Keyboard testing
  • Testing translations
  • Testing self-service
  • Testing in-person
  • QA testing
  • Smoke testing
• Creates a standalone Tutorial for Login.gov sandbox account setup
• Moves 99% of the content from the Benefits smoke testing doc to the docs site (we can now archive this file)

Review

1. Checkout the branch locally
2. Ensure the docs site builds without error
3. Navigate through the local pages, confirm all links work etc.
4. Attempt to hit the previous all-in-one page at /guides/manual-tests/ and be redirected to the new Getting started page

[github-actions]

Coverage report

This PR does not seem to contain any modification to coverable code.

[github-actions]

Preview url: https://benefits-3604--cal-itp-previews.netlify.app

[Scotchester]

Outstanding work! This will be a huge upgrade to our testing docs.

A few more things I'd like to see added eventually (not asking for them in this PR, just a note to selves):

• Testing SSO
• Testing analytics
• Screen reader testing
• QA testing an RC on test (What's generally considered "enough"?)

[thekaveman]

Thanks for the review and suggestions @Scotchester!!

Regarding:

QA testing an RC on test (What's generally considered "enough"?)

I was hoping the table at the bottom here covered that but let me know if you have ideas for how to improve: https://benefits-3604--cal-itp-previews.netlify.app/guides/manual-testing/getting-started/#when-to-test

[Scotchester]

Regarding:

QA testing an RC on test (What's generally considered "enough"?)

I was hoping the table at the bottom here covered that but let me know if you have ideas for how to improve: https://benefits-3604--cal-itp-previews.netlify.app/guides/manual-testing/getting-started/#when-to-test

Hmm, yeah, I suppose it does, but I'm now realizing I didn't connect a dot in my head to this idea when I posted it.

I was thinking about the actual release process and how we execute it, and one thing I thought would be useful to have a couple copyable chunks of Markdown for us to drop into the comments of the release issue, one for QA and one for smoke. The release manager can post it and then people can just check things off with lower risk of edit conflicts as we enter in new lines of what we're testing.

Smoke testing has its own page, so it makes sense for that one to go there, but QA testing doesn't have its own page, so the potential home for that one is less obvious.

[thekaveman]

I thought would be useful to have a couple copyable chunks of Markdown for us to drop into the comments of the release issue

That would be super useful, you are correct! Lemme think on this and amend the PR. Going back to draft for now...

[thekaveman]

Combined the Self-service and In-person pages into a single QA Testing page.

Added markdown snippets of scenarios for QA and Smoke testing for easy copy/paste into the release issue.

[lalver1]

This looks great @thekaveman!! I was following along and I agree with @Scotchester's comments, they were all very helpful. I took one last pass at the final reorganization and it looks good, I like the markdown snippets for the release process issue 👍. I guess the only other thing is that I also tested following links throughout the docs and didn't come across any broken ones.

[angela-tran]

Thanks @thekaveman for bringing these docs up-to-date and also making them much more complete. The guidance on which testing applies when is especially helpful.

I left comments on just some minor things I noticed. This is looking like it'll be ready to merge soon!

[Scotchester]

LGTM! Great work here 👏