Component testing

[Karma-Tsering]

Description

We are implementing component testing for the Monlam application to ensure each component functions correctly in isolation. This involves mocking the hooks and dependencies used by the components to accurately test their behavior and output under various scenarios.

completion criteria

Render each component in isolation and mock the required dependencies. Also the test should cover all the scenarios and their edge cases

Subtasks

Since there are many components, I will start with the simpler ones and progress to the more complex ones.

• [x] EditDisplay
• [x] CopyClipboard
• [x] FeedBucket
• [x] HeaderComponent
• [x] ThemeSwitcher
• [x] TranslationSwitcher
• [x] locationDetect
• [x] ReactionButtons
• [x] ActionButtons
• [ ] AppInstaller
• [ ] AudioPlayerWithWave
• [x] AudioToggle
• [x] Buttons
• [x] Card
• [x] Countdown
• [x] Devider
• [x] EachInference
• [x] ErrorMessage
• [x] ErrorPage
• [x] FeedBucket
• [x] FileUpload
• [x] InferenceList
• [x] ListInput
• [x] Progress
• [x] ShareLink
• [x] Speak
• [x] TermsandConditions
• [x] TextComponent
• [x] ToolWraper

[ta4tsering]

take advice from Tamdin or Kunsang for how to make subtasks

[kaldan007]

list all the components and discuss with @tenkus47 .

[Karma-Tsering]

As discussed with kunsang, I don't need to write test for AudioPlayerWithWave component.

[Karma-Tsering]

The appinstaller component required PWA behavior to test and isolating this component is not testable for now. I will look into it along with my daily tasks and try to write a test for it.

[kaldan007]

Update the test with new code.

[tenkus47]

suggestions:

1. ActionButtons -> null output is tackled as empty string
2. Card -> i don't thing line 50 where we check the card to be focussed is necessary because its already done on previous test
3. Countdown -> is not necessary for testing, we can remove it simply
4. Devider -> i dont think this needs a test too . may be we can discuss it