id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
34655	Tests for RadioSelect and Select have diverged considerably, potentially leaving RadioSelect undertested	Natalia Bidart	Jacob1507	"Even though `Select` and `RadioSelect` both share most of the functionality by inheriting from `ChoiceWidget`, there are no explicit tests for `ChoiceWidget`, and tests for `Select` and `RadioSelect` have diverged considerably over time.

While some tests will be specific to each children (for their custom code), after inspection when reviewing [https://github.com/django/django/pull/16929/ PR] for #34034, there seems to be some tests that were added to `Select` but not added to their counterpart `RadioSelect`, for example `test_deepcopy`.

My hope with this ticket is to either:

* evaluate the creation of specific tests for `ChoiceWidget` and have tests for  `Select` and `RadioSelect` reusing those, and then having custom tests for their custom functionality

* extend the tests for `RadioSelect` using those for `Select` as a guide and have some sort of comment suggesting to grow both test suites when making changes to their parent class."	Cleanup/optimization	closed	Forms	4.2	Normal	fixed			Ready for checkin	1	0	0	0	1	0