liuggio / fastest

Simple parallel testing execution... with some goodies for functional tests.
MIT License
473 stars 65 forks source link

Add an unique placeholder #68

Closed alexislefebvre closed 8 years ago

alexislefebvre commented 8 years ago

I'm trying to generate code coverage with fastest.

@liuggio suggested to use --log-junit /tmp/logfile{p}.xml, but when I run 26 tests, the value {p} goes from 1 to 4, it looks like the file is overwritten by each test that use the same {p} value.

Currently they are these placeholders:

Can we have another placeholder to ease code coverage logging? I suggest to add another placeholder with an unique number or name, like the ENV_TEST_INC_NUMBER or ENV_TEST_CHANNEL_READABLE variables.

liuggio commented 8 years ago

@alexislefebvre :+1: would you like to provide a PR?

alexislefebvre commented 8 years ago

@liuggio OK I'll give it a try. Is it better to provide the number with a name (like ENV_TEST_CHANNEL_READABLE) or only a number (like ENV_TEST_INC_NUMBER)?

liuggio commented 8 years ago

@alexislefebvre I'd go for ENV_TEST_INC_NUMBER is a pure number, but I think is better if you decide :)

liuggio commented 8 years ago

@alexislefebvre great!