- From: Brad Hill <hillbrad@gmail.com>
- Date: Tue, 22 Jul 2014 16:06:11 -0700
- To: Masahito Kawamori <kawamori@w3.org>
- Cc: public-test-infra <public-test-infra@w3.org>
I hadn't seen that, thanks, but it just points back to web-platform-tests for how to generate a manifest. That's where I started and where I'm stuck. On Tue, Jul 22, 2014 at 4:01 PM, Masahito Kawamori <kawamori@w3.org> wrote: > Hi Brad > > Does the README.rst at [1] help? > > Thanks > > Kawamori > > [1] https://github.com/w3c/wptrunner > > > > On Wed, Jul 23, 2014 at 5:55 AM, Brad Hill <hillbrad@gmail.com> wrote: >> >> 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 >> >
Received on Tuesday, 22 July 2014 23:06:39 UTC