Details
-
Improvement
-
Status: Resolved
-
P2
-
Resolution: Won't Fix
-
Not applicable
Description
At the moment, TestPipeline enforces some usage patterns, that may be too strict for non sdk/runner developers. It is therefore desired to separate it into 2 versions, one that is strict, and aimed to be used by sdk/runner developers, and one that is more lenient, and aimed to be used by casual (i.e., non sdk/runner) users.
For instance, the lenient version of the TestPipeline should NOT be required to be used as a JUnit rule, and should be easily inlined into test methods.
See also the discussion in GitHub PR #2089.
Attachments
Issue Links
- is related to
-
BEAM-1543 TestPipeline: @Rule error message confusing/javadoc doesn't explain proper usage
- Resolved