This repository has been archived by the owner on Mar 13, 2024. It is now read-only.
Cypress/E2E: Separate TM4J keys for team and enterprise of site statistics #7400
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
furqanmlk
approved these changes
Jan 26, 2021
prapti
approved these changes
Jan 27, 2021
|
@prapti I think we have many cases like this where some test require a license for some TM4J folder. The current convention we have is to remain as is in TM4J and then only organize in Cypress by having the same subfolder structure inside |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Separate TM4J keys for team and enterprise of site statistics