[
https://issues.apache.org/jira/browse/CASSANDRA-19050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805400#comment-17805400
]
Berenguer Blasi edited comment on CASSANDRA-19050 at 1/11/24 7:01 AM:
----------------------------------------------------------------------
^I think that will fail when seqNumber is 99 and jumps to 100, that's why you
need a loop instead of making room for N characters. I [also
tried|https://github.com/apache/cassandra/pull/2927#issuecomment-1822322918]
your approach and decided against it. Can you fire a test run please?
was (Author: bereng):
^I think that will fail when seqNumber is 99 and jumps to 100, that's why you
need a loop instead of making room for N characters. I [also
tried|https://github.com/apache/cassandra/pull/2927#issuecomment-1822322918]
your approach and decided against it. Can you fire a test run?
> 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]