rubickCenter/rubick

保持测试用例的更新

Open

#172 opened on Mar 14, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (5,026 stars) (568 forks)batch import
help wanted

Description

建议使用 Cucumber 框架，在 github Action 里跑测试，测各插件是否还能正常使用。

其状类似 https://github.com/tiddly-gittly/TidGi-Desktop/blob/master/features/openClose.feature

以便解决类似 https://github.com/rubickCenter/rubick/issues/151 、 https://github.com/rubickCenter/rubick/issues/171 、 https://github.com/rubickCenter/rubick/issues/164 等问题

Contributor guide

Tech stack
javascriptnodejsgithub actions
Domain
testingci cd
Issue type
feature
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of ElectronFamiliarity with GitHub ActionsKnowledge of Cucumber testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Review the existing Cucumber test setup in TidGi Desktop (https://github.com/tiddly gittly/TidGi Desktop/blob/master/features/openClose.feature) for reference. The issue requests integrating Cucumber tests for rubick plugins within GitHub Actions. Start by examining the plugin structure and identify areas to test. Look at the linked issues for examples of plugin failures. Implementation should include writing .feature files and step definitions, then configuring a GitHub Actions workflow to run the tests on push/PR.