-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Create consistency in wording in v2 tests #3559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Create consistency in wording in v2 tests #3559
Conversation
| ## Steps | ||
|
|
||
| 1. Run @MASTG-TECH-0014 on the app and look for insecure random APIs. | ||
| 1. Use @MASTG-TECH-0014 to look for insecure random APIs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please start by reviewing this. The v2 TESTs follow this pattern (where possible/TECH exists).
| ## Basic APK Installation | ||
|
|
||
| Use `adb install` to install an APK on an emulator or connected device. The given path is the path of the APK on the host. | ||
| Use `adb install` (@MASTG-TOOL-0004) to install an APK on an emulator or connected device. The given path is the path of the APK on the host. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fyi: This is a technique. Moved TOOL reference from the TEST to this file.
This PR has the goal to help v2 TEST authors use similar wording, such as here
Create consistency for v2 tests:
Use@MASTG-TECH-0000to look for", where possible. Updated instructions.Please focus feedback on the wording alignment:
useandto look for