Right now you are able to specify both the -t (--test) and -m (--manifest) together at the command line. That results in totally unexpected behavior and has to be avoided. If you want to specify tests use -t or -m but not both. Mozmill should make sure that both options can't be specified.
Comment on attachment 634437 [details] Patch Right now without a test but before I write test I want to know what you think about the patch.
Jeff, I have updated the patch and added a test for. It's not the safest right now but once I have moved all the tests and manifest related code into MozMill base, we can handle that inside the run_tests method.
So I figured that this behavior is on purpose? https://github.com/mozautomation/mozmill/blob/master/mozmill/mozmill/__init__.py#L529 Do we really want that? Where will this test be added? Always at the end? I still think we should drop that. But if you agree here, I would have to update my patch once more and get this code removed.
(In reply to Henrik Skupin (:whimboo) from comment #4) > So I figured that this behavior is on purpose? > > https://github.com/mozautomation/mozmill/blob/master/mozmill/mozmill/ > __init__.py#L529 > > Do we really want that? Where will this test be added? Always at the end? I > still think we should drop that. But if you agree here, I would have to > update my patch once more and get this code removed. It is on purpose. And yes, it gets added to the end.
So why do we want to have this behavior? What does it buy us beside confusion what gets run and when?
Comment on attachment 634437 [details] Patch Nice and simple, I like it
Attachment #634437 - Flags: review?(jhammel) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.