Skip to content

Latest commit

 

History

History
44 lines (31 loc) · 2.04 KB

README.md

File metadata and controls

44 lines (31 loc) · 2.04 KB
Raw

Cukeness

Cukeness is going to be a tool to help software teams write executable specifications using the Gherkin language that was popularized by Cucumber. Team members will be able to collaboratively write specifications in a web browser and, from that same web browser, see the results of executing those specifications against the system that the software team is working in.

For more information, see "Introducing the Cukeness Project".

Basic Architectural Diagram

block diagram show the relationship between the API server, Git server, web client, Cucumber runner, and step server

@startuml
[API Server] as ApiServer
[Git] as Git
[Web Client] as Client
[Cucumber Runner] as Runner
[Step Server] as StepServer
ApiServer -left-> Runner
ApiServer -> Git
Client -down-> ApiServer
Runner -down-> StepServer
ApiServer -down-> StepServer
@enduml

Getting Started

Start the current version of the API Server and the Step Server.

docker-compose up

In a different terminal window start a bash session for the Runner, to test running cucumber with it talking to the Step Server.

docker-compose run runner cucumber

Eventually starting the Cunner is something that will be controlled by an end-point via the API Server, but for now, we're focused on getting the Step Server functional enough so that it works for our purposes.

What We're Building

We're working on building out a server side implementation of the Cucumber Wire protocol. That will run in the step-server container.