CI/CD: Outdated Frontend Test Suites

[rohan-pandeyy]

Description

The current frontend test setup is outdated requires updating with the existing frontend architecture. As a result, frontend tests coverage does not meaningfully contribute to CI confidence around core UI stability in their current state.

Proposed Direction

The frontend has evolved, but tests haven’t kept pace

• Refresh the frontend test suites with new practical scopes.
• Add high value tests focusing on the most recent feature additions which lack test suites like core layout or navigation component tests + critical user facing interaction tests.

Upcoming features and fixes increase the risk of silent UI regressions. Updating the test baseline now will reduce future maintenance cost.

Undertakings

• I agree to follow the Code of Conduct.
• I want to work on this issue.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[github-actions]

👋 Thanks for opening this issue! The maintainers will review it shortly. Till then, do not open any PR. This is a strict rule we like to follow around here :)

[rohan-pandeyy]

@rahulharpal1603 kindly assign me this issue. Thank you

[rohan-pandeyy]

I closed the issue by mistake @rahulharpal1603 😅💀 Please reopen..

[aurthitaacharya-afk]

@rahulharpal1603 Sir 👋
I see this issue is assigned.
If it’s currently inactive, I’d be happy to help work on it.
Please let me know 🙏

[rohan-pandeyy]

Hi @aurthitaacharya-afk, thanks for the interest! I’m currently working on this issue, but I’ll post an update here if I need help. Thank you :)

[rohan-pandeyy]

@rahulharpal1603 I will be adding Sanity Tests for all the components as for stage one on top of the currently existing Smoke tests, majorly to establish a reliable baseline. I think, we should then expand from there incrementally, add more detailed functional tests.

I wanted your feedback on this, do you agree with "going one step at a time with Sanity tests" or would you like me to add detailed functions including edge cases as well (from the start only) like I did for the backend tests in this PR

TL;DR Would you want me to put tests step wise like sanity test for Navigation: that all routing works, Home page: All states are working, Settings page: All core controls working test... OR... detailed functionality testing from the start only