Mobile: Best Practices for E2E Mocking Strategy Documentation #109
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.
PR Description
This PR adds a document called
mobile-e2e-mocking.md
. It covers:Purpose of Mocking: How mocking helps test components under specific conditions, like network issues.
File Structure: A proposed layout for organizing mock tests separately from E2E tests, highlighting the importance of E2E for overall app functionality.
Implementation Changes: Notes that our mocking approach will evolve as we add more tests.
E2E Testing: Stresses that E2E testing remains essential to ensure the app works for end users.
This document aims to help the team with better testing practices.