Comments on: Interceptors in JUnit

By: Testing the testers: code samples from a TDD framework comparison | Xebia Blog

Fri, 27 Nov 2009 01:04:24 +0000

[...] 4.7 of JUnit introduced rules, sort-of around aspects that are called before and after the execution of a test. Some of the [...]

By: Neale

Neale — Thu, 03 Sep 2009 13:48:45 +0000

I’m wondering if the example you give in the release notes helps solve the downside of @Test(expect=SomeException.class), which can pass if the expected exception is thrown from the wrong place.

Would the following be valid:
@Rule
public ExpectedException thrown= ExpectedException.none();

@Test
public void throwsNullPointerExceptionWithMessage() {
maybeThrowNPE(); // should fail if this does throw NPE..?
thrown.expect(NullPointerException.class);
throw new NullPointerException();
}

By: Functional HTTP testing revisited using JUnit 4.7 Interceptors « Alistair Israel

Thu, 03 Sep 2009 03:07:59 +0000

[...] Interceptors in JUnit 2 JUnit 4.7: Interceptors: expected exceptions Posted by Alistair Filed in Uncategorized [...]

By: A.Clark

A.Clark — Sat, 01 Aug 2009 11:07:04 +0000

That’s awesome ! I can’t expect to use this new feature

By: JUnit 4.7RC-1 Rules « Cato’s Place

JUnit 4.7RC-1 Rules « Cato’s Place — Fri, 24 Jul 2009 14:57:41 +0000

[...] start with I begun reading Kent Beck’s blog entry about Inteceptors in JUnit which was originally written prior to the renaming of Inteceptors to [...]

By: JUnit Max » Blog Archive » The Open/Closed/Open Principle

JUnit Max » Blog Archive » The Open/Closed/Open Principle — Mon, 22 Jun 2009 11:45:37 +0000

[...] thoroughly we made sure the new tests worked alongside older tests. For the recent introduction of interceptors, though, we carefully isolated the code that ran tests and made it modular before finding a new way [...]

By: The Green Bar » Blog Archive » JUnit 4.7: Interceptors: expected exceptions

Wed, 27 May 2009 04:49:15 +0000

[...] the latest snapshot build of JUnit 4.7, we’ve re-implemented expected exceptions using Interceptors. Share and [...]

By: JUnit Max » Blog Archive » Three Designing Bears

JUnit Max » Blog Archive » Three Designing Bears — Wed, 06 May 2009 21:06:59 +0000

[...] and skill). All this goes to reduce the cost of slow and careful design. Last week we added interceptors. This is a change that has been percolating for a couple of years. Taking that long to actually try [...]

By: The Green Bar » Blog Archive » Interceptors in JUnit 4.7

The Green Bar » Blog Archive » Interceptors in JUnit 4.7 — Tue, 05 May 2009 20:16:52 +0000

[...] both of you that read this blog, and haven’t already seen it, there’s some fun stuff brewing in JUnit [...]

By: Daniel Brolund

Daniel Brolund — Thu, 30 Apr 2009 15:26:27 +0000

Looks like a giant leap in a good direction. How does the abstraction carry to suites?

I dream of being able to annotate a listener on the root suite, and then get all the events: before/after suite, test case, test method (fail/success).

Would that be possible?