[jira] [Commented] (CASSANDRA-19050) Enhanced usage of test method names in CQLTester for better test debugging

["Berenguer Blasi (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-19050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790431#comment-17790431 ] 

Berenguer Blasi commented on CASSANDRA-19050:
---------------------------------------------

Added trunk PR and failures seem TCM merge related. Do you agree [~mck]? if you do I'll merge

> Enhanced usage of test method names in CQLTester for better test debugging
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-19050
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19050
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Test/unit
>            Reporter: Berenguer Blasi
>            Assignee: Berenguer Blasi
>            Priority: Normal
>             Fix For: 5.0-rc, 5.x
>
>
> All views, tables, ks,... created in CQLTester are of the form {{table_00}}:
> - While debugging tests and flakies this makes it really hard to match logs to test methods.
> - Some async operations can spill log lines from a previous test method into the next's log lines which is incredibly confusing
> - It's hard on the eyes and easy to mix up
> - When comparing logs from 2 different branches, envs,... it's really hard to match logs
> The proposed solution is for {{CQLTester}} to decorate these with the test name.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org