Draft
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.
Description
This pull request updates test and demo documentation to clarify terminology around logging sensitive data, replacing generic terms like "secrets" and "sensitive data" with more precise language such as "authenticators" and "user sensitive data." The changes aim to improve clarity and consistency across Android and iOS test cases and demos.
Android Documentation Updates:
MASTG-DEMO-0006.mdto use "authenticators" (e.g., API keys) instead of "secrets" in both the title and description, and clarified evaluation instructions accordingly. [1] [2]MASTG-TEST-0203.mdandMASTG-TEST-0231.mdtest titles, descriptions, and evaluation criteria to consistently use "user sensitive data" instead of just "sensitive data." [1] [2] [3] [4] [5]iOS Documentation Updates:
MASTG-TEST-0296.mdto refer specifically to "user sensitive data" and updated the corresponding demo title inMASTG-DEMO-0066.mdto focus on authenticators. [1] [2] [3] [4][x] I have read the contributing guidelines.
Guidelines for Pull Requests (you can delete this section after reading):