consistent naming for tests

[Kevin Rushforth]

This might be a combination of Eclipse and eCryptfs. I agree that 143 
chars is very short for a max length.

-- Kevin


On 7/9/2024 8:22 AM, John Hendrikx wrote:
>
>
> On 09/07/2024 16:52, Andy Goryachev wrote:
>>
>> Two test files consistently generate an error in Eclipse
>>
>> - ObservableValueFluentBindingsTest
>> - LazyObjectBindingTest
>>
>> I admit I have a weird setup (EncFS on Linux Mint running on MacBook 
>> Pro), and it only manifests itself in Eclipse and not in the gradle 
>> build - perhaps Eclipse actually verifies the removal of files?
>>
>> Anyway, a suggestion - if you use @Nested, please keep the class 
>> names /short/.
>>
> This is not an Eclipse bug as I never encounter such issues. 143 
> characters is rather short these days, but I suppose we could limit 
> the nesting a bit.  Still, I'd look into a way to alleviate this 
> problem in your setup, sooner or later this is going to be a problem.
>
> --John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/openjfx-dev/attachments/20240709/ac038034/attachment.htm>