On Wed, Dec 30, 2009 at 2:33 PM, Sam Weinig sam.wei...@gmail.com wrote:
I would prefer we stick with the run prefix.
I am also not sure why we would have separate testing scripts based by
language.
Thanks, Sam.
The language-specific scripts are more an artifact of the fact that
the Perl test
I would prefer we stick with the run prefix.
I am also not sure why we would have separate testing scripts based by
language. I think it would make a lot more sense to base the scripts on what
they were testing as is currently done (run-webkit-tests tests webkit,
run-javascriptcore-tests tests
On Tue, Dec 29, 2009 at 11:07 AM, Adam Barth aba...@webkit.org wrote:
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
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-tests
run-javascriptcore-tests
My 2¢: I like the name test-webkit-python. Or unittest-python, or
unittest-webkit-python.
On Mon, Dec 28, 2009 at 9:14 PM, Chris Jerdonek
chris.jerdo...@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
5 matches
Mail list logo
