[Fix] Cannot read property 'type' of null - E2E Tests #850
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
Signed-off-by: evertonlperes <evertonluperes@gmail.com>
|
Fixed base repo on my forked rd :D - closing |
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.
Changes
window/index.tsCreateWindow property in order to force disabledevToolsduring E2E tests (spectron issue relatedPossible root cause
Possible root cause related to the error:
Cannot read property 'type' of nulldevToolsbe disabled in order to avoid crashes when the app starts. Looking into spectron issues,devToolscan be messed when the test framework starts (issues seen on both jest and mocha). More details: Spectron issue 174Image
Local intermittent issue:
s