-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated tests to detect BarcodeFormat & Barcode data #219
base: master
Are you sure you want to change the base?
Conversation
…ed barcode format. Refer PR-219 ftylitak/qzxing#219
Updated resources for this tests. So the resources PR-1 needs to be merged as well. |
Hello @maheshdev305, i have two comments:
|
Qt6 compilation errors are present without this PR changes as well. Please check from your side as well.
Not sure why it was a huge difference at your side. Below is the result counts from my machine.
Attached below is the complete output from my machine. Please do review and let me know. |
a) regarding the compilation errors, I was facing them when building for Qt 6.0. When compiling with Qt 6.2 it was successful. b) the reason why I am getting low success rate in the tests is because in both Ubuntu and Windows that I have tested, around 500 of the images can not be read for some reason. This resulted the QImage.isNull to be true after this line: Line 581 in 6ea2b31
Strange enough, the previous implementation of the tests work fine. So, this is the reason why this PR is not yet merged. I gave it a try though I wasn't able to understand why this happens. Now, since this PR regards the tests and not the core library, I will consider it low priority. This means that even though I am interested in merging it, I currently do not have time to debug why I get this strange behavior of the Null images. If anyone has any suggestion, I would be more than willing to test it ASAP. |
Below are my observations...
Also, requesting you to consider this as a little higher priority and let me know the results. |
The existing tests was just reporting the Decoded barcode data alone.
So, updating the tests to Decode barcode data as well as the Barcode Type/Format(i.e. QR_CODE , CODE_128 and so on)