cmd/mfp-test: add print system testing pipeline skeleton#78
Open
ArmxG wants to merge 12 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces cmd/mfp-test:- the skeleton of the full-stack print system testing pipeline.
What was added
cmd/mfp-test/test/capture.go
DocumentCapture implements abstract.Printer and collects all incoming print documents (job parameters + raw bytes)
for later inspection. It is thread-safe and signals via a channel when the first document arrives.
cmd/mfp-test/test/cupsctl.go
CreateCUPSQueue and RemoveCUPSQueue manage CUPS printer queues via lpadmin. The queue uses the IPP
Everywhere driver (-m everywhere) which works with any standards-compliant IPP printer.
cmd/mfp-test/test/command.go
The main command handler:
(WithoutCancel ensures cleanup runs even after ctx is cancelled)
cmd/mfp-test/main.go
Thin entry point following project convention:
test.Command.Main(nil)
How to test
cd cmd/mfp-test
go build -o mfp-test .
./mfp-test --model <printer-model-file.py> -v
A model file with ipp.attrs defined is required. Example model files can be generated with mfp-query or obtained from the modeling package.
Expected output:
virtual IPP printer at ipp://localhost:60000/ipp/print
CUPS queue "mfp-test" ready at ipp://localhost:60000/ipp/print
sending test PNG via lp...
captured doc 1: N bytes, format="image/pwg-raster", job="..."
Notes