This would apply to the description and body tests as well, but I'm always unsure of what tests like this are expecting just because technically they're passing, but they'd also pass even if label="another test label" were passed in. So less that a label doesn't render and more that a label with this specific test doesn't render.

At the same time I'm not sure how pretty an alternative would be. Using something like getByRole(checkbox).parentElement.querySelector(.${styles.checkLabel}) may work but is lengthy.

Probably splitting hairs too much so I don't think I'd really block over it, but curious what you think.

Yeah I don't have a hardline stance on this and happy to remove if you think they're unnecessary, but my reasoning for doing these kinds of tests is that it ensure that assertion in the following test (where we expect the label to exist) is actually valid and not giving a false positive.

Since it'd accept a regex, what about expect(screen.queryByLabelText(/\w+/)).not.toBeInTheDocument();? We don't really care what the label text actually is, just whether it's rendered, so this would result in a failure if any sort of label text were to be found (rather than currently a failure only occurs if label text that is "test label" is found). Probably wouldn't work for the body and description tests, though.

Yeah I'm not against that idea at all.