[
https://issues.apache.org/jira/browse/BEAM-8951?focusedWorklogId=370121&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-370121
]
ASF GitHub Bot logged work on BEAM-8951:
----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Jan/20 22:53
Start Date: 10/Jan/20 22:53
Worklog Time Spent: 10m
Work Description: markflyhigh commented on pull request #10435:
[BEAM-8951] Stop using nose in load tests
URL: https://github.com/apache/beam/pull/10435#discussion_r365451894
##########
File path: sdks/python/apache_beam/testing/load_tests/load_test.py
##########
@@ -31,8 +31,8 @@ def __init__(self):
self.project_id = self.pipeline.get_option('project')
self.metrics_namespace = self.pipeline.get_option('metrics_table')
self._metrics_monitor = MetricsReader(
- publish_to_bq=self.pipeline.get_option('publish_to_big_query') ==
- 'true',
+ publish_to_bq=self.pipeline.get_option('publish_to_big_query')
+ .lower() == 'true',
project_name=self.project_id,
Review comment:
Another way to make those options organized is to register them in
`TestPipelineOption` (recommended if commonly used in performance testing),
which works the same way as parser does.
----------------------------------------------------------------
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: 370121)
> Stop using nose in load tests
> -----------------------------
>
> Key: BEAM-8951
> URL: https://issues.apache.org/jira/browse/BEAM-8951
> Project: Beam
> Issue Type: Sub-task
> Components: testing
> Reporter: Kamil Wasilewski
> Assignee: Kamil Wasilewski
> Priority: Major
> Fix For: Not applicable
>
> Time Spent: 7h
> Remaining Estimate: 0h
>
> The community is considering moving away from nose to pytest:
> https://issues.apache.org/jira/browse/BEAM-3713. We should change the way of
> running Python load tests: instead of being subclasses of
> `unittest.TestCase`, they could be plain Python scripts, just like wordcount
> examples. This will bring one additional benefit: _LOAD_TEST_ENABLED_ guard
> will be no longer needed and could be safely removed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
