Skip to content

Add Unit Test Coverage for UI Components [Open for Multiple Contributors] #85

@kannananil

Description

@kannananil

This project began with experimenting and exploring suitable technologies and approaches for the application, so we didn’t initially follow a structured testing strategy or aim for thorough test coverage. Now that we have a stable foundation and a better understanding of the tech stack, it’s a good time to start adding the missing unit tests and adopt a test-driven development (TDD) approach moving forward, with a base threshold for test coverage.

At present, only a few of the custom UI components have adequate unit tests(Could use those as reference). Below is a list of components that are either missing tests entirely or have incomplete coverage.

Note: Multiple contributors can work on this issue. Please sign up for one component at a time and notify others by leaving a comment on which component you're working on.

List of components with lack of test coverage

  • AppBody
  • Editor
  • Header
  • PaneSplitter
  • RequestHeadersPanel
  • ResponsePanel
  • Sidebar
  • Snackbar
  • Spinner
  • UrlPanel
  • pages/Home
  • Dropdown
  • AuthPanel
  • AuthForm

Metadata

Metadata

Labels

L1 - smallComplexity level 1P0 - criticalCritical (must-fix immediately, blocking)test

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions