Fixes part of #4302 - Introducing a JUnit annotation & rule for overriding Platform Parameters and Feature Flags

[Rd4dev]

Explanation

Fixes part of #4302

This PR includes

A draft implementation for overriding platform parameters and feature flags in the tests using the PlatformParameterModule at class and functional level.

Validation Details

• Feature flags on Function level & Class level

  • Enable Feature flag performed on SpotlightFragmentTest.kt
  • Disable Feature flag and Reset Feature flag with the above class level validation, feature disabled only for testSpotlightFragment_disableSpotlights_requestSpotlight_shouldNotShowSpotlight

• Repeatable Annotation

  • Performed on ProfileAndDeviceIdFragmentTest.kt with testFragment_multipleProfiles_clickShareIdsAndLogs_sendsIntentWithIdsAndLogsText that required enabling both
    • android_enable_logging_learner_study_ids
    • android_enable_learner_study_analytics

• Overriding PlatformParameter value

  • Performed on StateFragmentTest.kt with testStateFragment_mathInteractions_numericExp_validAns_submissionDisplaysLatex while the default "cache_latex_rendering" was switched off, with @OverrideBoolParameter("cache_latex_rendering", true) annotation.

Todo on approval / feedback:

• Alter the implementation based on feedback received from the review process.
• Once approved, the final version will replace the old module with the new functionality across all applicable tests.
• Remove debugging statements.
• KDocs will be added.

Note:

• Any altered parameter values in this draft are solely for testing and validating the functionality.
• These changes will be reverted to their original states once the PR is out of draft.
• Current tests may fail due to the temporary removal of TestPlatformParameterModule in certain test classes.
• This setup is intended to validate the overridden values in the new implementation.

Essential Checklist

• The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• Any changes to scripts/assets files have their rationale included in the PR explanation.
• The PR follows the style guide.
• The PR does not contain any unnecessary code changes from Android Studio (reference).
• The PR is made from a branch that's not called "develop" and is up-to-date with "develop".
• The PR is assigned to the appropriate reviewers (reference).

[Rd4dev]

@BenHenning @adhiamboperes Would it be possible to provide a draft review or approval on the implementation to ensure things are on the right track before I proceed with the rest? I would like to confirm if the mentioned

"Updating all tests to use the production module instead of the test or a custom module, and adding OppiaTestRule/test annotations where needed to ensure overrides are still happening."

is done right. If not then will rework based on the feedback.