[webkit-dev] test scripts
abarth at webkit.org
Tue Dec 29 11:07:08 PST 2009
I'd prefer to have as few test commands as possible. Ideally, I
should just be able to run the grand unified test suite and know that
my patch is ok to commit. There's some advantages to breaking out the
JSC tests from the WebCore tests so we can avoid building WebCore when
testing JSC. Similarly, there's an advantage to breaking out the
tests of interpreted code from compiled code to avoid unnecessary
compilation. However, I don't see the advantage of dividing the Perl
tests from the Python tests.
On Mon, Dec 28, 2009 at 10:36 PM, Eric Seidel <eric at webkit.org> wrote:
> My 2¢: I like the name test-webkit-python. Or unittest-python, or
> On Mon, Dec 28, 2009 at 9:14 PM, Chris Jerdonek
> <chris.jerdonek at gmail.com> wrote:
>> Last night on IRC there was a brief discussion of the test scripts:
>> how they should be divided in the future and what they should be
>> called. These scripts are in WebKitTools/Scripts.
>> I believe we currently have at least (correct me if I'm wrong)--
>> run-webkit-unittests (tests Python scripts)
>> I also have a patch to add a script to test some Perl functionality.
>> Maciej mentioned that he thinks it's useful for scripts to begin with
>> an action word (i.e. a verb). However, we currently have many scripts
>> (not just testing scripts) that begin with the generic word "run."
>> Going forward, how would people feel about giving new test scripts
>> names that begin with the word "test"? For example--
>> Separate from this question, I think it would be great if one of those
>> participating last night (or anyone else) could share their vision of
>> how they think our tests should be divided up in the mid to long-term.
>> This can include new tests that we haven't written yet, but hope to.
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
More information about the webkit-dev