9021d3f5e1
In #37957, parts of the testing guide were broken out into separate guides. As part of that work, the `<live-example>` tags were also copied to the new guides. These `<live-example>` tags did not specify the targeted example project via the `name` attribute, thus they were implicitly targeting the example with the same name as the guide they were in. See the [Docs style guide][1] for more info. However, there is only one example project (`testing/`) and all `<live-example>` tags were supposed to target that. This worked fine on the `testing.md` guide, but it broke on other guides (which tried to target non-existing example projects based on their names). This commit fixes it by explicitly specifying which example is targeted by the `<live-example>` tags. It also removes the `embedded-style` attribute that has no effect. [1]: https://angular.io/guide/docs-style-guide#live-examples Fixes #38036 PR Close #38038
1.1 KiB
1.1 KiB
Debugging tests
If your tests aren't working as you expect them to, you can inspect and debug them in the browser.
For the sample app that the testing guides describe, see the sample app.
For the tests features in the testing guides, see tests.
Debug specs in the browser in the same way that you debug an application.
- Reveal the Karma browser window. See Set up testing if you need help with this step.
- Click the DEBUG button; it opens a new browser tab and re-runs the tests.
- Open the browser's “Developer Tools” (
Ctrl-Shift-Ion Windows;Command-Option-Iin macOS). - Pick the "sources" section.
- Open the
1st.spec.tstest file (Control/Command-P, then start typing the name of the file). - Set a breakpoint in the test.
- Refresh the browser, and it stops at the breakpoint.
