spockframework / spockframework/spock

Support for biz language "live doc" and execution reports.

Open
#382 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Module-Core Type-Enhancement
Dominant language
Java
Stars
3.6k
Forks
483
PR merge metrics
No merged PRs in 30d

Description

Originally reported on Google Code with ID 260

Would be very nice to push Spock further in it's support for BDD testing, particularly
making the tool more accessible to business users and QA by supporting generation of
business documentation from the implementation spec DSL (eg. http://goo.gl/XQmdT).

Relishapp is good example of generated doc.
http://goo.gl/5Mkq0

Having some ability to define custom grouping would very nice.
eg.
Epic->Story->Feature->Scenarios
or 
requirement->usecase->variations
or whatever...

Also generating similar business-language friendly execution reports would be very
nice, showing pass/fail at the grouping levels.  If something fails then the an indicator
could show failure indicators all the way down to the particular Scenario/Step that
failed, with optional display of technical detail of the failure.

Allowing the Scenario step labels to be parameterized would be very good for generating
spec execution reports for a particular set of test parameters.

Thank you.

Reported by marko.modelcitizen on 2012-07-06 12:36:49

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing Spock's specification DSL and the linked Relishapp examples for business-facing documentation. Done would require a defined design and implementation for custom grouping, business-language documentation, hierarchical execution reports with failure details, and parameterized Scenario step labels.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy, java
Domain
documentation, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.