Skip to content

Latest commit

 

History

History
243 lines (151 loc) · 3.45 KB

FakeTest.md

File metadata and controls

243 lines (151 loc) · 3.45 KB
Raw

Report for com.athaydes.spockframework.report.FakeTest

##Summary

  • Total Runs: 10
  • Success Rate: 50${ds}0%
  • Failures: 3
  • Errors: 2
  • Skipped: 2
  • Total time: Unknown

##This is just a Fake test to test spock-reports

As a user
I want foo
So that bar

Features

A first test

Result: FAIL Time: Unknown

  • Given: we have x and y

  • And: some more things

  • When: I do crazy things

  • Then: I get one iteration pass and another fail

  • Where: The examples below are used

x y
a a Unknown
b c Unknown

The following problems occurred:

  • [b, c]
Condition not satisfied:

x == y
| |  |
b |  c
  false
  1 difference (0% similarity)
  (b)
  (c)

Another feature!!!!

Result: PASS Time: Unknown

  • Given: Setup block here

  • Expect: Expecting something ??

A when then spec

Result: PASS Time: Unknown

  • When: This is the when

  • Then: This is the then

Please ignore me

Result: IGNORED Time: Unknown

  • Given: Nothing

  • When: Do nothing

  • Then: Nothing happens

A test with an error

Issues:

Result: ERROR Time: Unknown

  • When: An Exception is thrown

  • Then: Will never succeed

The following problems occurred:

java.lang.RuntimeException: As expected

A test with a failure

See:

Result: FAIL Time: Unknown

  • When: Do nothing

  • Then: Test fails

The following problems occurred:

Condition not satisfied:

3 == 2
  |
  false


Condition not satisfied:

5 == 1
  |
  false

An incredibly long feature description that unfortunately will popup in some cases where business

analysts write these too detailed overviews of what the test should be all about when what they really
should do is to let the details go in the body of the test using the Gherkin language which underlies BDD
and is proven to make it easier for all involved to understand what the test is doing, what the inputs are
and what the expected outcomes are in such a way that the best possible common understanding is reached

Result: PASS Time: Unknown

  • Expect: The long description above to look good in the report

A Spec with empty block Strings

Result: PASS Time: Unknown

  • Given: ----

  • When: ----

  • Then: ----

An @Unrolled spec with x=0 and y=1 [0]

Result: PASS Time: Unknown

  • Given: nothing

  • Expect: 0 to be 0

  • And: An error if y is 5

  • Where: ----

x y
0 1 Unknown

An @Unrolled spec with x=2 and y=3 [1]

Result: FAIL Time: Unknown

  • Given: nothing

  • Expect: 2 to be 0

  • And: An error if y is 5

  • Where: ----

x y
2 3 Unknown

The following problems occurred:

  • [2, 3]
Condition not satisfied:

x == 0
| |
2 false

An @Unrolled spec with x=0 and y=5 [2]

Result: ERROR Time: Unknown

  • Given: nothing

  • Expect: 0 to be 0

  • And: An error if y is 5

  • Where: ----

x y
0 5 Unknown

The following problems occurred:

  • [0, 5]
java.lang.RuntimeException: y is 5

Future feature

Pending Feature

Result: IGNORED Time: Unknown

  • When: the feature is ready

  • Then: the annotation will be removed

Generated by Athaydes Spock Reports