trackler 2.0.8.16 → 2.0.8.17

data/common/exercises/sum-of-multiples/canonical-data.json

@@ -1,64 +1,90 @@
 {
-    "cases": [
-        {
-            "factors": [3, 5],
-            "limit": 1,
-            "expected": 0
-        },
-        {
-            "factors": [3, 5],
-            "limit": 4,
-            "expected": 3
-        },
-        {
-            "factors": [3, 5],
-            "limit": 10,
-            "expected": 23
-        },
-        {
-            "factors": [3, 5],
-            "limit": 100,
-            "expected": 2318
-        },
-        {
-            "factors": [3, 5],
-            "limit": 1000,
-            "expected": 233168
-        },
-        {
-            "factors": [7, 13, 17],
-            "limit": 20,
-            "expected": 51
-        },
-        {
-            "factors": [4, 6],
-            "limit": 15,
-            "expected": 30
-        },
-        {
-            "factors": [5, 6, 8],
-            "limit": 150,
-            "expected": 4419
-        },
-        {
-            "factors": [5, 25],
-            "limit": 51,
-            "expected": 275
-        },
-        {
-            "factors": [43, 47],
-            "limit": 10000,
-            "expected": 2203160
-        },
-        {
-            "factors": [1],
-            "limit": 100,
-            "expected": 4950
-        },
-        {
-            "factors": [],
-            "limit": 10000,
-            "expected": 0
-        }
-    ]
+  "exercise": "sum-of-multiples",
+  "version": "1.0.0",
+  "cases": [
+    {
+      "description": "multiples of 3 or 5 up to 1",
+      "property": "sum",
+      "factors": [3, 5],
+      "limit": 1,
+      "expected": 0
+    },
+    {
+      "description": "multiples of 3 or 5 up to 4",
+      "property": "sum",
+      "factors": [3, 5],
+      "limit": 4,
+      "expected": 3
+    },
+    {
+      "description": "multiples of 3 or 5 up to 10",
+      "property": "sum",
+      "factors": [3, 5],
+      "limit": 10,
+      "expected": 23
+    },
+    {
+      "description": "multiples of 3 or 5 up to 100",
+      "property": "sum",
+      "factors": [3, 5],
+      "limit": 100,
+      "expected": 2318
+    },
+    {
+      "description": "multiples of 3 or 5 up to 1000",
+      "property": "sum",
+      "factors": [3, 5],
+      "limit": 1000,
+      "expected": 233168
+    },
+    {
+      "description": "multiples of 7, 13 or 17 up to 20",
+      "property": "sum",
+      "factors": [7, 13, 17],
+      "limit": 20,
+      "expected": 51
+    },
+    {
+      "description": "multiples of 4 or 6 up to 15",
+      "property": "sum",
+      "factors": [4, 6],
+      "limit": 15,
+      "expected": 30
+    },
+    {
+      "description": "multiples of 5, 6 or 8 up to 150",
+      "property": "sum",
+      "factors": [5, 6, 8],
+      "limit": 150,
+      "expected": 4419
+    },
+    {
+      "description": "multiples of 5 or 25 up to 51",
+      "property": "sum",
+      "factors": [5, 25],
+      "limit": 51,
+      "expected": 275
+    },
+    {
+      "description": "multiples of 43 or 47 up to 10000",
+      "property": "sum",
+      "factors": [43, 47],
+      "limit": 10000,
+      "expected": 2203160
+    },
+    {
+      "description": "multiples of 1 up to 100",
+      "property": "sum",
+      "factors": [1],
+      "limit": 100,
+      "expected": 4950
+    },
+    {
+      "description": "multiples of an empty list up to 10000",
+      "property": "sum",
+      "factors": [],
+      "limit": 10000,
+      "expected": 0
+    }
+  ]
 }

data/lib/trackler/version.rb

@@ -1,3 +1,3 @@
 module Trackler
-  VERSION = "2.0.8.16"
+  VERSION = "2.0.8.17"
 end

data/tracks/elixir/docs/INSTALLATION.md

