spockframework / spockframework/spock

Support specification scripts

Open
#154 1 comment 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 31

Ideas:
 - Groovy script that imports @Speck is considered a specification
 - Script class is annotated with @Speck and @RunWith behind the scenes
 - Make sure that the specification is also run when the script's main method is invoked
(important 
for tools that fail to identify the script as a specification (e.g. IDEs))

Reported by pniederw on 2009-06-26 21:30:55

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

No files or tests are named. Start by locating how Groovy scripts are currently recognized and run, then compare that path with the three requested behaviors: @Speck imports, implicit @RunWith handling, and execution through the script's main method; done means all three cases run as specifications, including in tools that do not identify them automatically.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.