Add a script that make it simple to run any type of test by just specifying the filename

NEW
Unassigned

Status

Testing
General
6 years ago
6 years ago

People

(Reporter: Unfocused, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Having so many test suites, all with different ways or running them, is a real pain.

darktrojan wrote a script that takes a test filename (or directory), figures out what type of test it is, how to run it, and runs it. It makes running tests *so* much easier. It should be in the tree for everyone to use.

Blog post: http://www.darktrojan.net/news/2012-01/test-running-script
Source: http://hg.mozilla.org/users/geoff_darktrojan.net/scripts/file/tip/runtest.py
Ted, Joel, Rob, would you be happy with this in the tree? If so, where should I put it?
this looks really handy!  Coming from the mobile side this would be confusing and difficult to do.  We would need to support crashtest at the very least, and possible jsreftest.  But for finding the majority of the tests this is great.  

a location for this might be:
testing/tools/runanytest.py
(In reply to Geoff Lankow (:darktrojan) from comment #1)
> Ted, Joel, Rob, would you be happy with this in the tree? If so, where
> should I put it?

yes please!

(In reply to Joel Maher (:jmaher) from comment #2)
> this looks really handy!  Coming from the mobile side this would be
> confusing and difficult to do.  We would need to support crashtest at the
> very least, and possible jsreftest.  But for finding the majority of the
> tests this is great.  
> 
> a location for this might be:
> testing/tools/runanytest.py

Either tools or testing/tests would be my votes.

Comment 4

6 years ago
I have this more or less implemented in bug 751795. I don't have all the test suites covered, but I intend to. I'm tempted to mark as a dupe. But, I'm not sure what Ted's plans for reviewing that patch are. Once mach gets checked in, it would certainly supersede this.
You need to log in before you can comment on or make changes to this bug.