browser.toml |
|
1971 |
browser_dbg-features-asm.js |
This test covers all specifics of debugging ASM.js files.
ASM.js is a subset of the Javascript syntax.
Thanks to these limitations, the JS engine is able to compile this code
into machine instructions and execute it faster.
When the DevTools are opened, ThreadConfiguration's `observeAsmJS` is set to true,
which sets DebuggerAPI's `allowUnobservedAsmJS` to false,
which disables the compilation of ASM.js files and make them run as regular JS code.
Thus, allowing to debug them as regular JS code.
This behavior introduces some limitations when opening the debugger against
and already loaded page. The ASM.js file won't be debuggable.
|
3639 |
browser_dbg-features-breakable-lines.js |
|
2856 |
browser_dbg-features-breakable-positions.js |
Cover the breakpoints positions/columns:
- assert that the UI displayed markers in CodeMirror next to each breakable columns,
- assert the data in the reducers about the breakable columns.
Note that it doesn't assert that the breakpoint can be hit.
It only verify data integrity and the UI.
|
10244 |
browser_dbg-features-breakpoints.js |
Assert that breakpoints and stepping works in various conditions
|
4141 |
browser_dbg-features-browser-toolbox-source-tree.js |
This test focuses on the SourceTree component, within the browser toolbox.
|
4092 |
browser_dbg-features-source-text-content.js |
This test focus on asserting the source content displayed in CodeMirror
when we open a source from the SourceTree (or by any other means).
The source content is being fetched from the server only on-demand.
The main shortcoming is about sources being GC-ed. This only happens
when we open the debugger on an already loaded page.
When we (re)load a page while the debugger is opened, sources are never GC-ed.
There are also specifics related to HTML page having inline scripts.
Also, as this data is fetched on-demand, there is a loading prompt
being displayed while the source is being fetched from the server.
|
18682 |
browser_dbg-features-source-tree.js |
This test focuses on the SourceTree component, where we display all debuggable sources.
The first two tests expand the tree via manual DOM events (first with clicks and second with keys).
`waitForSourcesInSourceTree()` is a key assertion method. Passing `{noExpand: true}`
is important to avoid automatically expand the source tree.
The following tests depend on auto-expand and only assert all the sources possibly displayed
|
18349 |
browser_dbg-features-tabs.js |
This test focuses on the Tabs component, where we display all opened sources.
|
3085 |
browser_dbg-features-wasm.js |
This test covers all specifics of debugging WASM/WebAssembly files.
WebAssembly is a binary file format for the Web.
The binary files are loaded by Gecko and machine code runs.
In order to debug them ThreadConfiguration's `observeWasm` is set to true,
only once the debugger is opened. This will set DebuggerAPI's `allowUnobservedWasm` to false.
Then, the engine will compute a different machine code with debugging instruction.
This will use a lot more memory, but allow debugger to set breakpoint and break on WASM sources.
This behavior introduces some limitations when opening the debugger against
and already loaded page. The WASM file won't be debuggable.
|
7013 |
browser_dbg-integration-reloading-compressed-sourcemaps.js |
This runs all integration tests against a test using sources maps
whose generated files (bundles) are compressed.
i.e. bundles are made of a unique line with all sources compressed into one line.
|
713 |
browser_dbg-integration-reloading-uncompressed-sourcemaps.js |
This runs all integration tests against a test using sources maps
whose generated files (bundles) are uncompressed.
i.e. bundles are keeping the same format as original files.
|
696 |
head.js |
eslint-disable no-unused-vars |
3477 |
integration-tests |
|
|