How do you properly test a GetX controller in isolation, given its own reliance on GetX's own particular static dependency injection system rather than a considerably more explicit constructor based approach?

Testing a GetX controller typically involves properly using Get.testMode together with correctly resetting GetX's own internal dependency container between separate individual tests using Get.reset, ensuring one test's own registered dependencies genuinely do not accidentally leak over and affect a completely separate subsequent test, and while this can genuinely be somewhat more cumbersome compared to the considerably more straightforward explicit constructor injection already used by BLoC or Riverpod, GetX controllers can still genuinely be thoroughly and properly unit tested by directly instantiating them and then properly calling their own specific public methods while carefully asserting the genuinely resulting expected state.

setUp(() => Get.testMode = true);
tearDown(() => Get.reset());

test('increment increases count', () {
  final controller = CounterController();
  controller.increment();
  expect(controller.count.value, 1);
});