site: nothing runs the operation-reference picture tests

Open Beginner friendly
#1,832 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, python
Domain
ci-cd

Research direction

Start in release.yml: find the site job that runs zola build and add the Python test invocation next to it, then document the command in site/README.md. Read site/tests/test_operation_reference.py first to see how it detects the Zola binary and skips the Zola arm when absent, and preserve that behaviour. Done when a cut run executes the test in the site job and fails if an operation picture view or reference section is missing.

Written by the indexing model from the issue text.

Description

area:build effort:low P7 source:agent

Problem

PR #1825 added site/tests/test_operation_reference.py. It pins the 44 operation
pictures against the OpType enum. Nothing runs it. cargo xtask gate covers
Rust suites only. The site job in release.yml runs zola build but not this
Python test. No other workflow calls it.

A later PR that adds an OpType kind can forget its reference section and its
picture view. No gate fails, so the site stays incomplete without a signal.

Fix

Run the test from the site job of release.yml, next to the Zola build.
Add the run command to site/README.md so contributors know it exists.
Keep the test's Zola arm skippable when the binary is absent, as today.

Done means:

  • A cut run executes test_operation_reference.py in the site job.
  • The job fails when a picture view or a reference section is missing.

Refs #1250

Dominant language
Rust
Stars
8
Forks
11
Avg merge
6h 45m
Merged PRs (30d)
905

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NeoTech/Camcraft

All issues in NeoTech/Camcraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.