Commits

Johannes Rudolph committed e2e7ba6

  • Participants
  • Parent commits c34a806

Comments (0)

Files changed (1)

 
 In order to support a **fluent syntax**, SubSpec allows you to specify each of the primitives as extension methods on strings that describe the primitive action that you pass as an argument to the Context (Arrange), Do (Act), or Assert (well, Assert) method.
 
-Because SubSpec allows you to **declare** the tests primitives instead of asking you to **execute** them, SubSpecs execution engine is free to **compose** them into test cases and take care of executing them. More specifically, SubSpec helps you enforce the "one assert per test" rule by generating **two** tests from the previous Specification, **one per verification (Assert or Observe, see below)**:
+Because SubSpec allows you to **declare** the tests primitives instead of asking you to **execute** them, SubSpecs execution engine is free to **compose** them into test cases and take care of executing them. More specifically, SubSpec helps you enforce the "one assert per test" rule by generating **two** tests from the previous Specification, **one per verification (see [[AssertAndObserve|Assert and Observe]] for more details)**:
 
 # **Given **a new stack **with **an element pushed onto it, **expect **the stack is not empty.
 # **Given **a new stack **with **an element pushed onto it, **expect **the stacks Top is the pushed element.
-
-The following illustration depicts the way SubSpec **composes** the primitive actions of the above Specification into test cases. **For each Assert a new Context is setup and the Do action applied:**
-
-{{http://jorudolph.files.wordpress.com/2010/08/subspec_assert1-e1283077403723.png|SubSpec Assert Flow}}
-
-Another verification primitive is available in SubSpec called **Observe**. Observe differs from Assert in that **all Observations share the same Context with the Do action applied:**
-
-{{http://jorudolph.files.wordpress.com/2010/08/subspec_observe1-e1283077433506.png|SubSpec Observe}}
-