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
Improve error messages when test programs are bogus #13
Comments
From yanegomi on February 06, 2011 11:48:35 Another case is when the testcase fails via atf_fail and . Compare the former output (snippet): tc-se:+ _atf_run_tc builtins_alias__0:body to the latter (full testcase being run manually via ${testcase}_body; exit $ atf-run info: atf.version, Automated Testing Framework 0.12 (atf-0.12)
The archive attached contains a snapshot of the testcases in the latter case for reproduction. Attachment: sh-testcases.tgz |
From yanegomi on February 06, 2011 19:51:48 Looking back on my experience today, the above comment is a subset of item 3 as this was fed by failing to understand the importance of scope with respect to shell functions (please note the conclusion at the end of the first thread). |
From jmmv@google.com on June 11, 2011 01:54:15 This issue was updated by revision r145 . The improvement of error messages when the test case terminates prematurely |
From jmmv@google.com on June 11, 2011 09:02:16 This issue was updated by revision r147 . This change is required to permit the engine to report nicer error |
From jmmv@google.com on June 11, 2011 09:42:57 This issue was updated by revision r148 . This change addresses part of the problems reported in this ticket. |
From jmmv@google.com on June 11, 2011 09:57:07 This issue was updated by revision r149 . Ensures some error conditions are reported in a useful manner. |
From jmmv@julipedia.org on June 11, 2011 09:57:47 I think the major culprits mentioned by this issue have now been addressed, so closing :-) Status: Fixed |
From jmmv@google.com on February 06, 2011 10:58:44
atf-run's reporting of error messages is suboptimal, and Kyua is still pretty similar to it in this regard. There have been some issues raised recently regarding the error messages reported when we try to execute invalid test programs.
Take a look at: http://mail-index.netbsd.org/atf-devel/2011/02/06/msg000237.html http://mail-index.netbsd.org/atf-devel/2011/02/06/msg000236.html Audit such error messages in Kyua and make them clearer. At the very least:
Original issue: http://code.google.com/p/kyua/issues/detail?id=13
The text was updated successfully, but these errors were encountered: