## Why is this an issue?

A common good practice is to write test methods targeting only one logical concept, that can only fail for one reason.

While it might make sense to have more than one assertion to test one concept, having too many is a sign that a test became too complex and should be refactored to multiples ones.

This rule will report any test method containing more than a given number of assertion.

### Noncompliant code example

With a parameter of 2.

    @Test
    void test() { // Refactor this method.
      assertEquals(1, f(1));
      assertEquals(2, f(2));
      assertEquals(3, g(1));
    }

### Compliant solution

    void test_f() {
      assertEquals(1, f(1));
      assertEquals(2, f(2));
    }
    void test_g() {
      assertEquals(3, g(1));
    }