Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upCommands UI assert errors should clearly delineate integers from strings. #25
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Could this be a first-timers-only issue? |
This was referenced Oct 31, 2019
Closed
This comment has been minimized.
This comment has been minimized.
The code for this is done in cypress-io/cypress#5619, but has yet to be released. |
1 similar comment
This comment has been minimized.
This comment has been minimized.
The code for this is done in cypress-io/cypress#5619, but has yet to be released. |
This comment has been minimized.
This comment has been minimized.
Released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The ASSERT error (in red background) on the commands UI does not signify whether my value is a string or not. The AssertionError (in yellow background) more clearly defines my error (that the integer 25 does not equal "25").
Example

To reproduce: