trackler 2.0.6.41 → 2.0.6.42

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 8a0eb8e8f6259e62c8da17ca7ac0eefaba3d5e97
-  data.tar.gz: 47716a522574a595c6d5ee22065df620e969ffb4
+  metadata.gz: 916131843c14575716760142ef6a9c34ee3c9229
+  data.tar.gz: b089c28e26aaef73d1c9b3acfe246fbc848922a4
 SHA512:
-  metadata.gz: a223ce1ceebc06956d09fda5aee39e7227a773cbbe684f871f036ae05c0a18aea9aff606571237f2dae98c4bfabc6e97567a5392aa6837a78ddf47d705787bc2
-  data.tar.gz: 19a3b26186351a315f71436f3ad1d8a83119d7e95722304eb95c97ff1e1690a36a810d7194e4f37bf85ac1dc012221ef69406e4eaeef17eba262868ec8e87b3c
+  metadata.gz: af9588537b3e457dcc734647725966973ffb0ccab0f2f47bcc70dbb1fba5acd552a6b31f815886bb5875366718d6275392b0b3639ecb3ef1843a3e8158ebfcb6
+  data.tar.gz: 7a395dd3b5ce1115b073cad41b7c307b2381b475854a1bec2ff077cc6e739212148b5c89c459ec352043d0470be3fe5285b400cfc354e7e44634ce0b7da28b8c

data/common/CONTRIBUTING.md

