Test-suite interop: run functional tests against presswork (Rust cupsd reimplementation)

Open
#499 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
44/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, python, rust
Domain
ci-cd, testing

Research direction

First check how the functional suite is run in CI and whether it exercises a daemon, then determine whether a second daemon is welcome. The proposal names no files or tests, so locate the suite's CI entry point and identify how it installs and starts stock cupsd. Done means an experimental CI leg runs the functional suite against presswork and reports actionable failures.

Written by the indexing model from the issue text.

Description

Hi - I'm the author of presswork, a drop-in replacement for the CUPS 2.x scheduler/daemon written in Rust (Apache-2.0 OR MIT). Same IPP wire protocol, config files, spool layout, and backend contract; upstream ipptool matrix 34/0/1, upstream test/5.x client suite 34/34.

Proposal: scp's test suite exercises real daemon behavior (queue create/delete, job ops, device URIs) - running it against presswork in addition to stock cupsd would validate both sides' IPP semantics and surface divergences as actionable bugs.

Happy to do the work (a CI leg installing presswork via the .deb or ghcr.io/vindeckyy/presswork:latest image, marked experimental). Is the functional suite currently daemon-backed in CI, and is a second-daemon leg welcome?

Dominant language
Python
Stars
209
Forks
111
Avg merge
2d 3h
Merged PRs (30d)
8

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 OpenPrinting/system-config-printer

All issues in OpenPrinting/system-config-printer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.