What the %$%^$ is SPEC?

• Very advanced form of subtests.
• Influenced by Ruby's RSPEC.
• Declarative testing structures.
• Concurrency control.
• Better test scoping and grouping
• Provided by the Test2-Workflow distribution

Test Blocks

Test blocks are not run immedietly, they will be run when the done_testing() function is called.

You can run a specific codeblock using the $T2_WORKFLOW variable, which takes either a name or a line number.

Test Block Params

You can combine any number of these at once.

Describe Blocks

Before

• outer1 will run once, before anything else
• outer2 will run once per test block, before the test block
• outer2 runs for 'not_color', 'red', 'green', and 'blue'
• inner1 will run once, before 'red', 'green', and 'blue'
• inner2 will run once per test block, before the block
• inner2 does not run for 'not_color'
• inner2 will run for any tests under 'nested'

After

• outer1 will run once, after everything else
• outer2 will run once per test block, after the test block
• outer2 runs for 'not_color', 'red', 'green', and 'blue'
• inner1 will run once, after 'red', 'green', and 'blue'
• inner2 will run once per test block, after the block
• inner2 does not run for 'not_color'
• inner2 will run for any tests under 'nested'

Around

• Same rules as before/after.
• You MUST call the $continue sub.
• Useful for localizing environment variables.

Test Cases

Case Modifiers

• These work just like before/after do with test blocks
• These bind to the cases instead of the test blocks

1. before_all
2. (for each case)
   1. before_case
   2. case
   3. after_case
   4. (for each test block)
      1. before_each
      2. tests
      3. after_each
3. after_all

Mocking

Test2::Tools::Spec is smart with Test2::Tools::Mock. It treats a mock in void context as a before_each (roughly).

Declare

Test2::Plugin::SpecDeclare provides nice syntax sugar:

• No need for 'sub' keyword.
• No need for ending semicolon.
• Parameters are like a signature.
• Uses Devel::Declare.