Organisation of test suites
14 views
Skip to first unread message
Steve Smith
May 19, 2011, 6:43:54 AM5/19/11
to yatspec
I'm currently sat in front of a demo of Twist and I'm distinctly
unimpressed. It makes me think of an pretty Eclipse plugin for
Concordion, which doesn't really float my boat to be honest.
It has made me think about organisation of test suites though. I
wonder if there's a way we can allow Yatspec to auto-generate a top-
level report of all tests run, organised by suite.
As our projects using Yatspec get larger, it becomes harder to find
tests published on a CI server and harder to find a test in an IDE.
If we can auto-generate that report without users having to explicitly
having to create suites a la JUnit 3 or 4, that could be really
useful.
S
unimpressed. It makes me think of an pretty Eclipse plugin for
Concordion, which doesn't really float my boat to be honest.
It has made me think about organisation of test suites though. I
wonder if there's a way we can allow Yatspec to auto-generate a top-
level report of all tests run, organised by suite.
As our projects using Yatspec get larger, it becomes harder to find
tests published on a CI server and harder to find a test in an IDE.
If we can auto-generate that report without users having to explicitly
having to create suites a la JUnit 3 or 4, that could be really
useful.
S
Matt Savage
May 19, 2011, 8:15:34 AM5/19/11
to yat...@googlegroups.com
I'm currently sat in front of a demo of Twist and I'm distinctly
unimpressed. It makes me think of an pretty Eclipse plugin for
Concordion, which doesn't really float my boat to be honest.
It's shit. And the wrong approach.
It has made me think about organisation of test suites though. I
wonder if there's a way we can allow Yatspec to auto-generate a top-
level report of all tests run, organised by suite.
We've talked about doing this it's a missing piece. We haven't really explored how good you can make living documentation using yatspec.
As our projects using Yatspec get larger, it becomes harder to find
tests published on a CI server and harder to find a test in an IDE.
I still like the stuff we were doing in Twig with basing the structure of the tests around the structure of resources/urls on the site.
Steve Smith
May 19, 2011, 10:33:00 AM5/19/11
to yatspec
Agreed Matt.
I guess what I really want is an index.html at the root of a Yatspec
test results directory, which a) I can then use to drill into
individual tests b) render in a custom tab called "Yatspec" or similar
in TeamCity. That would give me a high level view of how a test run
progressed - I think Concordion does give you that (sort of).
I guess what I really want is an index.html at the root of a Yatspec
test results directory, which a) I can then use to drill into
individual tests b) render in a custom tab called "Yatspec" or similar
in TeamCity. That would give me a high level view of how a test run
progressed - I think Concordion does give you that (sort of).
Daniel Worthington-Bodart
May 19, 2011, 12:16:27 PM5/19/11
to yat...@googlegroups.com
Indexes are definitely on their way as I will need it to make all my project self documenting!
This will allow me to crawl back into my cave, put the RTFM sign up and not speak to anyone except maybe you Matt!
Reply all
Reply to author
Forward
0 new messages