[
https://issues.apache.org/jira/browse/SOLR-8432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080466#comment-15080466
]
Joel Bernstein commented on SOLR-8432:
--------------------------------------
I agree that work needs to be done on the tests. We have a few open Streaming
issues (UpdateStream, JDBCStream, Intersect/Complement) and a few bugs to
clear. I'd like to get these issues committed, adding the new tests to
StreamingTest and StreamExpressionTests.
Then I think it makes sense to focus on inventorying, beefing up and
re-organizing the Streaming tests before the 6.0 release.
We can use this ticket to discuss how the tests could be re-organized and also
agree on a standard set of tests that should be present for each Stream
Implementation.
> Split StreamExpressionTest into separate tests
> ----------------------------------------------
>
> Key: SOLR-8432
> URL: https://issues.apache.org/jira/browse/SOLR-8432
> Project: Solr
> Issue Type: Test
> Affects Versions: Trunk
> Reporter: Jason Gerlowski
> Priority: Trivial
> Fix For: Trunk
>
> Attachments: SOLR-8432.patch
>
>
> Currently, {{StreamExpressionTest}} consists of a single JUnit test that
> calls 10 or 15 methods, each targeting a particular type of stream or
> scenario.
> Each of these scenario's would benefit being split into its own separate
> JUnit test. This would allow each scenario to pass/fail independently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
