You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Sanil Jain (JIRA)" <ji...@apache.org> on 2019/05/28 20:56:00 UTC
[jira] [Assigned] (SAMZA-2224) Move Samza integ tests to its own
module different from Samza-test
[ https://issues.apache.org/jira/browse/SAMZA-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanil Jain reassigned SAMZA-2224:
---------------------------------
Assignee: (was: Sanil Jain)
> Move Samza integ tests to its own module different from Samza-test
> ------------------------------------------------------------------
>
> Key: SAMZA-2224
> URL: https://issues.apache.org/jira/browse/SAMZA-2224
> Project: Samza
> Issue Type: Improvement
> Reporter: Sanil Jain
> Priority: Minor
>
> - Module Samza-test module has the Test Framework which jobs use for Testing
> - Samza test also has python integration tests used in release certification, these tests need a file
> logging because they assert on loglines, hence needs log4j1 or log4j2 to be used there
> - This forces people to use either of log4j1 or log4j2 in there job (this is bad for a framework to decide)
> - Ideal Change is:
> ** Test Framework lives in :samza-test which users depend upon and uses console logging
> ** Integ test needing file logging lives in another module called samza-integ-tests which users
> don't depend upon
> [~pmaheshwari] [~boryas]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)