[ https://issues.apache.org/jira/browse/BEAM-8148?focusedWorklogId=306721&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-306721 ]
ASF GitHub Bot logged work on BEAM-8148: ---------------------------------------- Author: ASF GitHub Bot Created on: 04/Sep/19 21:08 Start Date: 04/Sep/19 21:08 Worklog Time Spent: 10m Work Description: mxm commented on issue #9474: [BEAM-8148] Allow arguments to be passed to python tests from tox cli URL: https://github.com/apache/beam/pull/9474#issuecomment-528087865 Awesome, thanks! ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 306721) Time Spent: 1h (was: 50m) > [python] allow tests to be specified when using tox > --------------------------------------------------- > > Key: BEAM-8148 > URL: https://issues.apache.org/jira/browse/BEAM-8148 > Project: Beam > Issue Type: Improvement > Components: sdk-py-core > Reporter: Chad Dombrova > Assignee: Chad Dombrova > Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > I don't know how to specify individual tests using gradle, and as a python > developer, it's way too opaque for me to figure out on my own. > The developer wiki suggest calling the tests directly: > {noformat} > python setup.py nosetests --tests <module>:<test class>.<test method> > {noformat} > But this defeats the purpose of using tox, which is there to help users > manage the myriad virtual envs required to run the different tests. > Luckily there is an easier way! You just add {posargs} to the tox commands. > PR is coming shortly. -- This message was sent by Atlassian Jira (v8.3.2#803003)