quagga2 VS WebdriverIO

The next level up from that would be to hook up the business-specific frontend to a barcode scanner and at that point not only could both clients & business know what items are available, but also their current stock & availability.

quokka2

I used the zebra crossing app ("barcode scanner") in mass scan mode to scan all my books. The app keeps a history of scanned items and you can export it as CSV. This of course is not very "nice" but a very fast way to scan all your books. There is also some JS implementation for isbn scanning which works ok. It is used by bookwyrm which is open-source (but not free software).

Honorable mention to quagga. No longer actively maintained, but there is an active fork quagga2.

The component used for the camera barcode scanner is quagga2, feel free to improve it or even replace it with another one and provide a pull request if that maybe works better. Also already partly tracked in #737.

The camera barcode scanner component used is quagga2. Scanning highly depends on lighting, the angle and so on and is IMHO generally slow and error prone. I would only use a laser scanner which is 1000 % faster and works under any lighting condition. On my phone I personally simply use the dropdown / search way, since still faster than a single camera barcode scan...

The component used is Quagga2 and there are also some options in data/config.php to tweak it.

3.WebdriverIO: WebdriverIO is another popular open-source test automation framework. Key Features: Integrates well with popular testing frameworks (e.g., Mocha, Jasmine). Supports both synchronous and asynchronous commands. Works with various browsers and platforms

Webdriver.io

There is a tool called webdriver.io which purports to handle mobile automation. I haven't had a chance to play with it yet but it's on my radar.

We recently hired an engineer to write us integration tests with webdriver.io. All of our other tests run fine in Github actions - rspec, javascript jest, etc.

Your automated tests will act on behalf of a real user, open a real web browser (typically Chromium, Chrome, Firefox) using one an existing technology like Webdriver and add some syntactical sugar on top.

WebdriverIO (abbreviated as WDIO) is an E2E testing framework for Node.js. It allows you to automate all kinds of web and mobile applications using the Webdriver or Chrome DevTools protocols.

i recall having to deal with elements inside iframes and shadow roots when using webdriver.io for testing. you can always inspect an element and copy the selector. if it is unique to the page it should work