Update CoT test data with modern task definitions
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- testing-qa
Research direction
Start by reading test_cot_verify.py and the existing tests/data/cotv2 and tests/data/cotv4 directories to understand their constants, helpers, and task definitions. Add tests/data/cotv7 with modern definitions such as the decision task and actions.yml, migrate tests where possible, then remove obsolete data only when coverage remains intact.
Written by the indexing model from the issue text.
Description
The test data being used was generated a long time ago (circa cotv2 and cotv4). To help ensure the tests are relevant we should update the definitions with those from recent tasks.
I'm no expert in this regard, but I think the approach I would take is:
- Create
tests/data/cotv7(and add associated constants / helper methods totest_cot_verify.py) - Save modern task definitions there (e.g, decision task, actions.yml, etc)
- Attempt to convert as many tests over to this new data as possible
- Remove
cotv2andcotv4dirs. It might be fine for some tests to continue using the older data, but having a single data dir would simplify things... - Verify no loss in code coverage.
- Dominant language
- Python
- Stars
- 5
- Forks
- 41
- Avg merge
- 22h 52m
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mozilla-releng/scriptworker
-
Dependency DashboardOpen
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
mozilla-releng/scriptworker#748 ·
Maintainers usually reply within 1 day
-
verify_cot fails to validate pull requests on repos that are forksMay be free again @ahal claimed this 894 days ago, and no pull request is open. Open
mozilla-releng/scriptworker#645 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
mozilla-releng/scriptworker#584 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mozilla-releng/scriptworker#580 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mozilla-releng/scriptworker#570 ·
Maintainers usually reply within 1 day
All issues in mozilla-releng/scriptworker
Similar issues
-
Link Checker ReportOpenautomated issue report
Difficulty 1/5 Under an hour Newbie friendliness 85/100
RapidAI/RapidOCRDocs#119 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
btclib-org/btclib-node#1833 ·
Maintainers usually reply within 1 day
-
IRIS reader: no-data velocity bins (DB_VEL, DB_VELC) returned as 0.0 m/s instead of NaNPossibly taken @syedhamidali claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
elodin-sys/elodin#890 ·
Maintainers usually reply within 1 day