trackler 2.1.0.11 → 2.1.0.12

data/tracks/r/docs/TESTS.md

@@ -2,4 +2,6 @@
 
 Each problem will have a script named something like `test_problem.R` (e.g. `test_hello-world.R`). In RStudio, you can simply run this script to test your solution. What this will do is load your solution code through the `source` command on the first line, and then the suite of `testthat` tests below.
 
+That can be conveniently done with [testthat's `auto_test` function](https://www.rdocumentation.org/packages/testthat/topics/auto_test). Because exercism code and tests are in the same folder, use this same path for both  `code_path` and `test_path` parameters. 
+
 If you prefer, you can also run the tests on the command line with `Rscript test_problem.R` (e.g. `Rscript test_hello-world.R`).

data/tracks/r/exercises/TRACK_HINTS.md

@@ -5,4 +5,4 @@ See [this guide](https://github.com/exercism/xr/blob/master/docs/INSTALLATION.md
 In each problem folder, there is a file named `<exercise_name>.R` containing a function that returns a `NULL` value. Place your implementation inside the body of the function.
 
 ## How to run tests
-Inside of RStudio, simply execute the `test_<exercise_name>.R` script. On the command-line, you can also run `Rscript test_<exercise_name>.R`.
+Inside of RStudio, simply execute the `test_<exercise_name>.R` script. This can be conveniently done with [testthat's `auto_test` function](https://www.rdocumentation.org/packages/testthat/topics/auto_test). Because exercism code and tests are in the same folder, use this same path for both  `code_path` and `test_path` parameters. On the command-line, you can also run `Rscript test_<exercise_name>.R`.

data/tracks/racket/docs/INSTALLATION.md

@@ -1,17 +1,27 @@
 Please reference Racket's [Getting Started](http://docs.racket-lang.org/getting-started/) page for instructions on downloading and installing Racket.
 
-For *nix variants, you can also install Racket using your OS' package manager:
+Alternative installation options and further notes for specific OSes follow.
 
-**OS X**
+## macOS
 
 Install via Homebrew:
 
 ```
 brew update
+brew install minimal-racket
+```
+The `minimal-racket` package will probably work for solving the problems, but it does not include the graphical interface IDE, DrRacket. If you want that, you have to install the full racket distribution from cask:
+
+```
+brew tap caskroom/cask
 brew install racket
 ```
 
-**Linux**
+### macOS official installer
+Note that on macOS, the official installer puts the files under `/Applications`, and as a result the `racket` and `raco` executables are not accessible on command-line terminals. You have to add the `bin` subdirectory below the Racket installation location (e.g., `/Applications/Racket v6.8/bin` for version 6.8) to the `$PATH`.  
+
+
+## Linux
 
 Debian:
 ```

data/tracks/ruby/README.md

@@ -12,19 +12,24 @@ the language, so you're all set.
 
 ## Anatomy of an Exercise
 
-The files for an exercise live in `exercises/<exercise_name>` (where
-`<exercise_name>` is the slug for the exercise, e.g. `clock` or
-`atbash-cipher`). All exercises have:
+The files for an exercise live in `exercises/<slug>`. The slug for an exercise
+is a unique nickname composed of a-z (lowercase) and -, e.g. `clock` or
+`atbash-cipher`. Inside its directory, each exercise has:
 
 * a test suite, `<exercise_name>_test.rb`
-* an example solution, `example.rb`
+* an example solution, `.meta/solutions/<exercise_name>.rb`
 
-Tests with a test generator will also have:
+where `<exercise_name>` is the underscored version of the exercise's slug, e.g.,
+`clock` or `atbash_cipher`.
 
-* a `.version`
-* the test generator, `<exercise_name>_cases.rb`, in `.meta/generator`
+If the exercise has a test generator, the directory will also contain:
 
-A few tests have other custom files which are discussed below.
+* `.version`
+* the test generator, `.meta/generator/<exercise_name>_case.rb`
+
+A few exercises use a custom test template:
+
+* `.meta/generator/test_template.erb`
 
 ### Canonical Data
 
@@ -45,6 +50,7 @@ rake test:clock
 
 To pass arguments to the test command, like `-p` for example, you can run
 the following:
+
 ```sh
 rake test:clock -- -p
 ```
@@ -91,13 +97,11 @@ tree -L 1 ~/code/exercism
 
 From within the xruby directory, run the following command:
 
-```
-bin/generate <exercise_name>
-```
+    bin/generate <slug>
 
 #### Changing a Generated Exercise
 
-Do not edit `<exercise_name>/<exercise_name>_test.rb`. Any changes you make will
+Do not edit `<slug>/<exercise_name>_test.rb`. Any changes you make will
 be overwritten when the test suite is regenerated.
 
 There are two reasons why a test suite might change:
@@ -109,7 +113,7 @@ In the first case, the changes need to be made to the `canonical-data.json` file
 the exercise, which lives in the x-common repository.
 
 ```
-../x-common/exercises/<exercise_name>/
+../x-common/exercises/<slug>/
 ├── canonical-data.json
 ├── description.md
 └── metadata.yml
@@ -122,20 +126,20 @@ exercise.
 Changes that don't have to do directly with the test inputs and outputs should
 be made to the exercise's test case generator, discussed
 in [implementing a new generator](#implementing-a-generator), next.  Then you
-can regenerate the exercise with `bin/generate <exercise_name>`.
+can regenerate the exercise with `bin/generate <slug>`.
 
 #### Implementing a Generator
 
 An exercise's test case generator class produces the code that goes inside
 the minitest `test_<whatever>` methods. An exercise's generator lives in
-`exercises/<exercise_name>/.meta/generator/<exercise_name>_cases.rb`.
+`exercises/<slug>/.meta/generator/<exercise_name>_case.rb`.
 
 The test case generator is a derived class of `ExerciseCase` (in
 `lib/generator/exercise_case.rb`). `ExerciseCase` does most of the work of
 extracting the canonical data. The derived class wraps the JSON for a single
 test case. The default version looks something like this:
 
-```
+```ruby
 require 'generator/exercise_case'
 
 class <ExerciseName>Case < Generator::ExerciseCase
@@ -148,9 +152,9 @@ class <ExerciseName>Case < Generator::ExerciseCase
 end
 ```
 
-where `<ExerciseName>` is the <exercise_name> slug in CamelCase. This is
-important, since the generator script will infer the name of the class from the
-<exercise_name> slug.
+where `<ExerciseName>` is the CamelCased version of the exercise's slug. This is
+important, since the generator script will infer the name of the class from
+`<slug>`.
 
 This class must provide the methods used by the test
 template. A
@@ -160,8 +164,10 @@ base class provides methods for the default template for everything except
 `#workload`.
 
 `#workload` generates the code for the body of a test, including the assertion
-and any setup required. The base class provides a variety of assertion and
-helper methods. Beyond that, you can implement any helper methods that you need
+and any setup required. The base class provides a variety of
+[assertion](https://github.com/exercism/xruby/blob/master/lib/generator/exercise_case/assertion.rb) and
+[helper](https://github.com/exercism/xruby/blob/master/lib/generator/exercise_case.rb) methods.
+Beyond that, you can implement any helper methods that you need
 as private methods in your derived class. See below for more information
 about [the intention of #workload](#workload-philosophy)
 

data/tracks/ruby/bin/generate

@@ -5,7 +5,7 @@ require 'generator'
 
 paths = Generator::Paths.new(track: XRUBY_ROOT, metadata: METADATA_REPOSITORY_PATH)
 
-generator = Generator::CommandLine.new(paths).parse(ARGV)
-exit 1 unless generator
+generators = Generator::CommandLine.new(paths).parse(ARGV)
+exit 1 unless generators
 
-generator.call
+generators.map(&:call)

data/tracks/ruby/config.json

@@ -4,6 +4,7 @@
   "repository": "https://github.com/exercism/xruby",
   "active": true,
   "gitter": "xruby",
+  "solution_pattern": "[Ee]xample|\\.meta/solutions/[^/]*\\.rb",
   "exercises": [
     {
       "slug": "hello-world",
@@ -59,12 +60,6 @@
       "topics": [
       ]
     },
-    {
-      "slug": "robot-name",
-      "difficulty": 1,
-      "topics": [
-      ]
-    },
     {
       "slug": "nth-prime",
       "difficulty": 1,
@@ -257,6 +252,12 @@
       "topics": [
       ]
     },
+    {
+      "slug": "robot-name",
+      "difficulty": 6,
+      "topics": [
+      ]
+    },
     {
       "slug": "queen-attack",
       "difficulty": 1,

data/tracks/ruby/exercises/alphametics/.meta/generator/test_template.erb

@@ -4,11 +4,11 @@ require_relative 'alphametics'
 
 # Common test data version: <%= canonical_data_version %> <%= abbreviated_commit_hash %>
 class AlphameticsTest < Minitest::Test
-<% test_cases.each do |test_case| %>
+<% test_cases.each_with_index do |test_case, idx| %>
 
 <%= test_case.runtime_comment %>
   def <%= test_case.name %>
-    <%= test_case.skipped %>
+    <%= test_case.skipped(idx) %>
     <%= test_case.workload %>
   end
 <% end %>

data/tracks/ruby/exercises/bowling/.meta/generator/test_template.erb

@@ -12,9 +12,9 @@ class BowlingTest < Minitest::Test
     rolls.each { |pins| @game.roll(pins) }
   end
 
-<% test_cases.each do |test_case| %>
+<% test_cases.each_with_index do |test_case, idx| %>
   def <%= test_case.name %>
-    <%= test_case.skipped %>
+    <%= test_case.skipped(idx) %>
     <%= test_case.workload %>
   end
 

data/tracks/ruby/exercises/connect/.meta/generator/test_template.erb

@@ -4,9 +4,9 @@ require_relative 'connect'
 
 # Common test data version: <%= canonical_data_version %> <%= abbreviated_commit_hash %>
 class ConnectTest < Minitest::Test
-<% test_cases.each do |test_case| %>
+<% test_cases.each_with_index do |test_case, idx| %>
   <%= test_case.ignore_method_length%>def <%= test_case.name %>
-    <%= test_case.skipped %><% test_case.test_body.each do |line| %>
+    <%= test_case.skipped(idx) %><% test_case.test_body.each do |line| %>
     <%= line %><% end %>
   end
 

data/tracks/ruby/exercises/dominoes/.meta/generator/test_template.erb

@@ -4,9 +4,9 @@ require_relative 'dominoes'
 
 # Common test data version: <%= canonical_data_version %> <%= abbreviated_commit_hash %>
 class DominoesTest < Minitest::Test
-<% test_cases.each do |test_case| %>
+<% test_cases.each_with_index do |test_case, idx| %>
   def <%= test_case.name %>
-    <%= test_case.skipped %>
+    <%= test_case.skipped(idx) %>
     <%= test_case.workload %>
   end
 

data/tracks/ruby/exercises/dominoes/dominoes_test.rb

@@ -2,7 +2,7 @@
 require 'minitest/autorun'
 require_relative 'dominoes'
 
-# Common test data version: 1.0.0 89a5281
+# Common test data version: 1.0.1 33f20d3
 class DominoesTest < Minitest::Test
   def test_empty_input_empty_output
     # skip
@@ -81,7 +81,7 @@ class DominoesTest < Minitest::Test
     assert_correct_chain(input_dominoes, output_chain)
   end
 
-  def test_ten_elements
+  def test_nine_elements
     skip
     input_dominoes = [[1, 2], [5, 3], [3, 1], [1, 2], [2, 4], [1, 6], [2, 3], [3, 4], [5, 6]]
     output_chain = Dominoes.chain(input_dominoes)

data/tracks/ruby/exercises/hello-world/.meta/generator/test_template.erb

@@ -14,9 +14,9 @@ end
 
 # Common test data version: <%= canonical_data_version %> <%= abbreviated_commit_hash %>
 class HelloWorldTest < Minitest::Test
-<% test_cases.each do |test_case| %>
+<% test_cases.each_with_index do |test_case, idx| %>
   def <%= test_case.name %>
-    <%= test_case.skipped %>
+    <%= test_case.skipped(idx) %>
     <%= test_case.workload %>
   end
 <% end %>

data/tracks/ruby/exercises/leap/.meta/generator/test_template.erb

@@ -13,9 +13,9 @@ class Date
 end
 
 class YearTest < Minitest::Test
-<% test_cases.each do |test_case| %>
+<% test_cases.each_with_index do |test_case, idx| %>
   def <%= test_case.name %>
-    <%= test_case.skipped %>
+    <%= test_case.skipped(idx) %>
     <%= test_case.workload %>, "<%= test_case.failure_message %>"
   end