feat: make the assertion engine return a different error when no spans #3666
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
jorgeepc
approved these changes
Feb 20, 2024
danielbdias
approved these changes
Feb 20, 2024
mathnogueira
force-pushed
the
feat/assertion-not-matching-error
branch
from
c2652aa
to
5f46d4a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes the assertion engine return the following error when you try to run an assertion against an attribute when no spans match the selector:
Related thread message: https://tracetest-community.slack.com/archives/C06CF48NS79/p1708377604787339?thread_ts=1708367051.955759&cid=C06CF48NS79
Checklist