Discussion of the spec

[dignifiedquire]

I've created this repo to discuss and create the protocol we've talked about.

References

• Turn reporters into seperate module mochajs/mocha#492
• vojtajina/testacular#158

[airportyh]

Thanks @dignifiedquire. Here are my initial thoughts.

Extending TAP

To extend TAP we will need to get the TAP authors into the discussion too. But maybe we can simply use indentation to denote test suite hierarchy like Mocha's "spec" reporter already does. Something like

Config
    ok 1 can create
    ok 2 gives progOptions properties when got
    read yaml config file
        ok 3 gets properties from config file
        ok 4 falls back to config file value when progOptions is null
    read json config file
        ok 5 gets properties from config file
FileWatcher
    ok 6 should add
    ok 7 should ignore(not blow up) if watched file does not exist

Then for extra info like tags, we can just use yamlish which is already in the spec.

Extending TAP #2

Or we could extend TAP without changing the spec, but rather just by layering. One way is to use breadcrumbs to denote hierarchy

ok 1 Config > can create
ok 2 Config > gives progOptions properties when got
ok 3 Config > read yaml config file > gets properties from config file
ok 4 Config > read yaml config file > falls back to config file value when progOptions is null
ok 5 Config > read json config file > gets properties from config file
ok 6 FileWatcher > should add
ok 7 FileWatcher > should ignore(not blow up) if watched file does not exist

I am short on time so I'll save my thoughts for JSON stream for another post.

[Raynos]

cc @isaacs @substack

If tap were to be extended then tap consumers would need to be able to not puke on parsing the extension. Both @substack and @isaacs write tap consumers / parsers