I could also see value in adding a little help output to give examples on 
regex-based test selection. Also - when we run "ant testsome" in the base of 
the project it just starts to run things instead of kicking out help text to 
give guidance on how to run a subset of tests.

Generally speaking, I think we could probably really improve the 
discoverability of how to run a subset of tests and/or get involved with 
developing in this space. 

On Wed, Jul 23, 2025, at 6:33 PM, Joel Shepherd wrote:
> On 7/23/2025 7:21 AM, Josh McKenzie wrote:
>> 
>> There anything in that README that we could/should promote to 
>> https://cassandra.apache.org/_/development/testing.html?
> There'd be some value in selectively referencing some of the tools in there, 
> or at least mentioning their existence.
> 
> Let me get a little more familiar with what's in that directory and pull up 
> the juiciest-looking examples into the testing doc.
> 
> Thanks -- Joel.
> 
> 
> 
>> 
>> On Tue, Jul 22, 2025, at 8:04 PM, Joel Shepherd wrote:
>>> Ah, thanks: all kinds of good stuff in there.
>>> 
>>> -- Joel.
>>> 
>>> On 7/22/2025 1:45 PM, Mick Semb Wever wrote:
>>>> 
>>>> try
>>>> 
>>>> .build/run-tests.sh -a test -t org.apache.cassandra.hints
>>>> 
>>>> https://github.com/apache/cassandra/blob/cassandra-5.0/.build/README.md
>>>> 
>>>> 
>>>> 
>>>> On Tue, 22 Jul 2025 at 21:06, Joel Shepherd <sheph...@amazon.com> wrote:
>>>>> Hi - I know it's possible to run just the unit tests in a single test
>>>>> class, or a specific test in a specific class. I'd like to be able to
>>>>> run all tests in a single Java package (e.g., all unit tests for
>>>>> org.apache.cassandra.auth). I see that I can list the classes
>>>>> individually in a text file and use 'ant testclasslist': I'd like
>>>>> something more direct.
>>>>> 
>>>>> Assuming there's not another way to do it and that others would find it
>>>>> useful, any preference as to the invocation style?
>>>>> 
>>>>>    ant testsome -Dtest.name=<packageName>.*   // Similar to running all
>>>>> tests in a class, just using a wildcard for the
>>>>> // class name
>>>>> 
>>>>>    ant testsome -Dtest.package=<packageName>  // New, optional parameter
>>>>> for 'testsome': can ensure it's a
>>>>> // mutually exclusive option from -Dtest.name [-Dtest.methods].
>>>>> 
>>>>> Open to pointers and better ideas! Thanks -- Joel.
>>>>> 
>>>>> 
>>>>> 
>> 

Reply via email to