You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove default of merging CLI options with .typed-test.ts configs
Add --config, -c CLI flag for path to Config
-c by itself should default to .typed-test.ts
Re-run tests when their dependencies change
Remove metadata from browser test results to decrease payload size
Support running many browsers in parallel
Keep browser open in watch mode to live-reload updated tests
Investigate tsquery as a way to simplify static analysis
Integrate and rebuild the vscode extension to be readable 😄
Add --onWatch cli flag to call another cli with the files that changed
The latest version of @typed/test that have had some vscode extension support has been in use pretty heavily by myself over the past month or more. While I'm very happy with things now they could be better. With this next version I want to increase memory efficiency across the board, especially in watch mode. A big part of that will be re-architecting things to be able to re-use resources rather than constantly spinning things up and tearing them down.
I had the idea of maybe doing some form of test "linting" to maybe warn of possible errors in your tests. The only cases I can think of currently is not using done() in an asynchronous test, or forgetting to return a promise, and not using an assertion (which fails anyways).
The text was updated successfully, but these errors were encountered:
-c
by itself should default to.typed-test.ts
--onWatch
cli flag to call another cli with the files that changedThe latest version of @typed/test that have had some vscode extension support has been in use pretty heavily by myself over the past month or more. While I'm very happy with things now they could be better. With this next version I want to increase memory efficiency across the board, especially in watch mode. A big part of that will be re-architecting things to be able to re-use resources rather than constantly spinning things up and tearing them down.
I had the idea of maybe doing some form of test "linting" to maybe warn of possible errors in your tests. The only cases I can think of currently is not using
done()
in an asynchronous test, or forgetting to return a promise, and not using an assertion (which fails anyways).The text was updated successfully, but these errors were encountered: