AP-806 - Update using-integration-for-testing.html.md.erb#448
Open
ImogenCraigmile wants to merge 2 commits intomainfrom
Open
AP-806 - Update using-integration-for-testing.html.md.erb#448ImogenCraigmile wants to merge 2 commits intomainfrom
ImogenCraigmile wants to merge 2 commits intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://govukverify.atlassian.net/browse/AP-806
Why
It isn't necessary to have the test user data to test an authentication only journey, the existing documentation is causing users who do not need the test users to ask for the document. This is creating unnecessary work for the onboarding team to respond so the docs needs changing to accommodate this.
What
Added a line to explain that you don't need the user data for an auth only journey and removed references to it.
Technical writer support
Do you need a tech writer's support, for example to review your PR? Yes please.
How to review
/preview-with-docker.shChangelog
If this change is significant (for example, launching a new feature or deprecating a feature), you should update the changelog found at
partials/_changelog.erbunder the heading 'Documentation updates'.Confirm