@@ -38,6 +38,7 @@ themselves. There are other guides about contributing to other parts of the Exer
     * [Beta-Testing a Language Track](#beta-testing-a-language-track)
 * [Maintaining a Track](#maintaining-a-track)
 * [Useful Tidbits](#useful-tidbits)
+    * [Pull Request Guidelines](#pull-request-guidelines)
     * [Exercise Versioning](#exercise-versioning)
     * [Anatomy of an Exercise](#anatomy-of-an-exercise)
     * [config.json](#config-json)
@@ -591,6 +592,9 @@ scenarios in this guide.
 
 1. Put the name of the exercise in the subject line of the commit.
    E.g. `hamming: Add test case for strands of unequal length`
+1. The subject line should be a one-sentence summary, and should not include
+   the word *and* (explicitly or implied).
+1. Any extra detail should be provided in the body of the PR.
 1. Don't submit unrelated changes in the same pull request.
 1. If you had a bit of churn in the process of getting the change right,
    squash your commits.
@@ -598,6 +602,12 @@ scenarios in this guide.
    see two commits: First the refactoring, then the added behavior. It's
    fine to put this in the same pull request, unless the refactoring is
    huge and would make it hard to review both at the same time.
+1. If you are referencing another issue or pull-request, for instance
+   *closes #XXX* or *see #XXX*, please include the reference in the body of the PR,
+   rather than the subject line. This is simply because the subject line doesn't
+   support markdown, and so these don't get turned into clickable links. It makes
+   it harder to follow and to go look at the related issue or PR.
+1. Please also refer to the guidelines for [commit messages](#commit-messages).
 
 Once you've submitted a pull request, one or more of the track maintainers
 will review it. Some tracks are less active and might not have someone
@@ -748,9 +758,11 @@ Messages
 Suck?](https://www.youtube.com/watch?v=8YjSty6bfog).
 It's funny and enlightening, and you should watch it.
 
-Tim Pope wrote an article that has very clear guidelines about how to write
-excellent commit messages. [Please read
-it](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+Two articles that have very clear guidelines about how to write
+excellent commit messages are Tim Pope's
+[A Note About Git Commit Messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
+and Chris Beams' [How to Write a Git Commit Message](https://chris.beams.io/posts/git-commit/).
+Please read them.
 
 ##### Examples
 

data/common/README.md

@@ -47,9 +47,14 @@ variations.
 
 Each test case has the the following keys:
 - description: which will be used to name each generated test
+  - The description should not simply explain **what** each case is (that is redundant information)
+  - The description should explain **why** each case is there. For example, what kinds of implementation mistakes might this case help us find?
 - 'variable names': one or more variable names with values which will be passed to the solution method
-- expected: the expected result (this would be -1 when we expect an exception)
-- msg: a nice message for the failing case
+- expected: the expected result
+  - if the input is valid but there is no result for the input, the value at `"expected"` should be `null`.
+  - if an error is expected (because the input is invalid, or any other reason), the value at `"expected"` should be an object containing exactly one property, `"error"`, whose value is a string.
+    - The string should explain why the error would occur.
+    - A particular track's implementation of the exercise **need not** necessarily check that the error includes that exact string as the cause, depending on what is idiomatic in the language (it may not be idiomatic to check strings for error messages).
 
 ## Automated Tests
 

data/common/exercises/binary/.deprecated

@@ -0,0 +1,3 @@
+**NOTE: This exercise has been deprecated**
+Your track should implement "all-your-base" instead.
+https://github.com/exercism/x-common/issues/279

data/common/exercises/counter/.deprecated

@@ -1 +1,3 @@
 **NOTE: This exercise has been deprecated.**
+It was decided that Exercism should focus on exercises with provided test suites, rather than the reverse ("write the test suite").
+https://github.com/exercism/x-common/issues/80

data/common/exercises/hexadecimal/.deprecated

@@ -0,0 +1,3 @@
+**NOTE: This exercise has been deprecated**
+Your track should implement "all-your-base" instead.
+https://github.com/exercism/x-common/issues/279

data/common/exercises/luhn/description.md

@@ -7,62 +7,40 @@ The task is to check if a given string is valid.
 
 Validating a Number
 ------
+
 Strings of length 1 or less are not valid. Spaces are allowed in the input,
 but they should be stripped before checking. All other non-digit characters
 are disallowed.
 
-As an example of a valid string, here is a fictitious Canadian Social Insurance
-Number.
+## Example 1: valid credit card number
 
 ```
-046 454 286
+4539 1488 0343 6467
 ```
 
 The first step of the Luhn algorithm is to double every second digit,
 starting from the right. We will be doubling
 
 ```
-_4_ 4_4 _8_
+4_3_ 1_8_ 0_4_ 6_6_
 ```
 
 If doubling the number results in a number greater than 9 then subtract 9
 from the product. The results of our doubling:
 
 ```
-086 858 276
+8569 2478 0383 3437
 ```
 
-Then sum all of the digits
+Then sum all of the digits:
 
 ```
-0+8+6+8+5+8+2+7+6 = 50
+8+5+6+9+2+4+7+8+0+3+8+3+3+4+3+7 = 80
 ```
 
 If the sum is evenly divisible by 10, then the number is valid. This number is valid!
 
-An example of an invalid Canadian SIN where we've changed the final digit
-
-```
-046 454 287
-```
-
-Double the second digits, starting from the right
-
-```
-086 858 277
-```
-
-Sum the digits
-
-```
-0+8+6+8+5+8+2+7+7 = 51
-```
-
-51 is not evenly divisible by 10, so this number is not valid.
-
-----
-
-An example of an invalid credit card account
+## Example 2: invalid credit card number
 
 ```
 8273 1232 7352 0569
@@ -77,7 +55,7 @@ Double the second digits, starting from the right
 Sum the digits
 
 ```
-7+2+5+3+2+2+5+2+5+3+1+2+0+5+3+9 = 57
+7+2+5+3+2+2+6+2+5+3+1+2+0+5+3+9 = 57
 ```
 
 57 is not evenly divisible by 10, so this number is not valid.

data/common/exercises/octal/.deprecated

@@ -0,0 +1,3 @@
+**NOTE: This exercise has been deprecated**
+Your track should implement "all-your-base" instead.
+https://github.com/exercism/x-common/issues/279

data/common/exercises/point-mutations/.deprecated

@@ -1 +1,3 @@
 **NOTE: This exercise has been deprecated.**
+Your track should implement hamming instead.
+https://github.com/exercism/x-common/issues/184

data/common/exercises/trinary/.deprecated

@@ -0,0 +1,3 @@
+**NOTE: This exercise has been deprecated**
+Your track should implement "all-your-base" instead.
+https://github.com/exercism/x-common/issues/279

data/lib/trackler/version.rb

@@ -1,3 +1,3 @@
 module Trackler
-  VERSION = "2.0.6.41"
+  VERSION = "2.0.6.42"
 end

data/tracks/c/exercises/rna-transcription/test/test_rna_transcription.c

@@ -1,18 +1,17 @@
 #include "vendor/unity.h"
 #include "../src/rna_transcription.h"
 #include <stdlib.h>
-#include <string.h>
 
 void test_transcription(const char *dna, const char *expected)
 {
    char *rna = to_rna(dna);
-   TEST_ASSERT_TRUE(strncmp(rna, expected, strlen(dna)) == 0);
+   TEST_ASSERT_EQUAL_STRING(expected, rna);
    free(rna);
 }
 
 void test_failure(const char *dna)
 {
-   TEST_ASSERT_TRUE(to_rna(dna) == NULL);
+   TEST_ASSERT_NULL(to_rna(dna));
 }
 
 void test_transcribes_G_to_C(void)

data/tracks/ceylon/config.json

@@ -11,6 +11,14 @@
         "Integers"
       ]
     },
+    {
+      "slug": "hamming",
+      "difficulty": 2,
+      "topics": [
+        "Strings",
+        "Filtering"
+      ]
+    },
     {
       "slug": "sieve",
       "difficulty": 3,

data/tracks/ceylon/docs/ABOUT.md

@@ -0,0 +1,15 @@
+Ceylon is a general-purpose programming language featuring a syntax similar to Java and C#.
+It is imperative, statically-typed, block-structured, object-oriented, and higher-order.
+By _statically-typed_, we mean that the compiler performs extensive type checking, with
+the help of type annotations that appear in the code. By _object-oriented_, we mean that
+the language supports user-defined types and features a nominative type system where a type
+is a set of named attributes and operations, and that it supports inheritance and subtype
+polymorphism. By _higher-order_, we mean that every referenceable program element
+(every attribute, every operation, and every type) is also a value. By _block-structured_,
+we mean to say that the language features lexical scoping and an extremely regular recursive
+syntax for declarations and statements.
+
+Ceylon improves upon the Java language and type system to reduce verbosity and increase
+typesafety compared to Java and C#. Ceylon encourages a more functional, somewhat less
+imperative style of programming, resulting in code which is easier to reason about, and
+easier to refactor.

data/tracks/ceylon/docs/INSTALLATION.md

@@ -0,0 +1,9 @@
+The easiest way to install Ceylon is simply to **not** install it.
+You should be able to solve most of the exercises using our [web IDE](http://try.ceylon-lang.org/).
+
+However if you prefer, you can install the command line distribution; the easiest way to do that is via [SDKMAN](http://sdkman.io/),
+so you need to install that first if you don't have it yet, then just type `sdk install ceylon` at your terminal.
+
+OSX users can also install via the [Homebrew package manager](http://mxcl.github.com/homebrew/).
+
+Installation instructions for other platforms, as well as for the Ceylon IDE, a plugin for Eclipse, are available at [the official site](http://ceylon-lang.org/download/).

data/tracks/ceylon/docs/LEARNING.md

@@ -0,0 +1,7 @@
+The best way to get started with Ceylon right now is to read the [quick introduction](http://ceylon-lang.org/documentation/1.3/introduction/),
+then [take the tour](http://ceylon-lang.org/documentation/1.3/tour/) and/or [the walkthrough](http://ceylon-lang.org/documentation/1.3/walkthrough/).
+
+You can write and run your first programs in our [web IDE](http://try.ceylon-lang.org/)
+so you don't even have to install anything to get started.
+
+And of course you can contact the team and other users at our [Gitter page](https://gitter.im/ceylon/user).

data/tracks/ceylon/docs/TESTS.md

@@ -0,0 +1,11 @@
+## Running Ceylon Tests
+
+We run tests with the [ceylon test](https://ceylon-lang.org/documentation/reference/tool/ceylon/subcommands/ceylon-test.html) command.
+
+`ceylon test` expects a module name to run the tests on.
+In the Ceylon track, each exercise has just a single module.
+Therefore, you can run the tests with:
+
+```bash
+ceylon test $(basename source/*)
+```

data/tracks/ceylon/exercises/TRACK_HINTS.md

@@ -0,0 +1,11 @@
+## Running Ceylon Tests
+
+We run tests with the [ceylon test](https://ceylon-lang.org/documentation/reference/tool/ceylon/subcommands/ceylon-test.html) command.
+
+`ceylon test` expects a module name to run the tests on.
+In the Ceylon track, each exercise has just a single module.
+Therefore, you can run the tests with:
+
+```bash
+ceylon test $(basename source/*)
+```

data/tracks/ceylon/exercises/hamming/example/Hamming.ceylon

@@ -0,0 +1,8 @@
+class Error() {}
+
+Integer|Error distance(String s1, String s2) {
+  if (s1.size != s2.size) {
+    return Error();
+  }
+  return zipPairs(s1, s2).count(([c1, c2]) => c1 != c2);
+}

data/tracks/ceylon/exercises/hamming/source/hamming/Hamming.ceylon

@@ -0,0 +1,5 @@
+class Error() {}
+
+Integer|Error distance(String s1, String s2) {
+  return nothing;
+}

data/tracks/ceylon/exercises/hamming/source/hamming/HammingTest.ceylon

@@ -0,0 +1,30 @@
+import ceylon.test { ... }
+
+{[String, String, Integer?]*} cases => {
+  ["A", "A", 0],
+  ["GGACTGA", "GGACTGA", 0],
+  ["A", "G", 1],
+  ["AG", "CT", 2],
+  ["AT", "CT", 1],
+  ["GGACG", "GGTCG", 1],
+  ["ACCAGGG", "ACTATGG", 2],
+  ["AGA", "AGG", 1],
+  ["AGG", "AGA", 1],
+  ["TAG", "GAT", 2],
+  ["GATACA", "GCATAA", 4],
+  ["GGACGGATTCTG", "AGGACGGATTCT", 9],
+  ["", "", 0],
+  ["AATG", "AAA", null],
+  ["ATA", "AGTG", null]
+};
+
+test
+parameters(`value cases`)
+void testHamming(String s1, String s2, Integer? expected) {
+  value result = distance(s1, s2);
+  if (exists expected) {
+    assertEquals(result, expected);
+  } else if (!is Error result) {
+    fail("should have errored, but got ``result``");
+  }
+}

data/tracks/ceylon/exercises/hamming/source/hamming/module.ceylon

@@ -0,0 +1,3 @@
+module hamming "1.0" {
+  import "ceylon.test" "1.3.1";
+}

data/tracks/erlang/_test/check-exercises.escript

@@ -3,7 +3,7 @@
 main([])->
     main(["all"]);
 main(["all"]) ->
-    Examples = filelib:wildcard("exercises/*/rebar.conf"),
+    Examples = filelib:wildcard("exercises/*/rebar.config"),
     ExampleBasePaths = [extract_base_pathes(X) || X <- Examples],
     Exercises = [X -- "exercises/" || X <- ExampleBasePaths],
     run_exercises(Exercises);
@@ -15,7 +15,7 @@ main(["list"|Exercises]) ->
 
 extract_base_pathes(ConfPath) ->
     ConfPath1 = lists:reverse(ConfPath),
-    ConfPath2 = ConfPath1 -- "rebar.conf/",
+    ConfPath2 = ConfPath1 -- "rebar.config/",
     lists:reverse(ConfPath2).
 
 

data/tracks/erlang/exercises/{circular-buffer/rebar.conf → accumulate/rebar.config}

@@ -16,7 +16,7 @@
 ]}.
 
 %% eunit:test(Tests)
-{eunit_tests, [{application, beer_song}]}.
+{eunit_tests, []}.
 %% Options for eunit:test(Tests, Opts)
 {eunit_opts, [verbose]}.
 

data/tracks/erlang/exercises/allergies/{rebar.conf → rebar.config}

@@ -16,7 +16,7 @@
 ]}.
 
 %% eunit:test(Tests)
-{eunit_tests, [{application, allergies}]}.
+{eunit_tests, []}.
 %% Options for eunit:test(Tests, Opts)
 {eunit_opts, [verbose]}.
 

data/tracks/erlang/exercises/{accumulate/rebar.conf → anagram/rebar.config}

@@ -1,3 +1,5 @@
+%% -*- mode: erlang -*-
+
 %% Erlang compiler options
 {erl_opts, [debug_info]}.
 
@@ -16,7 +18,7 @@
 ]}.
 
 %% eunit:test(Tests)
-{eunit_tests, [{application, accumulate}]}.
+{eunit_tests, []}.
 %% Options for eunit:test(Tests, Opts)
 {eunit_opts, [verbose]}.
 

data/tracks/erlang/exercises/{bob/rebar.conf → atbash-cipher/rebar.config}

@@ -16,7 +16,7 @@
 ]}.
 
 %% eunit:test(Tests)
-{eunit_tests, [{application, beer_song}]}.
+{eunit_tests, []}.
 %% Options for eunit:test(Tests, Opts)
 {eunit_opts, [verbose]}.
 

data/tracks/erlang/exercises/{binary/rebar.conf → bank-account/rebar.config}

@@ -16,7 +16,7 @@
 ]}.
 
 %% eunit:test(Tests)
-{eunit_tests, [{application, beer_song}]}.
+{eunit_tests, []}.
 %% Options for eunit:test(Tests, Opts)
 {eunit_opts, [verbose]}.
 

data/tracks/erlang/exercises/beer-song/rebar.conf

@@ -16,7 +16,7 @@
 ]}.
 
 %% eunit:test(Tests)
