Standardised workflow for printer / library testing.

[Dshosev]

I would try to work out a standardised testing workflow, so that new printers and / or changes of the implemented features can be tested easily and repeatable. I think issues could be tracked down faster with the information of some standard test.

I got this idea, because I am working with a thermal printer, that is not in the list of tested printers, but I don't know if I had tested everything, for example. But I don't have unlimited access to this printer. So it would have been nice to just fire up a test-app that handles all the cases.

What do you guys think about that? Any further ideas about this?

Last but not least, @andrey-ushakov, thank you for this great package. It helped me quite a lot.

[andrey-ushakov]

Hi Josef, Thank you for your feedback! A test app is exactly what I was thinking to do, but unfortunately, I have less and less time for this package...I hope I will do it one day. And of course, if you can improve anything in this repo, feel free to add a pull request!

[Dshosev]

Hi Josef, Thank you for your feedback! A test app is exactly what I was thinking to do, but unfortunately, I have less and less time for this package...I hope I will do it one day. And of course, if you can improve anything in this repo, feel free to add a pull request!

I will try to get some time the next days to start think about this. Maybe i can come up with something.

[ayushin]

We've developed a higher-level abstraction package that abstracts combines the searching and printing functionality of the bluetooth, network but also some brand specific printers like Star...

It has a way for search for a printer, saving it in shared prefs and an abstraction layer to print tickets via different printer interfaces such as ESC or StarPrnt

https://github.com/apexlabs-ai/pos_printer_bloc/tree/dev

It would be great to have a plug-and-play solution for flutter where you can just find, connect and print on any device.