Motivation

IntegrationTest maintenance is difficult, because they depend on the systems they integrate.

Failures of the system that is integrated causes IntegrationTests to fail. This becomes an issue if there are dozens of tests in the project that depend on multiple systems, because each failing Tests must be checked if the failure is caused by the integrated system, or if there was a bug introduced in the previous day.

To solve this problem it should be possible to define a Condition that will be executed before any test is started.
The test that has a Condition defined will be executed only if the Condition execution was successful.
If the condition fails the user should be notified about that (a separate ConditionTest would be failing).

Only classes annotated with '@IntegrationTEST' can define one or more Conditions.

Implementation proposal

@IntegrationTest(conditions = {DatabaseCondition.class, SubsystemCondition.class})
public BookingServiceIntegrationTest {
   ...
}
@IntegrationTest(SubsystemCondition.class)
public PaymentServiceIntegrationTest {
   ...
}

public class DatabaseCondition implements Condition {
 ...
}

public class SubsystemCondition implements Condition {
 ...
}

public interface Condition {
    Status checkCondition();
}

If the DatabaseCondition fails then

• BookingServiceIntegrationTest will not be executed
• PaymentServiceIntegrationTest will be executed
• ConditionTest will fail with the explanation and list of tests that were excluded.

If the SubsystemCondition fails then

• BookingServiceIntegrationTest will not be executed
• PaymentServiceIntegrationTest will not be executed
• ConditionTest will fail with the explanation and list of tests that were excluded.

At the moment the project is bound to junit4. Junit 5 should also be supported.

There should only be one notation for test sweet-junit runner executes.
New annotation could be
@suitetest (because it alraeady exists)
@sweettest (because it reflects the name of the project)
@IntegrationTEST (I would remove it because, Tests do not need to be integrationTests)

@jlupi => what do you think?

At the moment sweet junit runner loads annotated with '@IntegrationTEST' or '@suitetest'.

It should be also possible to load or exclude classes based on a naming pattern, for example:

• *IntegrationTest -> all classes ending with IntegrationTest
• *Test -> all classes ending with Test
• org.package.*Test -> all classes ending with with Test from package org.package
• org.package.**Test -> all classes ending with Test located in package or subpackages of org.package

There should be a mechanism that checks if a loaded class is a JUnit Test class.