@@ -1,3 +1,5 @@
 ### Installation
 
 Detailed installation instructions can be found at [http://elixir-lang.org/install.html](http://elixir-lang.org/install.html).
+
+Help can be found on [Exercism's BEAM Gitter channel](https://gitter.im/exercism/xerlang)

data/tracks/elixir/docs/LEARNING.md

@@ -8,3 +8,5 @@ Exercism provides exercises and feedback but can be difficult to jump into for t
 * [Etudes for Elixir](http://chimera.labs.oreilly.com/books/1234000001642), by J. David Eisenberg (exercise companion for Intro to Elixir)
 * [Elixir School](https://elixirschool.com)
 * [Elixir Examples](https://elixir-examples.github.io/)
+* [Exercism's BEAM Gitter channel](https://gitter.im/exercism/xerlang)
+* [Elixir Forum](https://elixirforum.com/)

data/tracks/elixir/docs/RESOURCES.md

@@ -17,3 +17,11 @@
 ## Slack
 
 * [Request an Invite](https://elixir-slackin.herokuapp.com/)
+
+## Exercism's BEAM Gitter Channel
+
+* [Gitter channel](https://gitter.im/exercism/xerlang)
+
+## Elixir Forum
+
+* [Elixir Forum](https://elixirforum.com/)

data/tracks/groovy/docs/ABOUT.md

@@ -2,7 +2,7 @@
 
 Groovy is aimed at improving developer productivity thanks to a concise, easy to learn syntax.  It facilitates scripting, Domain-Specific Language authoring, runtime and compile-time meta-programming, and functional programming.
 
-It allows access to the entire ecosystem of Java libraries, integrates seamlessly with Java applications.
+It allows access to the entire ecosystem of Java libraries, and integrates seamlessly with Java applications.
 
 It can be used as a simple scripting language or added to complicated Java frameworks.  It powers technologies like Gradle, Spock, Ratpack, Grails, and scripting in Jenkins.
 

data/tracks/groovy/docs/LEARNING.md

@@ -1,16 +1,17 @@
 Interested in getting started with Groovy, or learning more while you work on exercises?
 
-Try out Groovy
+Try out Groovy with
 
-* [in a browser](https://www.jdoodle.com/execute-groovy-online)
-* opening the [Groovy Console](http://groovy-lang.org/groovyconsole.html) with `groovyConsole`
-* opening the [Groovy Shell](http://groovy-lang.org/groovyconsole.html) with `groovysh`
+* [a browser using an online interpreter](https://www.jdoodle.com/execute-groovy-online)
+* [the Groovy Console](http://groovy-lang.org/groovyconsole.html) by typing `groovyConsole` at a command line
+* [the Groovy Shell](http://groovy-lang.org/groovyconsole.html) by typing `groovysh` at a command line
 
 Take a quick tour of Groovy with
 
 * Tim Rows' [Groovy Tutorial for Java Developers](https://www.timroes.de/2015/06/27/groovy-tutorial-for-java-developers/) is equally good for non-Java developers
 * [Learn X in Y minutes, Where X=Groovy ](https://learnxinyminutes.com/docs/groovy/)
 * SmartThings' [Groovy Basics](http://docs.smartthings.com/en/latest/getting-started/groovy-basics.html)
+* a few of JDriven's [online Groovy Koans](http://www.groovy-koans.org/)
 
 Dive deeper with
 

data/tracks/groovy/docs/RESOURCES.md

@@ -5,12 +5,19 @@
 * the official [Groovy Language Documentation](http://docs.groovy-lang.org/docs/latest/html/documentation/)
 * Apache's [Groovy Documentation](http://www.groovy-lang.org/documentation.html), including the great [Learn Groovy](http://www.groovy-lang.org/learn.html) section
 
-# Tools
+## Tools
 
 * [SDKman](http://sdkman.io/)
 * [Groovy Eclipse](https://github.com/groovy/groovy-eclipse/wiki)
 * [IntelliJ Idea](https://www.jetbrains.com/idea/download/)
 
+## Technologies
+
+* [Gradle](https://gradle.org/), One Build Tool to Rule Them All
+* [Spock](http://spockframework.org/), The Next Generation of JVM language testing
+* [Ratpack](https://ratpack.io/), mini microservices with martinis
+* [Grails](https://grails.org/), "You must choose, but choose wisely."
+
 ## Collaboration
 
 * the [Groovy Community](http://www.groovy-lang.org/community.html) entry of the Groovy Language Documentation

data/tracks/rust/exercises/hello-world/GETTING_STARTED.md

@@ -18,141 +18,73 @@ Run the test suite. It can be run with `cargo`, which is installed with rust.
 $ cargo test
 ```
 
-This will fail, complaining that `hello-world` could not compile.
+This will compile the `hello-world` crate and run the test, which fails.
 
-To fix this, create a new directory called `src`.
-Create a new file called, `lib.rs`, inside the `src` directory.
-
-## Step 2
-
-Run the test again. It will give you a new error, another compile error.
-Our `lib.rs` does not contain any code, specifically the `hello()`
-function that our test is looking for.
-
-### Fixing the Error
-
-To fix it, open up the `src/lib.rs` file and add the following code:
-
-```rust
-pub fn hello(name: Option<&str>) -> String {
-    "".to_string()
-}
 ```
-
-Our test is looking for the `hello()` function from the `hello_world`
-crate. `lib.rs`, by default, is our crate root and our test
-is looking for the `hello()` function there.
-
-The code we are adding to `lib.rs` defines a public function (`pub fn`) that is called "hello".
-The function accepts a `name` as an optional argument (`Option`).
-The function returns a `String`.
-We start by returning an empty string (`"".to_string()`).
-
-## Step 3
-
-Run the test again.
-
-This time, code compilation will pass and we receive actual test failures.
-
-```
-running 3 tests
-test test_other_same_name ... ignored
-test test_sample_name ... ignored
-test test_no_name ... FAILED
+running 1 test
+test test_hello_world ... FAILED
 
 failures:
 
----- test_no_name stdout ----
-thread 'test_no_name' panicked at 'assertion failed: `(left == right)`
-(left: `"Hello, World!"`, right: `""`)', tests/hello-world.rs:5
-
+---- test_hello_world stdout ----
+thread 'test_hello_world' panicked at 'assertion failed: `(left == right)`
+(left: `"Hello, World!"`, right: `"Goodbye, World!"`)', tests/hello-world.rs:5
 
 failures:
-    test_no_name
+    test_hello_world
 
-test result: FAILED. 0 passed; 1 failed; 2 ignored; 0 measured
+test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured
 ```
 
 ### Understanding Test Failures
 
-Only one of the tests runs (`test_no_name`) and it fails. The other
-tests are ignored (more on that later).
-
-The `test_no_name` failure states that it is expecting the value,
-`"Hello, World!"`, to be returned from `hello("")`.
+The `test_hello_world` failure states that it is expecting the value,
+`"Hello, World!"`, to be returned from `hello()`.
 The left side of the assertion (at line 5) should be equal to the right side.
 
 ```
----- test_no_name stdout ----
-thread 'test_no_name' panicked at 'assertion failed: `(left == right)`
-(left: `"Hello, World!"`, right: `""`)', tests/hello-world.rs:5
+---- test_hello_world stdout ----
+thread 'test_hello_world' panicked at 'assertion failed: `(left == right)`
+(left: `"Hello, World!"`, right: `"Goodbye, World!"`)', tests/hello-world.rs:5
 ```
 
-To fix it, let's return `"Hello, World!"`, instead of an empty string
-(`""`) inside our `hello` function.
+### Fixing the Error
+
+To fix it, open up `src/lib.rs` and change the `hello` function to return
+`"Hello, World!"` instead of `"Goodbye, World!"`.
 
 ```rust
-pub fn hello(name: Option<&str>) -> String {
-    "Hello, World!".to_string()
+pub fn hello() -> &'static str {
+    "Hello, World!"
 }
 ```
 
-## Step 4
+## Step 2
 
 Run the test again. This time, it will pass.
 
 ```
-running 3 tests
-test test_other_same_name ... ignored
-test test_sample_name ... ignored
-test test_no_name ... ok
-
-test result: ok. 1 passed; 0 failed; 2 ignored; 0 measured
-
-   Doc-tests hello-world
-
 running 0 tests
 
 test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured
-```
-
-You may have noticed compiler warnings earlier:
 
-```
-Compiling hello-world v0.0.0
-(file:////exercism/exercises/rust/hello-world)
-src/lib.rs:1:14: 1:18 warning: unused variable: `name`, #[warn(unused_variables)] on by default
-src/lib.rs:1 pub fn hello(name: Option<&str>) -> String {
-                          ^~~~
-```
-
-Our `hello` function does not use the `name` argument so the
-compiler is letting us know that we could potentially remove the
-argument from our function (it likes "clean code").
-
-As we make the rest of the tests pass, we will find that we need the `name`
-argument, so don't delete it.
-
-Activate the next test. Open the `tests/hello-world.rs` file.
-Delete the `#[ignore]` line for the `test_sample_name` test.
+     Running target/debug/deps/hello_world-bd1f06dc726ef14f
 
-## Step 5
+running 1 test
+test test_hello_world ... ok
 
-Run the test suite again. Read the test failure and make the test pass.
+test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured
 
-As a reminder, the [rust book](http://doc.rust-lang.org/stable/book/README.html)
-is a good reference for understanding rust.
-The cargo output may also have hints to help you, depending on the errors you get.
-For example, `rustc --explain E0425` will explain unresolved name errors.
+   Doc-tests hello-world
 
-## Wash, Rinse, Repeat
+running 0 tests
 
-Delete one `#[ignore]`  at a time, and make each test pass before you move to
-the next one.
+test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured
+```
 
 ## Submit
 
-When everything is passing, you can submit your code with the following
+Once the test is passing, you can submit your code with the following
 command:
 
 ```

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: trackler
 version: !ruby/object:Gem::Version
-  version: 2.0.8.16
+  version: 2.0.8.17
 platform: ruby
 authors:
 - Katrina Owen