A set of utilities to support test-driven development.
When creating unit tests, developers need data that is not critical to the test. As Brian Marick says, if we need data that is not critical, arbitrary data is most likely to uncover an error in our code. These utilities support generating this arbitrary data.
For now, I think that the core module will contain the most basic code: Generating random
- Integers
- Floating-point numbers
- Characters
- Dates
TODO: Guide users through getting your code up and running on their own system. In this section you can talk about:
- Installation process
- Software dependencies
- Latest releases
- API references
Build your project once in dev mode with the following script and then open index.html
in your browser.
./scripts/build
To auto build your project in dev mode:
./script/watch
To start an auto-building Node REPL (requires rlwrap, on OS X installable via brew):
./scripts/repl
To get source map support in the Node REPL:
lein npm install
To start a browser REPL:
- Uncomment the following lines in src/test_utils_cljs/core.cljs:
;; (defonce conn
;; (repl/connect "http://localhost:9000/repl"))
- Run
./scripts/brepl
- Browse to
http://localhost:9000
(you should seeHello world!
in the web console) - (back to step 3) you should now see the REPL prompt:
cljs.user=>
- You may now evaluate ClojureScript statements in the browser context.
For more info using the browser as a REPL environment, see this.
Clean project specific out:
lein clean
Build a single release artifact with the following script and then open index_release.html
in your browser.
./scripts/release
TODO: Explain how other users and developers can contribute to make your code better.
If you want to learn more about creating good readme files then refer the following guidelines. You can also seek inspiration from the below readme files:
Copyright © 2015 FIXME
Distributed under the Eclipse Public License either version 1.0 or (at your option) any later version.