31 featuretoggleguard throws error because of missing reflector #46
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
- removed e2e folder and related configurations - migrated tests to integration folder - updated jest config to include integration tests - added VSCode launch configuration for debugging - fixed issue with jest verbose output fixes #31
Coverage reportTotal coverage
Show files with reduced coverage 🔻Reduced coverage
Report generated by 🧪jest coverage report action from 5c559c2 |
rorteg
deleted the
31-featuretoggleguard-throws-error-because-of-missing-reflector
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 Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently, E2E tests are configured as end-to-end tests, but these could be restructured as integration tests, improving speed and simplicity without the need to spin up a real server.
Issue Number: #31
What is the new behavior?
Does this PR introduce a breaking change?
Other information
This PR does not change any application functionality, focusing on improvements to the test structure and tool configuration.