- https://github.com/Abica/ruby-99-problems
- https://github.com/hcf/99-problems-in-Ruby
- https://github.com/kevinrutherford/rrwb-code
- https://github.com/lisafrench/JavaScriptExercises
- https://github.com/beastaugh/js-programming-exercises
- https://github.com/timestep/javascript-exercises
- https://github.com/wvmitchell/javascript
- Install leiningen
- Fork it
- Create your feature branch (
git checkout -b my-new-feature
) - Make changes
- Run tests (
lein test
). - Commit your changes (
git commit -am 'Added some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create new Pull Request
- Check if Request passed Travis-Ci
- Create yaml file with the name of your issue. Look at the example
level: easy # (elementary|easy|medium|hard) tags: [string, numbers] description: this is description author: github_nickname: your_name web_page: "http://your.site" checks: ruby: assert_equal 0, fibo_finder(0) assert_equal 1, fibo_finder(1) assert_equal 3, fibo_finder(4) assert_equal 13, fibo_finder(7) assert_equal 55, fibo_finder(10) multicode_checks: langs: [javascript] #[ruby, javascript, python, php]
If you need special things in your task, such as some Ruby objects, write asserts in "checks:" section. If your task is multiplatform write asserts in "multicode_checks:" section.
-
Create a .clj file in the test/battle_solutions folder, e.g. array_fetch_test.clj
-
Write a test by defining a function (deftest test-asserts ()) Look at the example
(deftest test-asserts
(let [arr [\a \b \c]]
(assert-equal \b (fetch arr 1 \d))
(assert-equal \d (fetch arr 5 \d))
(assert-equal \c (fetch arr -1 \d))
(assert-equal \d (fetch arr -5 \d))))
- Write a namespace with your issue name
(ns battle-solutions.array-fetch-test
(:require [clojure.test :refer :all]
[battle-asserts.test-helper :refer [assert-equal assert]]))
- Write a function to resolve your tests
(defn fetch
[s index default]
(let [positive-index (if (> index 0) index (+ (count s) index))]
(nth s positive-index default)))
- Run tests
lein test
If you want to run test for only one issue - use lein test + namespace
lein test battle-solutions.array-fetch-test
- Run code format
make format