elus 0.1.0

data/doc/user_stories_files/colorschememapping.xml

@@ -0,0 +1,2 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<a:clrMap xmlns:a="http://schemas.openxmlformats.org/drawingml/2006/main" bg1="lt1" tx1="dk1" bg2="lt2" tx2="dk2" accent1="accent1" accent2="accent2" accent3="accent3" accent4="accent4" accent5="accent5" accent6="accent6" hlink="hlink" folHlink="folHlink"/>

data/doc/user_stories_files/filelist.xml

@@ -0,0 +1,6 @@
+<xml xmlns:o="urn:schemas-microsoft-com:office:office">
+ <o:MainFile HRef="../user_stories.htm"/>
+ <o:File HRef="themedata.thmx"/>
+ <o:File HRef="colorschememapping.xml"/>
+ <o:File HRef="filelist.xml"/>
+</xml>

data/elus.gemspec

@@ -0,0 +1,91 @@
+# Generated by jeweler
+# DO NOT EDIT THIS FILE DIRECTLY
+# Instead, edit Jeweler::Tasks in rakefile, and run the gemspec command
+# -*- encoding: utf-8 -*-
+
+Gem::Specification.new do |s|
+  s.name = %q{elus}
+  s.version = "0.1.0"
+
+  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
+  s.authors = ["arvicco"]
+  s.date = %q{2010-03-11}
+  s.default_executable = %q{elus}
+  s.description = %q{This is a support tool for winning SpaceRangers:Elus}
+  s.email = %q{arvitallian@gmail.com}
+  s.executables = ["elus"]
+  s.extra_rdoc_files = [
+    "LICENSE",
+     "README.rdoc"
+  ]
+  s.files = [
+    ".document",
+     ".gitignore",
+     "LICENSE",
+     "README.rdoc",
+     "Rakefile",
+     "VERSION",
+     "bin/elus",
+     "doc/dev_plan.htm",
+     "doc/dev_plan_files/colorschememapping.xml",
+     "doc/dev_plan_files/filelist.xml",
+     "doc/dev_plan_files/themedata.thmx",
+     "doc/user_stories.htm",
+     "doc/user_stories_files/colorschememapping.xml",
+     "doc/user_stories_files/filelist.xml",
+     "doc/user_stories_files/themedata.thmx",
+     "elus.gemspec",
+     "features/gamer_inputs_state.feature",
+     "features/gamer_starts_solver.feature",
+     "features/gamer_updates_state.feature",
+     "features/solver_shows_hints.feature",
+     "features/step_definitions/elus_steps.rb",
+     "features/support/env.rb",
+     "features/support/stats.rb",
+     "lib/elus.rb",
+     "lib/elus/game.rb",
+     "lib/elus/generator.rb",
+     "lib/elus/piece.rb",
+     "lib/elus/rule.rb",
+     "lib/elus/solver.rb",
+     "spec/cucumber/stats_spec.rb",
+     "spec/elus/game_spec.rb",
+     "spec/elus/generator_spec.rb",
+     "spec/elus/piece_spec.rb",
+     "spec/elus/rule_spec.rb",
+     "spec/elus/solver_spec.rb",
+     "spec/spec.opts",
+     "spec/spec_helper.rb"
+  ]
+  s.homepage = %q{http://github.com/arvicco/elus}
+  s.rdoc_options = ["--charset=UTF-8"]
+  s.require_paths = ["lib"]
+  s.rubygems_version = %q{1.3.5}
+  s.summary = %q{This is a support tool for winning SpaceRangers:Elus}
+  s.test_files = [
+    "spec/cucumber/stats_spec.rb",
+     "spec/elus/game_spec.rb",
+     "spec/elus/generator_spec.rb",
+     "spec/elus/piece_spec.rb",
+     "spec/elus/rule_spec.rb",
+     "spec/elus/solver_spec.rb",
+     "spec/spec_helper.rb"
+  ]
+
+  if s.respond_to? :specification_version then
+    current_version = Gem::Specification::CURRENT_SPECIFICATION_VERSION
+    s.specification_version = 3
+
+    if Gem::Version.new(Gem::RubyGemsVersion) >= Gem::Version.new('1.2.0') then
+      s.add_development_dependency(%q<rspec>, [">= 1.2.9"])
+      s.add_development_dependency(%q<cucumber>, [">= 0"])
+    else
+      s.add_dependency(%q<rspec>, [">= 1.2.9"])
+      s.add_dependency(%q<cucumber>, [">= 0"])
+    end
+  else
+    s.add_dependency(%q<rspec>, [">= 1.2.9"])
+    s.add_dependency(%q<cucumber>, [">= 0"])
+  end
+end
+

data/features/gamer_inputs_state.feature

@@ -0,0 +1,135 @@
+Feature: Gamer inputs Game state
+
+    In order to get help with specific Elus game, 
+	as Gamer, I want to input Game state
+
+	Description: Gamer enters 3-char sequences representing 3 free Pieces. 
+	If the Game just started, he is then prompted for 3 3-char sequences representing Pieces already on the Board.
+	
+	Pieces have 3 characteristics: Size: BIG/SMALL, Color: YELLOW/GREEN, Type: DIAMOND/CIRCLE
+	Gamer's input will be in a form BYR, SGC, etc
+	
+	Scenario: every correct code results in correct feedback / game state
+		Given new Game just started
+		When I run solver 2,000 times and use 6 correct codes to input state
+		Then I should see all the correct feedback, piece names and game states
+
+	Scenario Outline: every correct code results in correct feedback and game state
+		Given new Game just started
+		When I input code <code> 
+		Then I should see "You entered Free Piece (1): <piece>"
+		
+		Examples: Big Yellow Diamond
+			| code | piece               |
+			| BYR  | Big Yellow Diamond  |
+			| BYD  | Big Yellow Diamond  |
+			| bYR  | Big Yellow Diamond  |
+			| ByR  | Big Yellow Diamond  |
+			| BYr  | Big Yellow Diamond  |
+			| byR  | Big Yellow Diamond  |
+			| bYr  | Big Yellow Diamond  |
+			| byr  | Big Yellow Diamond  |
+			| byd  | Big Yellow Diamond  |
+			| 111  | Big Yellow Diamond  |
+			| bdy  | Big Yellow Diamond  |
+			| dyb  | Big Yellow Diamond  |
+			| d y b | Big Yellow Diamond |
+			| dby  | Big Yellow Diamond  |
+			| ybd  | Big Yellow Diamond  |
+			| ddddyb | Big Yellow Diamond |
+			| dyybb | Big Yellow Diamond  |
+			| dxbyxd | Big Yellow Diamond |
+			| by1  | Big Yellow Diamond  |
+			
+		Examples: Small Yellow Diamond
+			| code | piece               |
+			| SYR  | Small Yellow Diamond|
+			| SYD  | Small Yellow Diamond|
+			| syr  | Small Yellow Diamond|
+			| syd  | Small Yellow Diamond|
+			| 011  | Small Yellow Diamond|
+			| dys  | Small Yellow Diamond|
+
+		Examples: Big Green Diamond
+			| code | piece               |
+			| BGR  | Big Green Diamond   |
+			| BGD  | Big Green Diamond   |
+			| bgr  | Big Green Diamond   |
+			| bgd  | Big Green Diamond   |
+			| BgR  | Big Green Diamond   |
+			| 101  | Big Green Diamond   |
+
+		Examples: Small Green Diamond
+			| code | piece               |
+			| SGR  | Small Green Diamond |
+			| SGD  | Small Green Diamond |
+			| sgd  | Small Green Diamond |
+			| 001  | Small Green Diamond |
+
+		Examples: Big Yellow Circle
+			| code | piece               |
+			| BYC  | Big Yellow Circle   |
+			| byc  | Big Yellow Circle   |
+			| byC  | Big Yellow Circle   |
+			| bYC  | Big Yellow Circle   |
+			| bYc  | Big Yellow Circle   |
+			| Byc  | Big Yellow Circle   |
+			| ByC  | Big Yellow Circle   |
+			| BYC  | Big Yellow Circle   |
+			| BYc  | Big Yellow Circle   |
+			| 110  | Big Yellow Circle   |
+
+		Examples: Small Yellow Diamond
+			| code | piece               |
+			| SYC  | Small Yellow Circle |
+			| syc  | Small Yellow Circle |
+			| 010  | Small Yellow Circle |
+
+		Examples: Big Green Circle
+			| code | piece               |
+			| BGC  | Big Green Circle    |
+			| bgc  | Big Green Circle    |
+			| 100  | Big Green Circle    |
+
+		Examples: Small Green Circle
+			| code | piece               |
+			| SGC  | Small Green Circle  |
+			| sgc  | Small Green Circle  |
+			| 000  | Small Green Circle  |
+
+	Scenario Outline: wrong codes results in error message
+		Given new Game just started
+		When I input code <code> 
+		Then I should see "Invalid code: <code>"
+		
+		Examples: Ambiguous codes
+			| code |
+			| BSYR  |
+			| BYgD  |
+			| bYRc  |
+			| Bydc  |
+			| BsYgr  |
+			| bygRc  |
+			| bsYrc  |
+			| bsygcr |
+
+		Examples: Not enough meaningful codes
+			| code |
+			| _   |
+			| !@# |
+			| B   |
+			| gb  |
+			| gr  |
+			| sca |
+			| bgt |
+			| thd |
+
+		Examples: Numeric code errors (not enough, too much, wrong numbers)
+			| code |
+			| 0   |
+			| 1   |
+			| 01  |
+			| 11  |
+			| 1111  |
+			| 112  |
+			| 101231|

data/features/gamer_starts_solver.feature

@@ -0,0 +1,13 @@
+Feature: Gamer starts Solver
+
+	In order to win multiple Elus games, 
+	as Gamer, I want to start Solver
+	
+	Description: Gamer opens up a shell, types a command, and sees a welcome message and a prompt to input Game state.
+
+	Scenario: start Solver
+		Given I have not started yet
+		When I start Solver
+		Then I should see "Welcome to Elus Solver!"
+		And I should see "Enter Game state:"
+		

data/features/gamer_updates_state.feature

@@ -0,0 +1,27 @@
+Feature: Gamer updates state
+
+    In order to get relevant help as the Elus game progress,
+    as Gamer, I want to update Game state, making moves and reporting its results
+
+	Description: In response to "Please make your move:" prompt, Gamer enters 3-char code of the
+	Piece he is going to move (it should be one of 3 free Pieces). Gamer then gets feedback
+	either confirming the move or error message and prompt for the correct move. Once the move
+	is confirmed, Gamer is asked for move result (was the move right or wrong) and a new set of
+	free Game pieces if the result was right.
+	
+	Scenario Outline: Gamer makes moves
+		Given Elus Game state is <state>
+		And Game started with <generator>
+		And Game state inputed
+		When I move <piece>
+		Then I should see "<feedback>"
+		And I should see "<next prompt>"
+		
+		Examples: 
+			| state 	              | generator      | piece | feedback                                           | next prompt		      |
+			| BGC sgd syc BYD SYD BGD | Turn1Generator | SGD   | You moved: Small Green Diamond                     | Was the move right(Y/N)?:|
+			| BGC sgd syc BYD SYD BGD | Turn1Generator | BGC   | You moved: Big Green Circle                        | Was the move right(Y/N)?:|
+			| BGC sgd syc BYD SYD BGD | Turn1Generator | SYC   | You moved: Small Yellow Circle                     | Was the move right(Y/N)?:|
+			| BGC sgd syc BYD SYD BGD | Turn1Generator |       | Wrong move (no piece given)                        | Make your move:   |
+			| BGC sgd syc BYD SYD BGD | Turn1Generator | SYD   | Wrong move (not in free set): Small Yellow Diamond | Make your move:   |
+	

data/features/solver_shows_hints.feature

@@ -0,0 +1,36 @@
+Feature: Solver shows hints
+
+	In order to get some help with Elus game
+	as Gamer, I want the Solver to show hints
+	
+	Description: Once the Gamer inputs/updates valid Elus Game state, 
+	Solver tries to figure out WHAT Rules may be possible under current Game state,
+	produces hints regarding possible rules and next moves by the Gamer and displays hints to the Gamer.
+
+	Scenario Outline: Solver shows hints after initial Game state input
+		Given Elus Game state is <state> 
+		And Game started with <generator> 
+		When I input Game state and prepare to move
+		Then I should see "<moves>"
+		And I should see "<rules>"
+	
+		Examples: Invalid Game states: 
+			| generator      | state                   | moves | rules |
+			| EmptyGenerator | BYD BYD BYD BYD BYD BYD | Moves(0): | Rules(0): |
+			| Turn1Generator | BYD BYD BYD BYD BYD BYD | Moves(0): | Rules(0): |
+			| Turn2Generator | BYD BYD BYD BYD BYD BYD | Moves(0): | Rules(0): |
+			| Turn3Generator | BYD BYD BYD BYD BYD BYD | Moves(0): | Rules(0): |
+
+		Examples: Valid Game states: 
+			| generator      | state                   | moves | rules |
+			| Turn1Generator | BGC sgd syc BYD SYD BGD | Moves(1): | Rules(2): |
+
+	Scenario Outline: Solver shows hints after Gamer makes his move state input
+		Given Elus Game state is <code1>,<code2>,<code3>,<code4>,<code5>,<code6> 
+		And Game started with <generator> 
+		And initial Game state was already input
+		When I move this <piece>
+		Then I should see "<moves>"
+		And I should see "<rules>"
+			
+			

data/features/step_definitions/elus_steps.rb

@@ -0,0 +1,116 @@
+def stdout
+  @stdout ||= StringIO.new # STDOUT is an instance of IO. The StringIO object is very much like an IO object.
+end
+
+def stdin(input=nil)
+  @stdin ||= StringIO.new # STDIN is an instance of IO. The StringIO object is very much like an IO object.
+  @stdin.reopen input if input
+  @stdin
+end
+
+def solver
+  @solver ||= Elus::Solver.new(stdin, stdout) # Elus::Solver expects STDOUT, but we're giving it our StringIO @stdout instead
+end
+
+def solver_restart_and_input(input_codes) 
+  @stdin = StringIO.new
+  @stdout = StringIO.new
+  stdin input_codes.join("\n")+"\n\n"
+  @solver = Elus::Solver.new(stdin, stdout)
+  solver.start generator
+  solver.input_state
+end
+
+def generator
+  @generator ||= stub('generator', :generate_rules => [])
+end
+  
+def fixnum_from(string)
+  string.scan(/\d/).join.to_i
+end
+
+def messages_should_include(message)
+  @stdout.string.split("\n" ).should include(message)
+end
+
+def messages_include?(message)
+  @stdout.string.split("\n").include?(message)
+end
+
+def outputs_count(string, options={})
+  pattern = Regexp.new(options[:regex]? string : Regexp.escape(string))
+  @stdout.string.scan(pattern).size
+end
+
+def outputs_count_should_be_correct_for input_codes
+  # For each unique name corresponding to one of the input_codes
+  input_codes.map {|code| @code_names[code]}.uniq.each do |name| 
+    repeats = input_codes.count {|code| @code_names[code]==name}
+    name_feedback = Regexp.escape('You entered ') + '.*' + Regexp.escape(": #{name}")
+    outputs_count(name_feedback, :regex => true).should == repeats
+  end
+end
+
+Given /^I have not started yet$/ do
+end
+
+When /^I start Solver$/ do
+  solver.start generator
+end
+
+Then /^I should see "([^\"]*)"$/ do |message|
+  messages_should_include(message)
+end
+
+Given /^new Game just started$/ do
+  solver.start generator
+end
+
+When /^I input code (.*)$/ do |code|
+  stdin "#{code}\n"+"BYR\n"*6+"\n"
+  solver.input_state
+end
+
+When /^I run solver (.*) times and use (.*) correct codes to input state/ do |times, num_codes|
+  @times = fixnum_from(times)
+  @num_codes = fixnum_from(num_codes)
+  @code_names = ElusTest::CODES
+end
+
+Then /^I should see all the correct feedback, piece names and game states$/ do
+   @times.times do
+      #@code_names.keys.combination(@num_codes) do |input_codes|  # Takes too long to complete!
+      input_codes = Array.new(@num_codes) {|i| @code_names.keys[rand(@code_names.size)]}
+      solver_restart_and_input input_codes
+      
+      outputs_count_should_be_correct_for input_codes
+#      outputs_count('Free:').should == 1
+#      outputs_count('Board:').should == 1
+  end    
+  
+end
+
+Given /^Elus Game state is (.*)$/ do |state|
+  stdin state.split(' ').join("\n")+"\n\n"
+end
+
+Given /^Game started with (.*)$/ do |gen_type|
+  Generator = Elus.const_get gen_type
+  solver.start Generator.new
+end
+
+When /^I input Game state and prepare to move$/ do
+  solver.input_state
+  @stdin.reopen "\n\n" # Inputing zero code for first move
+  solver.make_move
+end
+
+Given /^Game state inputed$/ do
+  solver.input_state
+end
+
+When /^I move (.*)$/ do |piece|
+  @stdin.reopen(piece+"\nY\nSYC\nSYD\nBYC\n")
+  solver.make_move
+end
+

data/features/support/env.rb

@@ -0,0 +1,5 @@
+$LOAD_PATH << File.join(File.dirname(__FILE__),".." ,".." ,"lib" )
+require 'spec/stubs/cucumber'
+require File.join(File.dirname(__FILE__), "../../spec/spec_helper" )
+
+require 'elus'

data/features/support/stats.rb

@@ -0,0 +1,32 @@
+#module ElusTest
+#  class Stats
+#    def initialize(strings)
+#      @strings = strings
+#      @input_names.unique.each {|name| @counters[name]=0 }
+##      @input_names = @input_codes.map {|code| codetable[code]}
+##      @counters = {} 
+##      
+##      @counters["Free:"] = 0
+##      @counters["Board:"] = 0
+#      end
+#    end
+#    
+#    def puts(message)
+#      @counters.each do |name, counter|
+#        
+#      end
+#    end
+# 
+#    def count_for(code_or_name)
+#      
+#    end
+# 
+#    def correct?
+#      #    @feedback.should == @runs
+#      #  @piece.should == @runs
+#      #  @free.should == @runs
+#      #  @board.should == @runs
+#    end   
+#    
+#  end
+#end