New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: rake/capistrano-like -T option #1022
Comments
Would '--dry-run' make more sense as an the option? On Jul 26, 2013, at 8:20 AM, Schnittchen notifications@github.com wrote:
|
Thinking out loudly... --dry-run works on a lower semantical level, it implies "do everything except touching the real code (hooks + example meat code)". I want "give me what you know about the suite at the meta level", which is a higher level use case, and can be implemented using --dry-run together with a formatter that produces well parsable output (btw do Formatters have access to metadata? That would be important). If you see any additional benefit in --dry-run beyond my use case, I would start with that. |
The main reason I was thinking of
Can you give me an idea of what output you want? I'm not totally sure what you are looking for... |
Yes, orthogonality is the word I was searching for :) Here's an oversimplified example with JSON as output, though the choice of formatting language is secondary.
would produce something like
|
I just found the JsonFormatter (horray for plain data!), but that wouldn't help with my problem. With --dry-run, I could do
in my CI run, that's a little ugly but does the job. I will look into implementing a --dry-run option. |
Looks good to me. |
Closing now that we have |
Thank you! |
schnittchen commentedJul 26, 2013
This option would not exercise the examples, just run the formatters. It would allow me to "query" the entire suite for things like "is there an example with focus: true" without resorting to ugly grep hacks.
If this sounds interesting, I'd try to give it a shot...
The text was updated successfully, but these errors were encountered: