Define testing perspective in TEST steps

[Diolor]

From here.
Platforms: both iOS + Android.

The testing perspective (white-box or black-box) must be documented in the instructions (mastg-test.instructions.md) and in the testing steps.

The tester might or might not have access to the source code. This affects the "steps" section.
We should:

1. Account for this in steps in both scenarios.
2. Ensure the RE MASTG-TECH (ios: MASTG-TECH-0065 / android: MASTG-TECH-0013) clearly defines or references any sub-tech or tools used.
3. Document this in mastg-test.instructions.md.

Example (applies to both platforms/wording is indicative):

1. (Optionally) reverse engineer the app // TECH for RE
2. Use TECH-xyz to look for ...

Issue outcome:

1. One template per platform (Android + iOS) for static analysis to account for both white/black box perspectives.
2. Updated TECH docs.
3. Updated TEST instructions.

Out of scope dynamic analysis

[SuyashJain17]

Hi, I’d be happy to work on this if it’s still open.

My plan is to start by documenting the white-box vs black-box testing perspective in mastg-test.instructions.md, then update the relevant RE TECH docs (Android: MASTG-TECH-0013, iOS: MASTG-TECH-0065). I’ll keep the scope incremental and exclude dynamic analysis as noted.

Please let me know if that approach works.

[Diolor]

Hi @SuyashJain17 , thanks for you interest in contributing to MAS! This issue to be successful, requires prior experience in writing few v2 MASTG TESTs. Please check such open issues first especially the ones marked as v1->v2 migration.

PS: Using LLMs alone is not enough and would need your critical experience.

[rishii-19-works]

Hi @Diolor ,

Thanks for opening this issue — it’s a really good point. I went through the description and I agree that clearly distinguishing white-box vs black-box testing perspectives in the MASTG test instructions would make the guidance much clearer for readers.

I’d be interested in working on this and updating the relevant documentation/templates so that both perspectives are properly reflected for Android and iOS testing steps. Before I start, just wanted to check if you have any preferred structure or examples in mind for how these perspectives should be documented.

Looking forward to your thoughts. Thanks!

[cpholguera]

Thanks for the interest @rishii-19-works , we've discussed this internally and the issue is assigned to @Diolor for the time being as this requires a high level of familiarity with the project. Please feel free to explore other issues. Thank you.

[rishii-19-works]

Thanks for the update and for letting me know. I appreciate the clarification.

Understood regarding the assignment — I’ll look into other issues and continue exploring the project.
Happy to help with related areas in the future if needed.

Thanks!