We'll have node reusage in dtests soon once CI is green again and 16951
merges (in review). #justfyi
On 27/1/22 0:28, Joshua McKenzie wrote:
I meant concretely from actually working on the tests, not a
theoretical list.
I think that's fair. I'll see if I can't whip up an example of how
it'd mutate a single test and the API boundary between that and ccm.
Should be a quick but helpful exercise in seeing how it'd materially
change things if at all.
My experience was working with manipulating large quantities of data
from JIRA that came back in a huge variety of types; was a real pain
in python. Probably less surface area in any given test in the dtest
suite interacting with ccm.
On Wed, Jan 26, 2022 at 3:23 PM Brandon Williams <dri...@gmail.com> wrote:
On Wed, Jan 26, 2022 at 2:17 PM Joshua McKenzie
<jmcken...@apache.org> wrote:
>>
>> I'm unable to think of an instance where typing in python could
have helped me,
>
> Discoverability, IDE integration, more primitives to describe
your intent in your code to other maintainers, and shifting a
certain class of runtime errors to being "merge-time" errors all
come to mind.
I meant concretely from actually working on the tests, not a
theoretical list.
