You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the JupiterTestEngine needlessly attempts to resolve Unique IDs that clearly belong to other test engines. This is because JavaElementsResolver.resolveUniqueId(UniqueId) completely ignores the Engine ID and then blindly attempts to resolve the supplied Unique ID. Consequently, the JupiterTestEngine always logs a warning about not being able to resolve a Unique ID that it was never meant to resolve.
Prior to this commit, the JupiterTestEngine needlessly attempted to
resolve Unique IDs that clearly belong to other test engines. This is
because JavaElementsResolver.resolveUniqueId(UniqueId) ignored the
Engine ID and then blindly attempted to resolve the supplied Unique ID.
Consequently, the JupiterTestEngine always logged a warning about not
being able to resolve a Unique ID that it was never meant to resolve.
This commit addresses this issue by ignoring Unique IDs selected via one
of the DiscoverySelectors.selectUniqueId() methods if the Unique ID
belongs to a different test engine.
Fixes: junit-team#1026
Overview
Currently, the
JupiterTestEngine
needlessly attempts to resolve Unique IDs that clearly belong to other test engines. This is becauseJavaElementsResolver.resolveUniqueId(UniqueId)
completely ignores the Engine ID and then blindly attempts to resolve the supplied Unique ID. Consequently, theJupiterTestEngine
always logs a warning about not being able to resolve a Unique ID that it was never meant to resolve.Related Issues
Deliverables
JupiterTestEngine
does not attempt to resolve Unique IDs that belong to other test engines.The text was updated successfully, but these errors were encountered: