Programming Ruby 3.2 (5th Edition): B1.0 page 225, rspec --format documentation

Community PragProg Customers
,
1

page 225 or even 220

It would be worth noting that adding -fd or --format documentation as option to rspec makes a nicer output with all tests passing in green (unfortunately no colours here) :

% rspec -fd unittesting/bdd/5/ts_spec_plus.rb

TennisScorer
  basic scoring
    starts with a score of 0-0
    makes the score 15-0 if the server wins a point
    raises an error if it doesn't know the player
    makes the score 0-15 if the receiver wins a point
    makes the score 15-15 after they both win a point
    is 40-0 after the server wins three points
    is W-L after the server wins four points
    is L-W after the receiver wins four points (PENDING: Not yet implemented)
    is Deuce after each wins three points (PENDING: Not yet implemented)
    is Advantage-server after each wins three points and the server gets one more (PENDING: Not yet implemented)

Pending: (Failures listed here are expected and do not affect your suite's status)

  1) TennisScorer basic scoring is L-W after the receiver wins four points
     # Not yet implemented
     # ./unittesting/bdd/5/ts_spec_plus.rb:55

  2) TennisScorer basic scoring is Deuce after each wins three points
     # Not yet implemented
     # ./unittesting/bdd/5/ts_spec_plus.rb:57

  3) TennisScorer basic scoring is Advantage-server after each wins three points and the server gets one more
     # Not yet implemented
     # ./unittesting/bdd/5/ts_spec_plus.rb:59


Finished in 0.00499 seconds (files took 0.15692 seconds to load)
10 examples, 0 failures, 3 pending
2

Maybe, but you have to draw the line somewhere and in general, I’m tending to be conservative about third-party tools, especially those that already have extensive docs.

(Also, the documentation output is often skipped on large projects because it’s measurably slower…)

Thanks!