-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update jest editor version #1
Closed
Closed
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
* Adding option to choose where debug output is sent * Bumping version number to 0.1.3
…s, setting test results on load (#23) * Making "run" use getTestId, refactoring mapJestAssertionToTestInfo to use getTestId to ensure both use the same name, add yarn.lock * Ran Prettier/ESLint on all files to improve readability * Changing test list to use a tree view same as folder structure * Setting run status on load * Removing yarn.lock in favour of using npm * Ran Prettier/TSLint on all files * Putting mapJestAssertionToTestInfo back into test parameter * Fixing rtbenfield/csvode-jest-test-adapter #29, allowing double quotes in test names # Conflicts: # src/helpers/mapJestToTestAdapter.ts
* Changing loadTests to use parser instead of initial test run * Updated dependencies and added rythos42 as a contributor * Fixing TSLint issue * Updating TestLoader to only return IParsedResults, using that to build tree view on load
Fixed helper method to choose correct jest binary to run based on platform (only Windows tested). Correctly load Jest config in use to find correct tests. Fixed some warnings about configuration value access.
Bumped dependency versions.
Re-implement algorithm
Feature/nested describe blocks
Updated package info for new repo. Updated publisher to correct value Added ts-jest to compile TS tests and updated dummy test to invoke production code to try to fix test coverage.
Feature/ci unit tests
Correct an access to property of null value.
Improved support for workspaces. By changing the debug target from js script to launcher in .bin directory, we rely on the installed location of jest. Note: workspace users still need to list jest as a devDependency in package.json
Co-authored-by: Ross Knudsen <rossknudsen@gmail.com>
…e-directory-structure Fix #79 | Add "Flatten Tests in Explorer" option
Support workspaces
make tsconfig optional for Nx
by checking jest is installed in package file
…roject Fix Standard parser checking if jest is available
Jest setting testRegex string or string[] handling
Project manager memory leak
Sorry, sent a PR to the wrong repo. |
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.
Related to kavod-io#26
It is said the the latest version handles parametrised tests properly.
As far as I can see by my tests, it does not fixes the problem in #26 out of the box. But since I've already updated it, decided to make a PR.