[
https://issues.apache.org/jira/browse/SAMZA-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940666#comment-13940666
]
Chris Riccomini commented on SAMZA-195:
---------------------------------------
I agree on the subclass comment from Martin.
If we go the ScalaTest route, it would also allow us to remove the goofy
build.gradle stuff we do we do to pull in TestUtil for samza-test:
{code}
// Depend on samza-core's test classes so TestUtils can be used.
testCompile project(":samza-core_$scalaVersion").sourceSets.test.output
{code}
That said, moving to ScalaTest is a bit heavy handed, and I'm inclined to stick
with something tried-and-true like JUnit or TestNG.
> Elucidate TestUtil:expect
> -------------------------
>
> Key: SAMZA-195
> URL: https://issues.apache.org/jira/browse/SAMZA-195
> Project: Samza
> Issue Type: Improvement
> Reporter: Jakob Homan
>
> The TestUtil::expect method seems a bit odd, as discussed in SAMZA-161.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
