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
Right now when we filter by pattern, any test in any file (and any workspace) will run: for example, the list displayed in the CLI may be interpreted to run the selected test.
This proposal is about allow run tests or suites in the UI and from CLI, and so, we will need:
expose runById in the core
expose runById in the rpc
add x to the CLI: will show a list of tests and suites matching a pattern: similar to t but for running the test or suite by id
update UI to use runById (right now using pattern)
I will try to send a PR to include the runById logic to the core, later we can iterate adding the new stuff to the RPC, CLI and the UI.
We have this draft PR #6405 introducing an overhauled public API.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Right now when we filter by pattern, any test in any file (and any workspace) will run: for example, the list displayed in the CLI may be interpreted to run the selected test.
This proposal is about allow run tests or suites in the UI and from CLI, and so, we will need:
runById
in the corerunById
in therpc
x
to the CLI: will show a list of tests and suites matching a pattern: similar tot
but for running the test or suite by idrunById
(right now using pattern)I will try to send a PR to include the
runById
logic to the core, later we can iterate adding the new stuff to the RPC, CLI and the UI.We have this draft PR #6405 introducing an overhauled public API.
related #6641 #6649
Beta Was this translation helpful? Give feedback.
All reactions