mrowrpurr/Specs.cpp

Issues

• CLI prints out results of tests as they are run remotely (Websockets)

  #11 opened 7 months ago
  0

• CLI exists which triggers Specs remotely (Websockets)

  #10 opened 7 months ago
  0

• Can listen for a remote trigger to run Specs, while Reactor sits idle (Websockets)

  #9 opened 7 months ago
  0

• A TestReporter can be provided which prints test results to std::cout as they are executed

  #8 opened 7 months ago
  0

• When Spec are run, their .name is added to a TestResults object or some kind

  #7 opened 7 months ago
  0

• Reactor can automatically execute Spec from queue when added

  #6 opened 7 months ago
  0

• Reactor only executes Specs::Spec when their conditions are valid, else they remain in the queue until valid (manually re-checking via function call)

  #5 opened 7 months ago
  0

• Specs::Spec can have conditions and are only run those conditions (no Reactor)

  #4 opened 7 months ago
  0

• Reactor exists and can execute Spec, removing them from a queue as they are run

  #3 opened 7 months ago
  0

• Simplest Specs::Spec with a .body std::function<void()> exists

  #2 opened 7 months ago
  0

• [Setup] Bandit specs setup

  #1 opened 2 years ago
  0