Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

experiment: special tracing view for API testing #32689

Closed
wants to merge 3 commits into from

Conversation

Skn0tt
Copy link
Member

@Skn0tt Skn0tt commented Sep 18, 2024

In #19177, lots of folks are asking for improvements to debugging API Tests. We show pretty much all they ask for in the UI, but a lot of the screen space is taken up by browser-specific UI that's simply irrelevant to API testing. This PR demonstrates what a special-purpose "API Testing View" could look like. Instead of the snapshot viewer, it shows request details front-and-center, and it hides the inspector and console tabs.

This comment has been minimized.

This comment has been minimized.

Copy link
Contributor

Test results for "tests 1"

9 failed
❌ [chromium-library] › library/trace-viewer.spec.ts:900:1 › should open two trace files
❌ [chromium-library] › library/trace-viewer.spec.ts:900:1 › should open two trace files
❌ [chromium-library] › library/client-certificates.spec.ts:237:3 › fetch › should fail with matching certificates in legacy pfx format
❌ [chromium-library] › library/client-certificates.spec.ts:602:3 › browser › should fail with matching certificates in legacy pfx format
❌ [chromium-library] › library/trace-viewer.spec.ts:900:1 › should open two trace files
❌ [firefox-library] › library/trace-viewer.spec.ts:900:1 › should open two trace files
❌ [chromium-library] › library/trace-viewer.spec.ts:900:1 › should open two trace files
❌ [playwright-test] › babel.spec.ts:135:5 › should not transform external
❌ [webkit-library] › library/trace-viewer.spec.ts:900:1 › should open two trace files

35492 passed, 659 skipped
✔️✔️✔️

Merge workflow run.

@pavelfeldman
Copy link
Member

Closing this PR as stale, let's open an issue and track proposal there (please attach screenshots if any)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants