W3C home > Mailing lists > Public > public-test-infra@w3.org > July to September 2014

Re: Generating manifests for the test runner

From: Michael[tm] Smith <mike@w3.org>
Date: Wed, 23 Jul 2014 09:08:30 +0900
To: Brad Hill <hillbrad@gmail.com>
Cc: public-test-infra <public-test-infra@w3.org>
Message-ID: <20140723000830.GM13741@jay.w3.org>
Hi Brad,

./tools/scripts/manifest.py --experimental-include-local-changes

You need to feed the script that "--experimental-include-local-changes" switch.

Sorry this hasn't been better documented yet.


Brad Hill <hillbrad@gmail.com>, 2014-07-22 13:55 -0700:

> Is there any documentation on how to use the manifest.py generator for
> the WPT  test runner?
> (Other than just reading through 600 lines of almost completely
> uncommented code?  I'm a python newbie.)
> I'm creating a new set of tests in a new directory and want to try
> them in the runner, but when I try to run the tool I get "Not writing
> manifest because working directory is not clean."  It's not an error
> that's really helping me out...
> Can I not run the tool until I've committed my tests? Until they've
> been pushed to my remote fork? Merged to the upstream master?
> Do I need to write a manifest for my test cases?
> Is it just generated automatically for all the tests?  How do I
> indicate what kind of tests they are?
>  It's not obvious to me where to start here, in part because I've
> already run the tool so I don't know what is generated vs. what is
> baseline, and my previous questions indicated that people had checked
> in things that really should've been generated... etc.
> thanks,
> Brad

Michael[tm] Smith http://people.w3.org/mike

Received on Wednesday, 23 July 2014 00:08:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:34:11 UTC