Closed Bug 853250 Opened 7 years ago Closed 3 years ago

Need better way of invoking B2G tests

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jgriffin, Unassigned)

References

Details

We don't have an easy way for developers to invoke B2G tests.  There are some scripts in test.sh, but they're quite limited, and not really flexible enough.  It would be better to have a mach-style shell for running them.  We discussed this some time ago, and there was pushback from porting mach to B2G for the build system, but maybe we can do so (or something similar) just for test running at this time.
Keep in mind mach is just a generic CLI driver. You just drop the Python package in the source tree, create a bootstrap script referencing all the .py files defining commands and you are good to go. comm-central installed their own mach bootstrap file that supplements m-c mach commands with their own. B2G could do the same. I encourage B2G to do the same. I know I would prefer to maintain Python over shell, especially considering many of the tools you are interfacing with are written in Python. It just works.
(In reply to Gregory Szorc [:gps] from comment #1)
> Keep in mind mach is just a generic CLI driver. You just drop the Python
> package in the source tree, create a bootstrap script referencing all the
> .py files defining commands and you are good to go. comm-central installed
> their own mach bootstrap file that supplements m-c mach commands with their
> own. B2G could do the same. I encourage B2G to do the same. I know I would
> prefer to maintain Python over shell, especially considering many of the
> tools you are interfacing with are written in Python. It just works.

Massive +1 to this. If we can at least start with tests people will become familiarized with it and there will be less push back if we decide to switch the build system over.
See Also: → 799308
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.