Refactoring DataLayer Validation Scenarios for Modularity #2062
Conversation
This file contains 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
scottqueen-bixal
approved these changes
Jan 22, 2025
scottqueen-bixal
deleted the
1982-refactor-datalayer-cypress-scenarios
branch
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.
PR Summary
This PR focuses on refactoring Cypress test scenarios related to dataLayer validation to enhance modularity, maintainability, and readability. The changes encapsulate repetitive logic into reusable utility functions and streamline the structure of the test cases, ensuring consistency and reducing redundancy.
Related Github Issue
Detailed Testing steps
cd benefit findernpm run dev:storybookcy:run:e2eand verify dataLayer and all other test pass