Hi Povilas, Povilas Kanapickas writes:
> Hey Olaf, > > Thanks for reply! > > On 09/11/2018 13:40, Olaf Meeuwissen wrote: >> Hi, >> >> Still interested? Just request access to the sane-project group as a >> whole at https://gitlab.com/groups/sane-project/-/group_members or just >> the backends project (if not interested in any of the other projects) at >> https://gitlab.com/sane-project/backends/project_members. >> >> Hope this helps (and apologies for the belated follow-up). > > Yes, I'm still interested. I've shopped around the local used hardware > market and got some scanners that cover most of the currently supported > chipsets. So even testing will be less of a problem for me. Cool! > I've opened the page for backends project > https://gitlab.com/sane-project/backends/project_members, but it does > not allow me to request access. According to > https://docs.gitlab.com/ee/user/project/members/, maybe request access > to projects is disabled? Weird. Both the group and backends project have requesting access enabled as far as I can see. Were you logged in at the time or not? Anyway, I added you with developer permissions and mentioned you as one of the genesys maintainers in https://gitlab.com/sane-project/backends/commit/dc8b27c1eff4617596f7b9304ef743d415791c26 > One of the things that I'd like to do long term would be to create a > test framework that works at libusb layer, so that we could intercept > data what data is written where and how the code behaves depending on > what data is read. The we could compare that to known good replays. We > could run such tests on Gitlab and hopefully catch the majority of > regressions. > > Also, it would be great if we could add hooks that capture live data > from scanning sessions and create tests based on that. We could ask > users with hardware that we don't access to, but which still works to > scan some blank page and send a log to us. This way we could create a > regression suite with which we could be reasonably sure that old device > support code does not bitrot. Eh, running device tests on GitLab would be a bit difficult. Oh wait, you're talking about replaying known good (or at least observed) I/O sequences against *changed* backend code to see if the changes introduce any breakage. Way cool! Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to [email protected]
