What problem are you trying to solve?

Code readability by using JUnit built-in features.

When using JUnit (and possibly other test frameworks too) one can use expected=... argument to the @Test annotation. Instead of manually handling the failure/success expectations in the test code with try catch.

What precondition(s) should be checked before applying this recipe?

No other checks being done, incl. no checks for the specific content of the Exception objects, etc.

Describe the situation before applying the recipe

    @Test
    public void test() {
        try {
            // ... some code here
            fail("should have thrown an exception");
        } catch (Exception e) {
            // expected
        }
    }

Describe the situation after applying the recipe

    @Test(expected = Exception.class)
    public void test() {
        // ... some code here
    }

OSS repro

Example:

• https://github.com/pmem/llpl/blob/e77257eba460d4969450a30290bf31361d02a8dd/src/test/java/com/intel/pmem/llpl/LongLinkedListPersistentTests.java#L193-L205 although this one uses some strange Assert.assertTrue(true); which would probably prevent the recipe from making any changes here