[
https://issues.apache.org/jira/browse/CASSANDRA-16025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321202#comment-17321202
]
Brian Houser commented on CASSANDRA-16025:
------------------------------------------
Hmm ok, so in conclusion, we look through the existing testing, and define test
areas and add them as sub tickets to this one. I think that makes sense.
Probably coming up with a simple first test should be one of the tickets (its a
lot easier to add tests once there is a single example).
One further question... is this a duplicate of
https://issues.apache.org/jira/browse/CASSANDRA-16023 ?
> Cqlsh unit testing and coverage improvements
> --------------------------------------------
>
> Key: CASSANDRA-16025
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16025
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
> Reporter: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0.x
>
>
> Nowadays the majority of cqlsh testing happens outside the main java unit
> testing effort. A lot is done as separate cqlsh tests, dtests, python, etc.
> The purpose of this ticket is to improve unit test coverage as much as
> possible now that CASSANDRA-15583 allows us to perform java unit tests for
> the tool.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
