[
https://issues.apache.org/jira/browse/CASSANDRA-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205512#comment-17205512
]
Josh McKenzie commented on CASSANDRA-15538:
-------------------------------------------
{quote}if you look at (true) unit testing for the classes that constitute the
read/write path, there isn't much
those path are mostly covered, but by "integration/functional" tests.
{quote}
So there's an opportunity for us to test this claim with code coverage,
assuming we can get the aggregate of unit + dtest + in-jvm dtest in a single
report. It looks like our coverage / jococo task in build.xml defaults to just
the equivalent of 'ant test' which will tell us where our gaps are from unit
testing but not much else.
[~aleksey] - you still planning on shepherding this? If so, have a point of
view on the thoughts given Sylvain's thoughts here?
Another interesting point:
{quote}biggest bucket (of bugs)... 'legacy layout conversions/handling'. And
that was clearly under-tested, but it's also gone in 4.0
{quote}
While I think there's some merit in that observation, it also makes the case
for us doing more robust testing and coverage analysis of how much our tests
actually exercise the legacy layout code in the 3.0 and 3.11 line. I'd advocate
for us opening another ticket for that rather than coupling it with the 4.0
line, but certainly seems like it'd be valuable to at least know where our gaps
and risk are.
> 4.0 quality testing: Local Read/Write Path: Other Areas
> -------------------------------------------------------
>
> Key: CASSANDRA-15538
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15538
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/java, Test/dtest/python
> Reporter: Josh McKenzie
> Priority: Normal
> Fix For: 4.0-beta
>
>
> Reference [doc from
> NGCC|https://docs.google.com/document/d/1uhUOp7wpE9ZXNDgxoCZHejHt5SO4Qw1dArZqqsJccyQ/edit#]
> for context.
> *Shepherd: Aleksey Yeschenko*
> Testing in this area refers to the local read/write path (StorageProxy,
> ColumnFamilyStore, Memtable, SSTable reading/writing, etc). We are still
> finding numerous bugs and issues with the 3.0 storage engine rewrite
> (CASSANDRA-8099). For 4.0 we want to ensure that we thoroughly cover the
> local read/write path with techniques such as property-based testing, fuzzing
> ([example|http://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html]),
> and a source audit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
