All projects
Note: artifacts in italics are non-canonical forks. See the wiki for more details.
Displaying projects 24501 - 24520 of 32045
- org.clojars.voltron42/dao-clj 0.1.2-SNAPSHOT
Wrapper for database interaction via jdbc
voltron422018-05-23 - org.clojars.voltron42/yardstick 0.1.0-SNAPSHOT
Yardstick is an implementation of Gauge testing in Clojure. Yardstick is built to run any valid Gauge ".spec" test files.
voltron422018-05-08
License compliance tool to identify dependencies license names and types: permissive, copyleft, proprietory, etc.
vrs2022-12-26 - org.clojars.vshender/clojure-contrib 1.2.0-SNAPSHOT
Clojure user contributions library.
vshender2010-07-28
Avoid the hassle of restructuring comments into functions. Testify turns selected comments into automatically evaluated scripts, while remaining as comments embedded within the code. Evaluate these comments directly from within a test, or in any other way preferred. Rename the (comment) to (test-comment) and evaluate with (eval-in-ns 'your-namespace). Testify will find the test-comment and evaluate its content for you. The test-comment is an empty macro ignoring its body, just like comment, that Testify recognizes. Testify can easily be told to evaluate content of any other top level form, while test-comment is a default. Testify use levels of isolation. While eval-in-ns evaluates expressions in its namespace, like when evaluating comments manually, its sibling eval-as-use evaluates from within a temporary namespace, preventing pollution. This is more suitable for repeatable tests. Testify reads source code, and keeps track of where it is. Code should be highlighted when a test assertion fails, even though the assertion is in a comment. Testify is not a testing framework, but rather a pun on: to witness, reveal comment, display it in the repl.
vstein2024-04-19