[Feature Request] More precise assertation failure information need to be provided

[zhoujingya]

Review Mojo's priorities

• I have read the roadmap and priorities and I believe this request falls within the priorities.

What is your request?

when I worked on #2378, I wrote some test cases, but the assertation failure only told me i failed my test, but I didn't know the error line and column

Unhandled exception caught during execution: AssertionError: condition was unexpectedly False
mojo: error: execution exited with a non-zero result: 1

when we added too many test cases later, I think it was not friendly for our developers to find the precise source code information

What is your motivation for this change?

More precise assertation failure information

Any other details?

No response

[gabrieldemarmiesse]

Stacktraces ❤️

[mikowals]

testing.assert_... functions now print the file and line number when there is a failure. See this commit.

So I think this issue can be closed.

[JoeLoser]

Yep, I'm going to close this issue as we have the source location now plumbed through in the assert functions. Thanks @laszlokindrat for making this happen! Stack traces from Mojo programs are a whole separate beast. Feel free to open a separate GitHub issue for that, but it's well known internally that users would like that.