Testing Output With RSpec

2 min read

This is a quick blog on testing output with RSpec. Currently, I am working on a Tic Tac Toe game in Ruby, where a human player can play against a computer.

Previous test attempts

I’ve experienced issues testing a loop in the game, where it keeps requesting moves from players until the board is full or a player has won.

1def main_game
2 play_move until @game.over?
3 end_of_game

One attempt at testing this was to spy on the play_move and end_of_game methods. This worked fine if a full board was provided.

However, this was proving difficult to test when an incomplete board was present. Despite simulating user input, the test would hang at this stage. The same issue occurred when using object doubles.

Testing output

One of my mentors suggested testing the output of the end_of_game method. The end_of_game method prints the Tic Tac Toe board and the outcome of the game.

1it 'plays a game that ends with a winning player' do
3 expect { controller.main_game }
4 .to output("""
6 1 | x | x
8 o | o | x
10 x | o | o
11The current player is x
12Choose a position from 1-9:
14 x | x | x
16 o | o | x
18 x | o | o
19x is the winner!""")
20 .to_stdout

The multi-lines and alignment was also proving difficult to get right for the expected output. The key element that needed to be tested was the outcome of the game, which was the last line of the output: 'x is the winner!'


StringIO is a ‘string-based replacement for an IO object. It acts same as a file, but it’s kept in memory as a String’.

The idea is to catch the stream of output and redirect it. To check the last line of the output was correct, my mentor suggested trying the following:

1it 'plays a game that ends with a winning player' do
2 controller = controller_setup([1, 'x', 'x', 4, 'o', 'x', 'x', 8, 'o'])
3 allow($stdin).to receive(:gets).and_return('8', '4', '1')
4 $stdout = *StringIO*.new
6 controller.main_game
7 output = $stdout.string.split("\n")
9 expect(output.last).to eq('x is the winner!')

In this test:

  • A new instance of the controller class is created, with an incomplete board

  • The input is simulated to play the three remaining positions on the board

  • The standard output $stdin is redirected to a new instance of StringIO

  • The main_game method is called to play and complete the game

  • The output is then saved to the variable output, converted to a string, and split at the points where there is a new line to create an array of strings

  • The last item in the array is expected to be 'x is the winner!'

I’ll continue to use this method when testing large blocks of text with multiple lines. It’s significantly simpler than trying to align multi-line outputs in a test.


Previous post:
The Red Green Refactor Cycle
Next post:
Creating An Unbeatable Computer Player Using Minimax