Liking cljdoc? Tell your friends :D
Clojure only.
fundingcircle.jukebox
Integrates instrumented clojure functions with jukebox backends.
Here's an example feature:
Feature: Belly
Scenario: a few cukes
Given I have 42 cukes in my belly
When I wait 2 hours
Then my belly should growl
Clojure functions can be mapped to each step by tagging it with :scene/step:
(defn i-have-cukes-in-my-belly
"Returns an updated `board`."
{:scene/step "I have {int} cukes in my belly"}
[board cukes]
;; Write code here that turns the phrase above into concrete actions
(throw (cucumber.api.PendingException.)))
(defn i-wait-hours
"Returns an updated `board`."
{:scene/step "I wait {int} hours"}
[board hours]
;; Write code here that turns the phrase above into concrete actions
(throw (cucumber.api.PendingException.)))
(defn my-belly-should-growl
"Returns an updated `board`."
{:scene/step "my belly should growl"}
[board]
;; Write code here that turns the phrase above into concrete actions
(throw (cucumber.api.PendingException.)))
Functions with multiple arities can also be tagged. (Clojure allows metadata to be placed after the function body. This example uses that style.)
(defn i-wait-hours
"Returns an updated `board`."
([board]
;; Write code here that turns the phrase above into concrete actions
(throw (cucumber.api.PendingException.)))
([board hours]
;; Write code here that turns the phrase above into concrete actions
(throw (cucumber.api.PendingException.)))
{:scene/steps ["It felt like forever"
"I wait {int} hours"]})
Functions can be registered to run before or after a scenario by
tagging them with :scene/before or :scene/after (or both). A
list of tags can also be provided.
(defn ^:scene/before setup
"Initializes systems under test."
{:scene/tags ["tag-a" "tag-b"]}
[board scenario])
(defn ^:scene/after teardown
"Tears down the test system."
[board scenario])
A function can be registered to be run before or after each step by
tagging it with :scene/before-step or :scene/after-step:
(defn ^:scene/before-step before-step
"Runs before each scenario step."
[board])
(defn ^:scene/after-step after-step
"Runs after each scenario step."
[board])
Integrates instrumented clojure functions with jukebox backends.
Here's an example feature:
```
Feature: Belly
Scenario: a few cukes
Given I have 42 cukes in my belly
When I wait 2 hours
Then my belly should growl
```
Clojure functions can be mapped to each step by tagging it with `:scene/step`:
```
(defn i-have-cukes-in-my-belly
"Returns an updated `board`."
{:scene/step "I have {int} cukes in my belly"}
[board cukes]
;; Write code here that turns the phrase above into concrete actions
(throw (cucumber.api.PendingException.)))
(defn i-wait-hours
"Returns an updated `board`."
{:scene/step "I wait {int} hours"}
[board hours]
;; Write code here that turns the phrase above into concrete actions
(throw (cucumber.api.PendingException.)))
(defn my-belly-should-growl
"Returns an updated `board`."
{:scene/step "my belly should growl"}
[board]
;; Write code here that turns the phrase above into concrete actions
(throw (cucumber.api.PendingException.)))
```
Functions with multiple arities can also be tagged. (Clojure allows
metadata to be placed after the function body. This example uses
that style.)
```
(defn i-wait-hours
"Returns an updated `board`."
([board]
;; Write code here that turns the phrase above into concrete actions
(throw (cucumber.api.PendingException.)))
([board hours]
;; Write code here that turns the phrase above into concrete actions
(throw (cucumber.api.PendingException.)))
{:scene/steps ["It felt like forever"
"I wait {int} hours"]})
```
Functions can be registered to run before or after a scenario by
tagging them with `:scene/before` or `:scene/after` (or both). A
list of tags can also be provided.
```
(defn ^:scene/before setup
"Initializes systems under test."
{:scene/tags ["tag-a" "tag-b"]}
[board scenario])
(defn ^:scene/after teardown
"Tears down the test system."
[board scenario])
```
A function can be registered to be run before or after each step by
tagging it with `:scene/before-step` or `:scene/after-step`:
```clojure
(defn ^:scene/before-step before-step
"Runs before each scenario step."
[board])
(defn ^:scene/after-step after-step
"Runs after each scenario step."
[board])
```hooksclj
(hooks)(hooks source)Finds steps and hooks in ns, or in all namespaces if ns is not
specified.
Finds steps and hooks in `ns`, or in all namespaces if `ns` is not specified.
JukeBackendcljprotocol
Implement this to integrate with a bdd backend like cucumber, .
Implement this to integrate with a bdd backend like cucumber, .
register-after-scene-hookclj
(register-after-scene-hook _ tags hook-fn)Called to register a :scene/after hook.
Called to register a :scene/after hook.
register-after-step-hookclj
(register-after-step-hook _ hook-fn)Called to register a :scene/after-step hook.
Called to register a :scene/after-step hook.
register-before-scene-hookclj
(register-before-scene-hook _ tags hook-fn)Called to register a :scene/before hook.
Called to register a :scene/before hook.
register-before-step-hookclj
(register-before-step-hook _ hook-fn)Called to register a :scene/before-step hook.
Called to register a :scene/before-step hook.
register-stepclj
(register-step _ pattern step-fn)Called to register a step function.
Called to register a step function.
registerclj
(register backend hook-fns)Registers the given step/hook functions with the backend.
Registers the given step/hook functions with the backend.
scene-related?clj
(scene-related? v)Checks whether a var is tagged with any scene related metadata.
Checks whether a var is tagged with any scene related metadata.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close