[
https://issues.apache.org/jira/browse/CASSANDRA-19050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805577#comment-17805577
]
Benjamin Lerer commented on CASSANDRA-19050:
--------------------------------------------
The patch had a minor issue. The new version is
[here|https://github.com/blerer/cassandra/commit/a650fbce6a5092bc9004ca47fe25a424623b1d6e].
The unit test run is
[green|https://app.circleci.com/pipelines/github/blerer/cassandra/370/workflows/8fbcb82b-a5c4-4ac8-baf7-e54909209eaa].
> 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: [email protected]
For additional commands, e-mail: [email protected]
