Issues (problems) for Codebattle games
Clojure Makefile
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
bin
cm
issues
source
src/battle_asserts
test Fix namespaces: remove ':include-macros true' Feb 15, 2016
.gitignore
.travis.yml
Dockerfile
LICENSE
Makefile
README.md
Vagrantfile
issue.example.yml
project.clj

README.md

Build Status Hexlet chat

Setup for development

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Make changes
  4. Run tests (make test).
  5. Commit your changes (git commit -am 'Added some feature')
  6. Push to the branch (git push origin my-new-feature)
  7. Create new Pull Request
  8. Check if Request passed Travis-Ci

How to add a new problem

You have to write the description of the problem and the correct implementation. See examples in src/battle_asserts/issues. Corresponding tests are in test/battle_asserts/issues.

A problem file includes:

  • level — difficulty of the problem; possible values are elementary, easy, medium, hard.
  • description — detailed description of the problem.
  • test-data — data in a specified format which will be used to test solutions. The first element in this list will be displayed as an example to players, so it should clarify and illustrate the problem as much as possible. Do not choose a trivial case for this example.
  • arguments-generator — arguments generator for the solution function; generated arguments will be used to test players' solutions.
  • solution — implemented correct solution.

Test file includes a call to a test generator (the same for all tests).

Related links

Leiningen

Bitdeli Badge