Feature: usage of the NoopTransactionContext in tests

[paullatzelsperger]

Feature Request

Many of the SQL-related tests have to use a transaction context. Currently that means adding a gradle dependency onto the LocalTransactionContext and instantiating it in the @BeforeEach.

There already is a NoopTransactionManager that does nothing and is always available.

Which Areas Would Be Affected?

Tests, especially the SQL-tests

Why Is the Feature Desired?

Reduce inter-module dependencies

Solution Proposal

Use the NoopTransactionManager in all tests.

Type of Issue

cleanup

Checklist

• assigned appropriate label?
• Do NOT select a milestone or an assignee!