[
https://issues.apache.org/jira/browse/BEAM-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles resolved BEAM-2335.
-----------------------------------
Resolution: Won't Do
Fix Version/s: Not applicable
No more maven - no more documentation of this. With gradle it is quite a bit
more straightforward.
> Document various maven commands for running tests
> -------------------------------------------------
>
> Key: BEAM-2335
> URL: https://issues.apache.org/jira/browse/BEAM-2335
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Ted Yu
> Priority: Major
> Labels: document
> Fix For: Not applicable
>
>
> In this discussion thread, various maven commands for running / not running
> selected tests were mentioned:
> http://search-hadoop.com/m/Beam/gfKHFd9bPDh5WJr1?subj=Re+How+can+I+disable+running+Python+SDK+tests+when+testing+my+Java+change+
> We should document these commands under
> https://beam.apache.org/contribute/testing/
> Borisa raised the following questions:
> how do I execute only one test marked as @NeedsRunner?
> How do I execute one specific test in java io?
> How to execute one pecific test in any of the runners?
> How to use beamTestpipelineoptions with few json examples?
> Will mvn clean verify execute ALL tests against all runners?
> For the #1 above, we can create profile which is used run tests in
> NeedsRunner category.
> See the following:
> http://stackoverflow.com/questions/3100924/how-to-run-junit-tests-by-category-in-maven
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
