Greenstand/treetracker-query-api

Build up our test CI to protect the code

Open

#274 opened on Jan 18, 2023

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)TypeScript (65 forks)auto 404
good first issue

Repository metrics

Stars
 (17 stars)
PR merge metrics
 (PR metrics pending)

Description

  1. we don't run test in CI to check the code
  2. The test is incomplete, and inappropriate, we just run e2e test to connect to the real database, downside of this is that we have to rely on outside truth, database here. So we need change to integration test + unit test to cover at lease the main part of the API

Maybe this issue is too big, could consider a project and split to smaller pieces of tasks.

Some hints:

  • Please read our readme for more information/guide/tutorial.
  • Here is an engineering book in Greenstand.
  • To know more about our organization, visit our website.
  • If you want to join the slack community (some resources need the community member's permission), please leave your email address.

Contributor guide

Research direction
Understand the current test structure, identify gaps, and design a CI pipeline that includes unit and integration tests. Review existing e2e tests and propose how to convert them to integration tests.
Tech stack
typescript
Domain
backendapitestingci cd
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.
3-5 days
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
GitCI/CD concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75