Open Bug 1189456 Opened 4 years ago Updated 4 years ago

Mochitest should alert you if the test you're running is disabled

Categories

(Testing :: Mochitest, defect)

defect
Not set

Tracking

(Not tracked)

People

(Reporter: mconley, Unassigned)

Details

My intern just burned a bunch of time trying to fix a newtab test that ended up being disabled for the platform for reasons not related to the patch she had written (which she assumed had broken the test).

I find it mildly surprising that we allow a user to run a disabled test.

At the very least, I feel like we should inform the dev running the test locally that the test has been disabled (and print out the reason / bug # from the .ini file).
I think we explicitly allowed this somewhere when running a single test, because we assumed that developers were intentionally trying to run that test. We should definitely try to make it clearer that you're doing something odd though. I don't know what we can do there, anything we put in the log is likely to just be lost in the spew.
Maybe after the test run:


#####################################################################
#                                                                   #
# Note: This test is currently disabled for this platform!          #
#                                                                   #
# We went ahead and ran this test for you because you asked for it  #
# explicitly, but it doesn't normally run in automation for the     #
# following reason:                                                 #
#                                                                   #
# "disabled until foo-bar-baz works in e10s - bug 15223125"         #
#                                                                   #
#####################################################################

Or variations on that wording. *shrug*
Hi,

I'd like to work on this bug !

Thanks.
You need to log in before you can comment on or make changes to this bug.