Mute OK messages by default
ezyang - January 19, 2008 - 20:11
| Project: | Drupal |
| Version: | 7.x-dev |
| Component: | simpletest.module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active (needs more info) |
Jump to:
Description
While having a full screen of "OK" gives one a nice fuzzy feeling, it's not so great when you've got a single test that has started failing and you now need to find exactly which one it is. I propose, just as the default SimpleTest reporter does, that Drupal's SimpleTest reporter not display passes. Comments?
#1
Hmmm. The only thing is that it's nice to have the context around the fails to know exactly what you were trying to do when whatever it was didn't work.
Maybe a set of "jump-down" links that skip directly to the failures themselves..?
#2
Ok msgs can you give you a trail where exaclty did your test fail if you get a general msg like
[browser] Setting title="!SimpleTest test node! simpletest_y1ouaeAn_E" at [/Applications/MAMP/htdocs/drupalHEAD/sites/all/modules/simpletest/drupal_test_case.php line 204]
You have no idea where this is. I am in favor of partitioning test results even more. ATM we display test results for one test class together. It would help a lot if we would display it separately for every test function in a test class.
#3
+1 for partitioning.
Having an option to hide passes would be nice too.
I sort of miss the ability to have 'neutral' information messages (neither pass nor fail), to ease tracking progress and spot in which part of a test an error happens. Not sure the simpletest framework itself allows that, though...
#4
Simpletest does support partitioning down to function level with paintMethodStart and paintMethodEnd. It shouldnt be too hard to implement.
#5
This has been stagnant for quiet some time. A consensus needs to be reached on this issue.
This isn't a bug report, it is a feature request.
#6
A consensus needs to be reached on this issue.
I don't think it is very useful. I prefer to see context.