Kelsey Gilbert [:jgilbert] Reporter
	Description • 10 years ago

I had tests that were not running because the files started were like `test-foo.html` instead of `test_foo.html`, and the only message was a warning buried in the mochitest spew about them 'not being valid tests'.

It should assert.

	Joel Maher ( :jmaher ) (UTC -8)
	Comment 1 • 10 years ago

would you want this as a 'test-unexpected-fail' in the log file?  how would you like the notification to be shown?

	Kelsey Gilbert [:jgilbert] Reporter
	Comment 2 • 10 years ago

(In reply to Joel Maher (:jmaher) from comment #1)
> would you want this as a 'test-unexpected-fail' in the log file?  how would
> you like the notification to be shown?
No, this is not a test error, it's a manifest error. Just throw an assert from python.

	Joel Maher ( :jmaher ) (UTC -8)
	Comment 3 • 10 years ago

this failure comes from inside the browser (javascript) where the test definition is.  I would like to avoid duplicating the logic here, but I could duplicate it.  We have different rules for chrome, browser-chrome, plain.

	(not currently active) Ted Mielczarek
	Comment 4 • 10 years ago

Sadly at the moment I think we still have junk in our manifests (from when we auto-converted from Makefiles) that means we can't make this fatal yet.

	Kelsey Gilbert [:jgilbert] Reporter
	Comment 5 • 10 years ago

(In reply to Ted Mielczarek [:ted.mielczarek] from comment #4)
> Sadly at the moment I think we still have junk in our manifests (from when
> we auto-converted from Makefiles) that means we can't make this fatal yet.

I'm willing do to the mechanical patches to fix this.

	(not currently active) Ted Mielczarek
	Comment 6 • 10 years ago

That's bug 983867. I am happy to review patches!

	Joel Maher ( :jmaher ) (UTC -8)
	Comment 7 • 10 years ago

:vaibhav, there are a lot of dependencies here, this is additional manifest work you could easily help out on!

	Kelsey Gilbert [:jgilbert] Reporter
	Comment 8 • 10 years ago

I'd like to note that while it's easy to just remove these, since they're already not being run, a bunch of them look like valid tests. A module owner/peer should check that we can just remove them.