forked from learn-co-students/ttt-1-welcome-rb-cb-gh-000
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
572cbfa
commit 9d6429d
Showing
8 changed files
with
40 additions
and
95 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,6 @@ | ||
tags: | ||
- tag1 | ||
- puts | ||
- tictactoe | ||
languages: | ||
- language1 | ||
resources: 0 | ||
- ruby | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,4 +4,4 @@ source "https://rubygems.org" | |
# gem "rails" | ||
|
||
gem 'rspec' | ||
gem 'pry' | ||
gem 'pry' |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,23 @@ | ||
--- | ||
tags: | ||
languages: | ||
resources: | ||
--- | ||
# Ttt Welcome Rb | ||
# Welcome Message for Tic Tac Toe | ||
|
||
## Overview | ||
|
||
We're going to build a simple program that implements only the very first thing a complete Tic Tac Toe program would require, simply greeting the player with a welcome message. | ||
|
||
## Objectives | ||
|
||
1. Read the output from running `learn`. | ||
2. Use `puts` in `lib/welcome.rb` to print "Welcome to Tic Tac Toe!" | ||
3. Have your tests pass locally by running `learn`. | ||
4. Submit your solution. | ||
|
||
## Instructions | ||
|
||
1. Run `learn` | ||
2. Read output. | ||
3. Code solution in `lib/welcome.rb` | ||
4. Run `learn` | ||
5. Read output. | ||
6. If still broken, repeat 3-5 | ||
7. If passing, submit with `learn submit` | ||
|
Empty file.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
# Edit this file to output "Weclome to Tic Tac Toe!" | ||
# You can see what this file does by running: | ||
# ruby lib/welcome.rb from your terminal. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,78 +1,3 @@ | ||
# This file was generated by the `rspec --init` command. Conventionally, all | ||
# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`. | ||
# The generated `.rspec` file contains `--require spec_helper` which will cause this | ||
# file to always be loaded, without a need to explicitly require it in any files. | ||
# | ||
# Given that it is always loaded, you are encouraged to keep this file as | ||
# light-weight as possible. Requiring heavyweight dependencies from this file | ||
# will add to the boot time of your test suite on EVERY test run, even for an | ||
# individual file that may not need all of that loaded. Instead, make a | ||
# separate helper file that requires this one and then use it only in the specs | ||
# that actually need it. | ||
# | ||
# The `.rspec` file also contains a few flags that are not defaults but that | ||
# users commonly want. | ||
# | ||
# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration | ||
RSpec.configure do |config| | ||
# The settings below are suggested to provide a good initial experience | ||
# with RSpec, but feel free to customize to your heart's content. | ||
=begin | ||
# These two settings work together to allow you to limit a spec run | ||
# to individual examples or groups you care about by tagging them with | ||
# `:focus` metadata. When nothing is tagged with `:focus`, all examples | ||
# get run. | ||
config.filter_run :focus | ||
config.run_all_when_everything_filtered = true | ||
# Many RSpec users commonly either run the entire suite or an individual | ||
# file, and it's useful to allow more verbose output when running an | ||
# individual spec file. | ||
if config.files_to_run.one? | ||
# Use the documentation formatter for detailed output, | ||
# unless a formatter has already been configured | ||
# (e.g. via a command-line flag). | ||
config.default_formatter = 'doc' | ||
end | ||
# Print the 10 slowest examples and example groups at the | ||
# end of the spec run, to help surface which specs are running | ||
# particularly slow. | ||
config.profile_examples = 10 | ||
# Run specs in random order to surface order dependencies. If you find an | ||
# order dependency and want to debug it, you can fix the order by providing | ||
# the seed, which is printed after each run. | ||
# --seed 1234 | ||
config.order = :random | ||
# Seed global randomization in this process using the `--seed` CLI option. | ||
# Setting this allows you to use `--seed` to deterministically reproduce | ||
# test failures related to randomization by passing the same `--seed` value | ||
# as the one that triggered the failure. | ||
Kernel.srand config.seed | ||
# rspec-expectations config goes here. You can use an alternate | ||
# assertion/expectation library such as wrong or the stdlib/minitest | ||
# assertions if you prefer. | ||
config.expect_with :rspec do |expectations| | ||
# Enable only the newer, non-monkey-patching expect syntax. | ||
# For more details, see: | ||
# - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax | ||
expectations.syntax = :expect | ||
end | ||
# rspec-mocks config goes here. You can use an alternate test double | ||
# library (such as bogus or mocha) by changing the `mock_with` option here. | ||
config.mock_with :rspec do |mocks| | ||
# Enable only the newer, non-monkey-patching expect syntax. | ||
# For more details, see: | ||
# - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/ | ||
mocks.syntax = :expect | ||
# Prevents you from mocking or stubbing a method that does not exist on | ||
# a real object. This is generally recommended. | ||
mocks.verify_partial_doubles = true | ||
end | ||
=end | ||
config.order = :default | ||
end |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
describe "lib/welcome.rb" do | ||
it 'prints "Welcome to Tic Tac Toe"' do | ||
expect($stdout).to receive(:puts).with("Welcome to Tic Tac Toe!"), "Make sure lib/welcome.rb has code that can output 'Welcome to Tic Tac Toe!' exactly." | ||
|
||
load './lib/welcome.rb' | ||
end | ||
end |