scribe-org/Scribe-iOS

Create functional testing files and ci process

Open

#8 opened on Nov 22, 2021

View on GitHub
 (17 comments) (0 reactions) (2 assignees)Swift (106 forks)auto 404
-priority-good first issuehelp wanted

Repository metrics

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

Description

Terms

Issue

Testing for Scribe and a continuous integration process would be very helpful to assure that pull requests can merged without issue. Discussions of best practices as well as how best to integrate the process into pull requests would be a first step in this issue. This would be followed by writing tests for a baseline, and then adding a ci.yml file to a workflows directory in Scribe-iOS/.github.

Contributor guide

Research direction
Learn about the existing codebase structure, especially any current testing setup and CI tools. Then outline a plan for writing functional tests and creating a ci.yml workflow that runs on pull requests. Start with a simple test for a key component and a basic CI workflow.
Tech stack
swiftgithub actions
Domain
mobileci cdtesting qa
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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
SwiftGitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65