This repository was archived by the owner on Jan 21, 2020. It is now read-only.
Create AbstractExpressiveContainerConfigTest with required test traits composed #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch builds on a comment on #2.
First, it renames
ContainerTest
toAbstractContainerTest
, in order to follow our naming guidelines for abstract classes.Second, it introduces
ExpressiveTestTrait
, which composes the various traits that are required by implementations in order to be compatible with Expressive configuration.Third, it modifies
AllTestTrait
to useExpressiveTestTrait
as well asSharedTestTrait
.Fourth, it introduces
AbstractExpressiveContainerConfigTest
, which extendsAbstractContainerTest
and composesExpressiveTestTrait
.Fifth, it removes the
BaseContainerTest
as redundant to the newAbstractExpressiveContainerConfigTest
, and updates all test classes to extend it.