[TAMAYA-324] CDI-Test failures in extensions modules on certain environments

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.4-incubating
• Fix Version/s: 0.4-incubating
• Component/s: Extensions
• Assignee: Philipp Ottlinger
• Reporter: Philipp Ottlinger
• Created: 17/Jan/18 21:50
• Updated: 20/Jan/18 20:35
• Resolved: 20/Jan/18 20:35

Description

Certain ASF nodes with older Ubuntu LTS versions show test failures in CDI-Tests:

Tests in error:
  CDIAwareServiceContextTest.getServiceReturnsInstanceWithHighestPriority:57 » IllegalState
  CDIAwareServiceContextTest.getServiceReturnsNonCachedInstanceAtFirstCall:32 » IllegalState
  CDIAwareServiceContextTest.getServiceReturnsNullIfThereAreNoRegisteredSPIInstancesAvailable:50 » IllegalState
  CDIAwareServiceContextTest.getServiceReturnsOnSecondCallCachedInstance:40 » IllegalState

 

Williams commits:

First, the CDIAwareServiceContextTest now uses the same Arquillian
backing as various other successful tests.

Second, the ConfiguredVetoExtensionTest is now more idempotent with respect
to the ConfigurationProvider.  Previously, it would leave the shared
ConfigurationProvider pointing at the mocked ConfigurationContext, which
caused other tests (specifically ConfiguredBTest) which rely on a valid
ConfigurationContext to fail.