-{eunit_tests, [{application, beer_song}]}.
+{eunit_tests, []}.
 %% Options for eunit:test(Tests, Opts)
 {eunit_opts, [verbose]}.
 

data/tracks/erlang/exercises/binary/rebar.config

@@ -0,0 +1,30 @@
+%% Erlang compiler options
+{erl_opts, [debug_info]}.
+
+{deps, []}.
+
+{dialyzer, [
+  {warnings, [underspecs, no_return]},
+  {get_warnings, true},
+  {plt_apps, top_level_deps}, % top_level_deps | all_deps
+  {plt_extra_apps, []},
+  {plt_location, local}, % local | "/my/file/name"
+  {plt_prefix, "rebar3"},
+  {base_plt_apps, [stdlib, kernel, crypto]},
+  {base_plt_location, global}, % global | "/my/file/name"
+  {base_plt_prefix, "rebar3"}
+]}.
+
+%% eunit:test(Tests)
+{eunit_tests, []}.
+%% Options for eunit:test(Tests, Opts)
+{eunit_opts, [verbose]}.
+
+%% == xref ==
+
+{xref_warnings, true}.
+
+%% xref checks to run
+{xref_checks, [undefined_function_calls, undefined_functions,
+  locals_not_used, exports_not_used,
+  deprecated_function_calls, deprecated_functions]}.

