refactor(radio-button, radio-button-group): convert enzyme tests to RTL

[nuria1110]

Proposed behaviour

Convert tests to RTL

Current behaviour

Tests are in enzyme

Checklist

• Commits follow our style guide
• Related issues linked in commit messages if required
• Screenshots are included in the PR if useful
• All themes are supported if required
• Unit tests added or updated if required
• Playwright automation tests added or updated if required
• Storybook added or updated if required
• Translations added or updated (including creating or amending translation keys table in storybook) if required
• Typescript d.ts file added or updated if required
• Related docs have been updated if required

QA

• Tested in provided StackBlitz sandbox/Storybook
• Add new Playwright test coverage if required
• Carbon implementation matches Design System/designs
• UI Tests GitHub check reviewed if required

Additional context

Testing instructions

[Parsium]

praise: great job checking the ARIA roles! Your method of targeting elements mirrors how an assistive technology user would inspect the page 👍🏼

[Parsium]

suggestion: restoring the logger's original behavior should prevent the console from being accidentally masked in other tests:

Suggested change

	});
	loggerSpy.mockRestore();
	});

[robinzigmond]

Really good job - just some very minor comments to add to those of @Parsium

[robinzigmond]

suggestion (non-blocking): I'd prefer in these focus/blur tests to explicitly fetch a particular element to call .focus() (and then tab/click as necessary for the rest of the test) - this ensures we're focusing/blurring the correct thing and avoids any future test flakiness if we later introduce other tab stops etc

[nuria1110]

The focus method seems to call the actual HTML focus() method but this isn't getting flagged by the linter (issue raised here). I do agree that using tab() might be a bit flakey, though I think using click() should be fine.

[robinzigmond]

hmm, I wasn't aware there was any recommendation against using .focus() on an HTML element, I thought this was what you needed to do to ensure a particular element was focused at the start of a test (I agree that once into the actual sequence of steps you're testing you should do "user things" like click/tab). I've done it myself in plenty of RTL tests recently and never been suggested not to 😂

[carbonci]

🎉 This PR is included in version 141.0.7 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