Fix an issue when one uses only the PantherTestCaseTrait #303
Conversation
This file contains hidden or 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
dunglas
approved these changes
Feb 23, 2020
Member
|
Good catch! Thanks Alex. |
dunglas
added a commit
that referenced
this pull request
Dec 28, 2020
Fix an issue when one uses only the PantherTestCaseTrait
nicolas-grekas
pushed a commit
that referenced
this pull request
Jan 18, 2021
Fix an issue when one uses only the PantherTestCaseTrait
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
On a project I just use the trait without the full test case, and if so, the
self::CHROMEinstruction throws an error since this constant is defined in the full test case.