cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9852) Complete test coverage for StorageProxy
Date Tue, 21 Jul 2015 06:23:05 GMT


Stefania commented on CASSANDRA-9852:

h3. Old analysis

Code coverage results after running some relevant dtests for CASSANDRA-9102: *,,, and*.

Quick observations after analyzing StorageProxy and auxiliary files:

||File||Percentage||Missing coverage||
|ReadCallback|55%|Exception handling or generation (ReadTimeout, ReadFailure, DigestMismatch)|
|StorageProxy|56%|Exception handling (timeouts, failures), hinting due to exception handling
and max limit of hints reached, logged batches and triggers, some estimation of ranges due
to indexes and range slices, describe cluster (a nodetool command), truncation of data, paxos
contentions, jmx methods (but I think we have some nodetool tests I did not run and they are
|RowDataResolver|79%|replyCount == 1|

See [this comment|]
for more context.

> Complete test coverage for StorageProxy
> ---------------------------------------
>                 Key: CASSANDRA-9852
>                 URL:
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Stefania
>            Assignee: Stefania
> Run relevant unit and dtests under code coverage to find out which parts of StorageProxy
and auxiliary classes are still not tested. Below is an old analysis  which should be repeated
now that CASSANDRA-8099 is integrated into trunk.
> Then add more unit or distributed tests to complete code coverage. The framework provided
by CASSANDRA-9165 will most likely be required to inject failures and time outs.

This message was sent by Atlassian JIRA

View raw message