RSpec Story Runner (early BDD tools)

E440640

RSpec Story Runner was an early behavior-driven development tool for Ruby that introduced a narrative, story-based style of specifying application behavior before it evolved into RSpec’s more familiar example-based syntax.

Try in SPARQL Jump to: Surface forms Statements Referenced by

All labels observed (1)

Label Occurrences
RSpec Story Runner (early BDD tools) canonical 1

Statements (48)

Predicate Object
instanceOf Ruby testing tool
behavior-driven development tool
software testing framework component
aimsTo align tests with user stories
make tests readable by non-programmers
designGoal bridge communication between developers and stakeholders
encourage outside-in design
support executable user stories
documentationStyle narrative user stories
evolvedInto RSpec example-based syntax
RSpec story-like features in RSpec 2
executionModel parse stories and invoke Ruby step definitions
feature Given-When-Then style scenarios
mapping steps to Ruby code
narrative story-based syntax
plain-language stories
granularity high-level behavior specifications
historicalRole early BDD tool for Ruby
precursor to modern BDD story frameworks
influenced Cucumber NERFINISHED
RSpec example-based syntax
RSpec feature specs
inputFormat text-based story files
license open-source software license
maintainerCommunity RSpec core team NERFINISHED
output test execution reports
partOf RSpec NERFINISHED
primaryUse executable specifications
specifying application behavior
programmingLanguage Ruby NERFINISHED
relatedTo Cucumber NERFINISHED
RSpec example groups
Story Runner in RSpec 1.x
softwareGenre acceptance testing tool
behavior-driven development framework
status deprecated
superseded by Cucumber and RSpec example groups
supersededBy Cucumber feature files
RSpec example-based specs
supportsActivity acceptance-level testing
regression testing via stories
requirements specification
timePeriod early era of RSpec 1.x
typicalDomain business applications
web applications
typicalUser BDD practitioners
Ruby developers
usesParadigm behavior-driven development

Referenced by (1)

Full triples — surface form annotated when it differs from this entity's canonical label.

RSpec influencedBy RSpec Story Runner (early BDD tools)