Nothing happens when attempting to run test
See original GitHub issueI click the play button which has a tooltip stating “Run Test” and nothing happens. I assume it’s not running the test, but if it is then there is no visual feedback given.
This is the SvelteKit repository https://github.com/sveltejs/kit. The particular file I have open is packages/kit/test/apps/basics/test/test.js
.
I’m using v0.2.3
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:6 (2 by maintainers)
Top Results From Across the Web
When trying to run tests, nothing happens
When I run a very simple test, nothing happens. And I cannot run anything anymore, since run button is disabled.Here is the test...
Read more >Tests not running in Test Explorer - visual studio
However, the tests are not running when using the Visual Studio test explorer. The Test Explorer is showing all unit tests, but once...
Read more >Nothing happens when I click Run for Web App in test case
This means the installer is trying to replace a file that is currently in use by another program. Close all programs that are...
Read more >Could not run tests on class - Salesforce Stack Exchange
I was not trying to estimate code coverage, just run a single test class. Oddly, I could still view results of individual tests...
Read more >unittest — Unit testing framework — Python 3.11.1 ...
The runner may use a graphical interface, a textual interface, or return a special value to indicate the results of executing the tests....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Most likely you have more than one Playwright config. Use the drop down next to Test and debug actions in the toolbar to select your default configuration.
This is also problematic with the new component testing feature, since it’s now encouraged to have a
playwright.config.js
and aplaywright-ct.config.js
file in your repo to run different tests with different configs.