data/tracks/erlang/exercises/bob/rebar.config

@@ -0,0 +1,30 @@
+%% Erlang compiler options
+{erl_opts, [debug_info]}.
+
+{deps, []}.
+
+{dialyzer, [
+  {warnings, [underspecs, no_return]},
+  {get_warnings, true},
+  {plt_apps, top_level_deps}, % top_level_deps | all_deps
+  {plt_extra_apps, []},
+  {plt_location, local}, % local | "/my/file/name"
+  {plt_prefix, "rebar3"},
+  {base_plt_apps, [stdlib, kernel, crypto]},
+  {base_plt_location, global}, % global | "/my/file/name"
+  {base_plt_prefix, "rebar3"}
+]}.
+
+%% eunit:test(Tests)
+{eunit_tests, []}.
+%% Options for eunit:test(Tests, Opts)
+{eunit_opts, [verbose]}.
+
+%% == xref ==
+
+{xref_warnings, true}.
+
+%% xref checks to run
+{xref_checks, [undefined_function_calls, undefined_functions,
+  locals_not_used, exports_not_used,
+  deprecated_function_calls, deprecated_functions]}.

data/tracks/erlang/exercises/circular-buffer/rebar.config

@@ -0,0 +1,30 @@
+%% Erlang compiler options
+{erl_opts, [debug_info]}.
+
+{deps, []}.
+
+{dialyzer, [
+  {warnings, [underspecs, no_return]},
+  {get_warnings, true},
+  {plt_apps, top_level_deps}, % top_level_deps | all_deps
+  {plt_extra_apps, []},
+  {plt_location, local}, % local | "/my/file/name"
+  {plt_prefix, "rebar3"},
+  {base_plt_apps, [stdlib, kernel, crypto]},
+  {base_plt_location, global}, % global | "/my/file/name"
+  {base_plt_prefix, "rebar3"}
+]}.
+
+%% eunit:test(Tests)
+{eunit_tests, []}.
+%% Options for eunit:test(Tests, Opts)
+{eunit_opts, [verbose]}.
+
+%% == xref ==
+
+{xref_warnings, true}.
+
+%% xref checks to run
+{xref_checks, [undefined_function_calls, undefined_functions,
+  locals_not_used, exports_not_used,
+  deprecated_function_calls, deprecated_functions]}.

