| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Otherwise it prints "Interrupt" and a traceback.
|
|
|
|
|
|
* Use a new, currently empty `Board#winner?` method as our loop
condition
* Add `Player#insignia` so we can print the correct player insignia
depending on who the current player is
* Print the board and a prompt for coordinates
* Switch the current player after a player finishes moving
|
|
Return the actual board in the right format instead of always returning
3 rows of 3 dots.
|
|
Also add `Board#update_cell` to facilitate player movement.
|
|
Add an `initialize` method to get rid of our test errors and use the
constants we created in 231060de4c493a9c6ba3510a9be4d405517af5c6 when
creating new `Player`s.
|
|
|
|
Test some code for an API concept for player, ideas for tests of the
`Player#move` method.
|
|
We shouldn't be requiring all our files & classes in the spec_helper. It
should just be used for test setup. We can require the modules we need
for testing directly in the test files.
|
|
Take string coordinates in the form ":integer:,:integer:" and convert
them to [integer, integer]. We'll be using these converted coordinate
values to place a piece on the board.
|
|
* main.rb will be what we use to run the game. Add some setup and an
idea for grabbing board coordinates to place a piece.
* Add empty Player class to represent Xes and Os
|
|
Will be writing both spec and TestUnit versions of the tests.
|
|
Don't print the grid directly. We'll do this in a separate display
method or game loop area.
|
|
The board starts as a grid of dots represented by a 2-dimensional array.
|
|
Use specs for testing, create a spec for the Board class.
Simple functionality and test to print a grid of dots for the board.
|
|
* Add test_helper.rb for includes
* Add a test to sample test that initializes Board
|
|
Create an untracked directory for extra files.
|
|
Create a Rakefile to run tests and a sample test file.
|
