mattermost/mattermost

Add unit test cases for integrations.ts

Open

#27,663 opened on Jul 15, 2024

View on GitHub
 (2 comments) (0 reactions) (1 assignee)TypeScript (7,823 forks)batch import
HacktoberfestHelp Wanted

Repository metrics

Stars
 (32,880 stars)
PR merge metrics
 (Avg merge 6d 5h) (318 merged PRs in 30d)

Description

File: https://github.com/mattermost/mattermost-mobile/blob/main/app/actions/remote/integrations.ts Acceptance criteria:

  • Should pass in CI
  • Should have Coverage of 95%

When submitting a PR:

  1. PR title: test: <Jira ticket> unit test for filename``, ex. test: MM-59413 unit test for app/actions/remote/apps.ts
  2. Indicate test coverage improvement, ex. From 2% to 96%
  3. Attached a screenshot of test coverage result.
  4. If something can’t be tested, describe and explain for reference.

Need help or would like to get in touch?

Feel free to post a message, questions and or anything at https://community.mattermost.com/core/channels/native-mobile-apps and get in touch with us – Mattermost developers and community.

If you're interested please comment here and come join our "Contributors" community channel on our daily build server, where you can discuss questions with community members and the Mattermost core team. For technical advice or questions, please join our "Developers" community channel.

New contributors please see our Developer's Guide.

JIRA: https://mattermost.atlassian.net/browse/MM-59420

Contributor guide

Research direction
Write unit tests for the integrations.ts file using Jest to achieve 95% coverage. Follow the existing test patterns in the codebase, and ensure tests pass in CI.
Tech stack
typescriptjest
Domain
mobile
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScriptJest
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75