Feature request: rules for tests

[brunoborges]

Let's consider the example of a Java application that connects to an RDBMS system. THe existing rules will identify which RDBMS system is used, and may provide recommendations on what to do about that. But these recommendations are only about the actual business application code.

In certain apps, code in Unit Tests and Integration Tests may also connect to a database, and in these cases, one recommendation may be to adopt emulators and Test Containers to spin up a temporary database.

Today, there is no clear path on how to draft rules that provide recommendations specifically for code that performs tests.

Another point is rules for testing frameworks, e.g. moving from an old version of JUnit to a new version or migrating to TestNG and vice-versa.

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.