Dotnet test hangs in Cursor – how to skip or improve test execution feedback?

Discussions
1

I’m encountering an issue where running dotnet test via Cursor’s inline interface causes the UI to hang indefinitely. Here’s what I’m doing:

image
image1574×350 4.97 KB

  • The test environment is a .NET 8 C# game server project.
  • Tests do run correctly in the background, but the Cursor interface shows a “Running…” screen and doesn’t return.
  • I have to manually click “Skip” in the bottom right every time, which is not ideal for workflow efficiency.

What I’ve tried:

  • Adding --verbosity minimal to reduce output size
  • Running tests via terminal manually (which works fine)
  • Checking if it’s caused by long-running tests (not the case)

My question:

  • Is there a way to make Cursor auto-skip or fallback gracefully after a few seconds of test inactivity?
  • Or, could we disable the inline test feedback and just use the terminal output instead?

Would love any tips, workarounds, or if this is a known issue already.

Thanks in advance!

1 Like