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

Document the order in which assertions are reported on test failures #1036

Closed
Evalir opened this issue Nov 3, 2023 · 2 comments
Closed

Document the order in which assertions are reported on test failures #1036

Evalir opened this issue Nov 3, 2023 · 2 comments
Labels
A-forge Area: forge good first issue Good for newcomers T-enhancement Type: enhance existing docs

Comments

@Evalir
Copy link
Member

Evalir commented Nov 3, 2023

In most test frameworks, the first test assertion to fail is the one reported. In foundry, the last test assertion to fail (that comes from DSTest or cheatcodes) is the one to be reported. This should be documented in a "debugging with foundry" or existing suitable section.

@Evalir Evalir added T-enhancement Type: enhance existing docs good first issue Good for newcomers A-forge Area: forge labels Nov 3, 2023
@ATREAY
Copy link
Contributor

ATREAY commented Nov 7, 2023

Hey @Evalir, is it okay if I work on this issue if it's available? Also, can you confirm if the page I've linked below is the right place to add this information, or should it go somewhere else?

Debugger

@Evalir
Copy link
Member Author

Evalir commented Feb 8, 2024

Closed by #1058

@Evalir Evalir closed this as completed Feb 8, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Foundry Book Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-forge Area: forge good first issue Good for newcomers T-enhancement Type: enhance existing docs
Projects
No open projects
Status: Done
Development

No branches or pull requests

2 participants