On 02/20/2013 01:42 PM, L. David Baron wrote:
My main question is: what will continue to work and what will stop
working?
For example, which of these ways of running mochitests will still
work and which won't:
TEST_PATH=layout/style/test make mochitest-plain
_tests/testing/mochitest/runtests.py --test-path=layout/style --debugger=valgrind
--debugger-args="..." --setenv=XPCOM_MEM_LOG_CLASSES=nsHTMLDocument
(other things that other people use should probably go here)
If particular things are going to stop working, I'd like to know
what they are; if you're planning to maintain compatibility with
existing ways to run and debug tests (and this is just a change in
what happens underneath), I'd also like to know that. It's not
clear to me from your message which sort of change this is.
-David
The plan is to keep as much of the API/CLI initially the same. If there
will be planned/known breakages, then I will endeavor (and hope others
will do the same) to follow up to this list with the planned breakages.
This is intended as a refactor of the innards in stage one.
In subsequent stages, we are likely to change the way running e.g.
mochitests will work. Hopefully they will be simpler! I can't give any
answers as far as how they will change, as we (or at least I) am not
that far along enough yet. Suffice it to say, we will insist on not
dropping functionality (albeit one man's feature is another man's bug)
and will support as much of legacy methods as possible without having to
take huge steps backwards for them. But in this case also, we will
endeavor to communicate with dev-platform.
Jeff
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
