You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/07/11 22:47:07 UTC
[jira] [Updated] (SAMZA-274) Refactor SamzaContainer and improve
test coverage
[ https://issues.apache.org/jira/browse/SAMZA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Riccomini updated SAMZA-274:
----------------------------------
Summary: Refactor SamzaContainer and improve test coverage (was: Refactor SamzaController and improve test coverage)
> Refactor SamzaContainer and improve test coverage
> -------------------------------------------------
>
> Key: SAMZA-274
> URL: https://issues.apache.org/jira/browse/SAMZA-274
> Project: Samza
> Issue Type: Improvement
> Affects Versions: 0.7.0
> Reporter: Martin Kleppmann
> Fix For: 0.8.0
>
>
> SamzaController would benefit from refactoring, to split the very long methods into shorter ones, and separating out concerns better.
> In the process, we should also make it more testable, and write more tests. It currently only has two tests. Amongst other things, we should make sure that we're testing for the issue that was fixed in SAMZA-142 (test coverage that we lost in SAMZA-224).
> If appropriate, the unit tests can start covering aspects of integration tests like TestStatefulTask, but in a more focussed manner.
--
This message was sent by Atlassian JIRA
(v6.2#6252)