Potential stack trace improvement
- Dominant language
- TypeScript
- Stars
- 210
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Hi! First of all, thank you for the plugin! It works really well.
I have a question/suggestion.
If I use default `cy.request()`, on failure I get this behaviour:
So I could explore stack trace and click on link to go to test scenario.
Using `cy.api()`, seems I miss this opportunity:
Could it be improved somehow?
Best,
Vitali
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the reported failure with both Cypress `cy.request()` and this plugin's `cy.api()` command, using the linked screenshots as the expected comparison. Trace how each command reports failures and determine whether the `cy.api()` stack can expose a clickable link back to the test scenario; done means its failure output provides comparable navigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, typescript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100