Comments (1)
Thanks for feedback and suggestions. Can you elaborate what your debugging workflow was like? (I don't know what is/was the "correct" way as I don't use debugger much).
From what I can guess, I suppose you were using "Source > Page" in devtools to pick up source files (which doesn't exist since v1.5.1):
And overall steps would be something like:
- run
vitest (maybe file filter)
withbrowser.headless: false (default)
- wait for tests to finish first run
- on browser, open devtools and find source file and set breakpoint
- on terminal, press "r" to rerun
- browser hits breakpoint
Assuming this is what you were doing, it looks like it's still possible to put debugger
statement directly in test files to replace 3rd step without going through "Source > Page" tabs.
import { expect, it } from 'vitest'
it('basic', async () => {
debugger;
expect(typeof window).toBe("object");
})
Just for a reference, this is what I tested https://github.com/hi-ogawa/reproductions/tree/main/vitest-browser-debugger
from vitest.
Related Issues (20)
- jest-extended lib seems to create duplicates inside JUnit reporter HOT 3
- Components styled with emotion do not get theme from material theme provider HOT 3
- Automatic expect tracking for concurrent tests HOT 3
- Include inspect command (not argument) to be able to debug in command line HOT 1
- Vitest run times very slow on a AWS T3.xlarge instance vs Jest with same configuration
- Type 'ExpectStatic' has no call signatures HOT 6
- Mock module with `import(path)` to be resistant to file renaming HOT 1
- FormData with file is not setting boundary when running in jsdom env HOT 3
- Cannot Alter values of Vi.Mock for different test cases
- Producing unstable snapshots HOT 7
- Fails to run tests with federated module HOT 1
- [jsdom setup] Global APIs not matching HOT 2
- Tests start failing when upgrading from 1.5.2 to 1.5.3 HOT 2
- ``` HOT 1
- The "cause" property of Error is ignored when matching HOT 9
- Unhandled uncaught error fails test run, no stack trace present HOT 2
- Missing input elements from Form event in Submit handler HOT 1
- Type safe assertions HOT 3
- Migrate UI Cypress tests to Vitest Browser Tests
- web-worker search path regression with ES6 wasm module
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vitest.