An RSpec and Cucumber inspired testing framework for Java with the goal of helping better designs emerge through expressive tests
import com.xdd.Spec;
import static org.junit.Assert.*;
public class CalculatorSpec extends Spec {{
it("calculates the sum of positive numbers", () -> {
Calculator calculator = new Calculator();
int result = calculator.add(2, 2);
assertEquals(4, result);
});
context("The calculation of negative numbers", () -> {
it("calculates sum of negative numbers", () -> {
Calculator calculator = new Calculator();
int result = calculator.add(-2, 2);
assertEquals(0, result);
});
}
describe("calculating the sum of positive numbers", () -> {
given("a stateless calculator", () -> {
return new Calculator();
});
when("I add two positive numbers", calculator -> {
return calculator.add(2, 2);
});
then("I should have the correct sum", sum -> {
assertEquals(4, sum);
});
});
} }This DSL is emerging, but this is the flavor of it's intent.
I find great value in tests that are communicative. I never realized this value until working with RSpec.
If you haven't yet tried RSpec, I suggest you do. I also suggest reading the RSpec book. It might just change the way you write code.
For me, BDD has provided a greater level of visibility into the design of what I'm building. I look to my tests to tell me things about my design. If a test is difficult to setup, something might be wrong with my design. If the methods of the component I'm testing don't seem cohesive, there might be something wrong with my design. There are several little heuristics like this that guide me as I'm developing and I've found that they ultimately lead me to better designs had I not payed close attention to them.
That being said, I've looked for a communicative tool like this in Java and haven't found one I've liked. In Scala, I'm fond of Scala Test but there are times (and teams) where adding another language into the mix can cause a bit of complexity that some aren't comfortable with. I do (at times) enjoy working with Cucumber (and Cucumber JVM) but find that this tool is best suited when collaborating with others at a less technical level than I usually find myself working in while in a tool like RSpec.
The goal of emerge is to provide a tool that allows TDD/BDD practitioners to better express the intent of what they're developing in Java.
I welcome any and all feedback and welcome all contributions to emerge so long as those who use emerge agree that these contributions align with this goal.
(Gradle & Maven instructions to come)