question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Tests are not running

See original GitHub issue

Describe the bug

It looks like our browser tests are not running

This would explain recent regressions (e.g. https://github.com/sveltejs/kit/issues/2041)

I’m hesitant to merge any PRs until this gets fixed. I’ve added a note to the PR template informing PR submitters of this

Help looking into this issue would be appreciated

Reproduction

If I make the first line throw new Error('this should fail'); the test suite still passes

https://github.com/sveltejs/kit/blob/459efa27a8af5ad51d2a2c3aa8932f91344492cf/packages/kit/test/apps/basics/src/routes/routing/_tests.js#L205

Logs

No response

System Info

`master`

Severity

blocking an upgrade

Additional Information

No response

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:11 (10 by maintainers)

github_iconTop GitHub Comments

2reactions
benmccanncommented, Aug 2, 2021

I just changed it locally back to:

		"dev": "svelte-kit dev",
		"build": "svelte-kit build",
		"preview": "svelte-kit preview"

It doesn’t look like it changes anything. I changed a test so that it should fail and I’m still not seeing any test failures

The reason for changing was so that I could run the test projects myself with pnpm run dev and see what the tests were seeing. I added a line to the readme describing this:

You can run the test server with cd packages/kit/test/apps/basics; pnpm run dev to hit it with your browser.

I think the path is correct as is since the following works:

cd packages/kit/test/apps/basics/
ls ../../../svelte-kit.js
1reaction
sebastianrothecommented, Aug 3, 2021

I also have idea, we should probably set in workflow, that skipped tests must be = 0.

It would be a good idea to use eslint-plugin-jest and enforce the linting in the CI. The plugin does not allow skipping or restricting tests.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Tests not running in Test Explorer - visual studio
All tests are running, all tests are showing the right test outcome. However, the tests are not running when using the Visual Studio...
Read more >
Test explorer not running tests - Visual Studio Feedback
It looks like it is getting ready to run them but then ends with all selected tests in a “Not Run” status. It...
Read more >
How To Resolve Issue Of Test Project Not Running The Unit ...
Two of my test projects didn't run the test cases, it was about to start and took some time to run the test...
Read more >
Tests not running in Visual Studio - Developers Log
Test are showing in the Visual Studio test explorer window, but they are not running: how to solve this issue.
Read more >
Test Not Run Issue - MSDN - Microsoft
After updating my visual studio to latest version, i'm facing this issue. Test Explorer shows test not run message while running tests. I ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found