data/tracks/erlang/exercises/clock/rebar.config

@@ -0,0 +1,30 @@
+%% Erlang compiler options
+{erl_opts, [debug_info]}.
+
+{deps, []}.
+
+{dialyzer, [
+  {warnings, [underspecs, no_return]},
+  {get_warnings, true},
+  {plt_apps, top_level_deps}, % top_level_deps | all_deps
+  {plt_extra_apps, []},
+  {plt_location, local}, % local | "/my/file/name"
+  {plt_prefix, "rebar3"},
+  {base_plt_apps, [stdlib, kernel, crypto]},
+  {base_plt_location, global}, % global | "/my/file/name"
+  {base_plt_prefix, "rebar3"}
+]}.
+
+%% eunit:test(Tests)
+{eunit_tests, []}.
+%% Options for eunit:test(Tests, Opts)
+{eunit_opts, [verbose]}.
+
+%% == xref ==
+
+{xref_warnings, true}.
+
+%% xref checks to run
+{xref_checks, [undefined_function_calls, undefined_functions,
+  locals_not_used, exports_not_used,
+  deprecated_function_calls, deprecated_functions]}.

data/tracks/erlang/exercises/difference-of-squares/rebar.config

@@ -0,0 +1,30 @@
+%% Erlang compiler options
+{erl_opts, [debug_info]}.
+
+{deps, []}.
+
+{dialyzer, [
+  {warnings, [underspecs, no_return]},
+  {get_warnings, true},
+  {plt_apps, top_level_deps}, % top_level_deps | all_deps
+  {plt_extra_apps, []},
+  {plt_location, local}, % local | "/my/file/name"
+  {plt_prefix, "rebar3"},
+  {base_plt_apps, [stdlib, kernel, crypto]},
+  {base_plt_location, global}, % global | "/my/file/name"
+  {base_plt_prefix, "rebar3"}
+]}.
+
+%% eunit:test(Tests)
+{eunit_tests, []}.
+%% Options for eunit:test(Tests, Opts)
+{eunit_opts, [verbose]}.
+
+%% == xref ==
+
+{xref_warnings, true}.
+
+%% xref checks to run
+{xref_checks, [undefined_function_calls, undefined_functions,
+  locals_not_used, exports_not_used,
+  deprecated_function_calls, deprecated_functions]}.

