Bruno P. Kinoshita

The example above fails for me with the latest `cwltool`. ```bash kinow@ranma:/tmp/bunny-1.0.6$ mkdir /tmp/cwl kinow@ranma:/tmp/bunny-1.0.6$ touch /tmp/cwl/a kinow@ranma:/tmp/bunny-1.0.6$ touch /tmp/cwl/b ``` ```bash (venv) kinow@ranma:~/Development/python/workspace/cwl-v1.2$ cwltool /tmp/make_secondary.cwl --parent_file /tmp/cwl/a --children /tmp/cwl/b...

Here's an example that runs `pytest` (which is able to run `unittest` tests too) and also verifies the doctests: https://github.com/cylc/cylc-flow/blob/91bd2cf7958fcbfe982d3f260363ef13e731666e/pytest.ini#L19

Hey @jonathanKingston, maybe this issue can be merged with #9?

Oh, got it @jonathanKingston, thought it was more like #9, defining entries and schema. Thanks for clarifying :-)

> I would argue that requiring the results be in order is silly. Good point. Though sometimes users might want to keep tests in order too. For instance, when you...

> My worry with having two implementations (ordered and unordered) we are making consumers have to cope with both. Understandable. As I mentioned, I still don't have a strong opinion...

@jonathanKingston I'm happy with the old proposal for subtests ``` TAP 13 1..1 ok 1 - Subtest 1 ok 1 - subtest 2a ok 2 - subtest 2b ``` I'd...

@Ovid > As for how to handle YAML diagnostic information, I thought it was to be indented four spaces from the current line I also recall reading it somewhere, probably...

Since the specification has been frozen for a while, a TAP 14 which breaks backward compatibility could be dangerous and reduce the number of adopters, IMO. Though I agree with...

Thanks @xmojmr! Just created issue #10 for it, so that we can move this discussion there.