The combined power of JUnit, Guice and Mockito. Plus it sounds like a cool martial art.
So you started using dependency injection because somebody told you it would make your tests simpler? But as you gaze at your deep hierarchy of test classes, "simple" is not exactly the word you think of. Plus, creating a new mock whenever you add a parameter to an injected constructor gets old very quickly.
You are not alone! And Jukito was created specifically for people like you. Read on, or get started right away!
If you use Google Guice, or if your GWT application uses Gin, then Jukito is the perfect antidote to your unit testing headaches. Now you can write tests like this:
@RunWith(JukitoRunner.class)
public class EmailSystemTest {
@Inject EmailSystemImpl emailSystem;
Email dummyEmail;
@Before
public void setupMocks(
IncomingEmails incomingEmails,
EmailFactory factory) {
dummyEmail = factory.createDummy();
when(incomingEmails.count()).thenReturn(1);
when(incomingEmails.get(0)).thenReturn(dummyEmail);
}
@Test
public void shouldFetchEmailWhenStarting(
EmailView emailView) {
// WHEN
emailSystem.start();
// THEN
verify(emailView).addEmail(dummyEmail);
}
}
That's right, Jukito lets you @Inject fields exactly as if your test class was injected with Guice. You can also inject parameters into your @Test, @Before and @After methods. Guice's just-in-time binding automatically instantiate your concrete classes, like EmailFactory. What about interfaces like IncomingEmails or EmailView? Jukito mocks them out automatically for you using mockito!
Let's look at another example:
@RunWith(JukitoRunner.class)
public class CalculatorTest {
public static class Module extends JukitoModule {
protected void configureTest() {
bindMany(Calculator.class,
ScientificCalculator.class,
BusinessCalculator.class);
bindManyInstances(AdditionExample.class,
new AdditionExample(1, 1, 2),
new AdditionExample(10, 10, 20),
new AdditionExample(18, 24, 42));
}
}
@Test
public void testAdd(@All Calculator calculator, @All AdditionExample example) {
// WHEN
int result = calculator.add(example.a, example.b);
// THEN
assertEquals(example.expected, result);
}
}
As you see here, Jukito lets you define your very own test module, where you can bind classes just like a regular Guice module. It doesn't stop there, however. The bindMany methods let you bind different classes or instances to the same interface. Combined with the powerful @All annotation this lets you easily run a single test on a whole suite of test examples. The code above will run a total of six tests!
Getting Started
Read the wiki to find out everything Jukito has to offer, and join the discussion!
Latest Release
- 1.5
Links
- Jukito Custom Google Search - Search GWTP documentation, wiki and thread collections.
- Jukito WebSite Source - Jukito website source.
- Jukito Google Group - Find help here.
- Jukito Previous Repo - Previous home of Jukito.
- GWTP - Find out more about GWT-Platform.
2 Sep 9, 2022
43 Dec 23, 2022
21 Sep 15, 2022
2 Dec 16, 2022
605 Dec 30, 2022
11 Jan 2, 2023
13 Dec 17, 2022
3 Aug 29, 2022
32.9k Dec 31, 2022
3.6k Jan 5, 2023
2.3k Dec 31, 2022
1.6k Dec 21, 2022
19 Sep 23, 2022
411 Jan 3, 2023
35 Nov 29, 2022
110 Jan 4, 2023
7 Apr 1, 2022
5 Jun 23, 2022
16 Dec 13, 2022