[sane-devel] test backend

Jeff jffry at posteo.net
Fri Mar 30 11:54:38 UTC 2018

I know about the test backend, and it is very useful.

However, it cannot cover every combination of option type/reload that is
out in the wild.

I often have to spend hours mocking up a backend from a log file to be
able to reproduce a bug in gscan2pdf, in order then to be able to fix it.

It would be really useful to have a SANE option to test a real backend
without the scanner being present. i.e. instead of calling
sane_device_open, to be able to call sane_device_mock_open or similar,
which would still allow sane_set_option, etc., but would not try to pass
the options to the hardware.

Unfortunately, I assume that to implement something like this, every
backend would have to be changed to separate out the hardware calls.

Would anyone else find something like this useful?

Does anyone have any better ideas for supporting hardware for which
there is no access?



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20180330/3b46d673/attachment.sig>

More information about the sane-devel mailing list