1. make test
- Posted by jaygade Feb 26, 2011
- 1335 views
How can we get a good summary from "make test"? Even redirecting the output to a file didn't completely solve the problem for me. The information that I wanted (which tests failed, percentage, etc.) was buried pretty deep in the other output and I wasn't sure if any change which I made was responsible.
Heck, it seemed like it ran some more tests even AFTER printing a summary.
2. Re: make test
- Posted by ne1uno Feb 26, 2011
- 1321 views
How can we get a good summary from "make test"? Even redirecting the output to a file didn't completely solve the problem for me. The information that I wanted (which tests failed, percentage, etc.) was buried pretty deep in the other output and I wasn't sure if any change which I made was responsible.
there is another target, make report that will create a html report, but you have to create $eudir/report directory first or it will fail. with report, you can see exactly which test failed and the output.
3. Re: make test
- Posted by ne1uno Feb 26, 2011
- 1338 views
How can we get a good summary from "make test"?
there is another target, make report that will create a html report
looks like the report target is just in the watcom makefile,
add -log option after eutest in the make test target.
then when the tests are done. the watcom makefile calls this line
$(EUTEST) -process-log -html > ..\reports\report.html
4. Re: make test
- Posted by mattlewis (admin) Feb 26, 2011
- 1259 views
How can we get a good summary from "make test"? Even redirecting the output to a file didn't completely solve the problem for me. The information that I wanted (which tests failed, percentage, etc.) was buried pretty deep in the other output and I wasn't sure if any change which I made was responsible.
Heck, it seemed like it ran some more tests even AFTER printing a summary.
You can also run an individual (or several tests):
$ make test TESTFILE=t_switch.e $ make test TESTFILE="t_switch.e t_literals.e"...etc.
I tend to run the full suite in one terminal, and then follow up tests in another, to see the details, or to see if my code has improved the results. For whatever reason, I've never had success with the log.
Another trick, especially if you're just changing the front end, is to run the test using int.ex or ec.ex, since you don't have to retranslate the front end after each change.
Matt
5. Re: make test
- Posted by jaygade Feb 26, 2011
- 1267 views
Okay, thanks.
Matt, I knew about running one test from our previous discussion in the workflow thread. I just wanted to make sure that I knew which tests I should run individually after making a change.
Although it looks like whatever fails I had last night were (probably) unrelated to my own changes.
6. Re: make test
- Posted by mattlewis (admin) Feb 26, 2011
- 1239 views
Although it looks like whatever fails I had last night were (probably) unrelated to my own changes.
t_net_http.e at least is failing due to changes to example.com. We need to update that test.
Matt
7. Re: make test
- Posted by jaygade Feb 26, 2011
- 1244 views
I had a t_de_math failure which is one thing which made me suspicious. But I think it was only binding, which may be related to the -eudir option.