data/tracks/erlang/exercises/etl/rebar.config

@@ -0,0 +1,30 @@
+%% Erlang compiler options
+{erl_opts, [debug_info]}.
+
+{deps, []}.
+
+{dialyzer, [
+  {warnings, [underspecs, no_return]},
+  {get_warnings, true},
+  {plt_apps, top_level_deps}, % top_level_deps | all_deps
+  {plt_extra_apps, []},
+  {plt_location, local}, % local | "/my/file/name"
+  {plt_prefix, "rebar3"},
+  {base_plt_apps, [stdlib, kernel, crypto]},
+  {base_plt_location, global}, % global | "/my/file/name"
+  {base_plt_prefix, "rebar3"}
+]}.
+
+%% eunit:test(Tests)
+{eunit_tests, []}.
+%% Options for eunit:test(Tests, Opts)
+{eunit_opts, [verbose]}.
+
+%% == xref ==
+
+{xref_warnings, true}.
+
+%% xref checks to run
+{xref_checks, [undefined_function_calls, undefined_functions,
+  locals_not_used, exports_not_used,
+  deprecated_function_calls, deprecated_functions]}.

data/tracks/erlang/exercises/gigasecond/rebar.config

@@ -0,0 +1,30 @@
+%% Erlang compiler options
+{erl_opts, [debug_info]}.
+
+{deps, []}.
+
+{dialyzer, [
+  {warnings, [underspecs, no_return]},
+  {get_warnings, true},
+  {plt_apps, top_level_deps}, % top_level_deps | all_deps
+  {plt_extra_apps, []},
+  {plt_location, local}, % local | "/my/file/name"
+  {plt_prefix, "rebar3"},
+  {base_plt_apps, [stdlib, kernel, crypto]},
+  {base_plt_location, global}, % global | "/my/file/name"
+  {base_plt_prefix, "rebar3"}
+]}.
+
+%% eunit:test(Tests)
+{eunit_tests, []}.
+%% Options for eunit:test(Tests, Opts)
+{eunit_opts, [verbose]}.
+
+%% == xref ==
+
+{xref_warnings, true}.
+
+%% xref checks to run
+{xref_checks, [undefined_function_calls, undefined_functions,
+  locals_not_used, exports_not_used,
+  deprecated_function_calls, deprecated_functions]}.