Top-level run tests button doesn't always run all tests

[CodeSmith32]

I've noticed that, every so often, I hit "Run All Tests" and it does not run all tests. It runs most tests, but I see a bunch that were skipped.

I have 2600+ tests. A moment ago, I tried running all tests, and only 692 (I believe) tests ran. But it said 692/692, making it appear as if all ran through successfully. Following this, I ran npx vitest and it ran through all 2600+ tests.

Since the tests are collapsed into folders, and since the "skipped" status doesn't propagate upward, I can't even use this extension because I can't trust that it actually ran all tests unless I either know the exact number of tests I have at all times, or unless I manually expand the tree until I see that no leaf node was "skipped", which is tedious for a lot of tests.

Am I just missing some "Don't actually run all tests" option? Or is this a bug?

I wish I could narrow it down to a specific time that this occurs. What I can say is, the computer I'm running these tests on is a bit short on RAM, which may contribute, but should not have the effect of making the extension completely unreliable. i.e., If after clicking "Run All" it fails to actually run all, simply because it can't, I need to at least know it didn't run all, so I can run it again.

[sheremet-va]

Is this the same issue? #772

[CodeSmith32]

Right.. I was about to comment on that one actually.. I decided to post a different discussion for a few reasons:

• Some of my tests do run. They're not all getting skipped.
• Also, I'm hitting "Run all" whereas I wasn't entirely sure what the OP of that discussion was clicking.
• Also, my seems to happen sporadically. I'm not sure it only happens when I restart VSCode, but sometimes it works when I restart VSCode.
• My issue also may be due to low RAM issues..?

In any case, I suppose there's still a chance they're related in some fashion.. I apologize if the above criteria aren't sufficient for a separate discussion.

[sheremet-va]

Seems like there was an update in vscode that broke one of the assumptions this extension made. I need some time to reproduce and figure out the fix

[sheremet-va]

I cannot reproduce this, it seems like the button provides different TestRunRequest based on some conditions, but I don't know what the conditions are

[CodeSmith32]

I'll see if I can get it to happen again so I can report more details here. (It hasn't happened for a bit.)

Until then, I know there's not much that can be done.

Thanks!

[CodeSmith32]

@sheremet-va,

I just reproduced it, and I realize it occured when I hit this button:

 
It may or may not happen when I hit the "Run All Tests" button - I'm not sure:

---

I've updated/corrected the title of this discussion.

In any case, under what conditions does the lower button not run all tests, if all my tests are under that root-level folder? (Which, in my case, they are.)

[sheremet-va]

Thank you, this is a much better reproduction, I can confirm the bug. The "run all" and "run this folder" (which "packages" are in your case) buttons have different resolvers.

[sheremet-va]

This should be fixed in 1.50.2

[CodeSmith32]

Hey @sheremet-va,

I appreciate the update. Unfortunately, I'm not sure it's completely resolved. But what I found seems pretty reproducible.

I checked and I do have version 1.50.2 of the extension. To test the update, I pressed the run button next to "packages", but it stops after finishing "common":

 

I tried pressing run again; I cleared the tests and pressed it again; etc., and it seems to only re-run just tests from "common".
It seems a little different, though. It's not marking the tests as skipped — it's just not running them at all.

On that note, though:

I decided to run the tests in my "shared" package manually, by clicking 'run' for it specifically. Then I cleared tests. Then I ran "packages" again, and it did in fact mark the "shared" package tests as skipped, after a moment of thinking about it while it ran tests from "common":

---

Thanks @sheremet-va! Hope this helps!

[CodeSmith32]

@sheremet-va,

Ok, a little worse of an issue...
Now, additionally, the "run all" button doesn't run any tests. It only marks as skipped the ones that ran from a previous run.

---

Another thing to note, I also just upgraded my Vite / Vitest packages to a little newer versions:
(not latest though, due to other package requirements)

• Vite: 7.3.2
• Vitest: 4.1.4

In the process of doing this, I had to also upgrade my vitest.workspace.ts file to a vitest.config.ts file (since this is a monorepo).

My root vitest.config.ts now looks like this, in case it helps:

import { defineConfig } from "vitest/config";

export default defineConfig({
  test: {
    projects: ["./apps/*/vitest.config.ts", "./packages/*/vitest.config.ts"],
  },
});