[10:49] schestowitz[10:49] schestowitzAt KDE we have multiple levels of quality assurance ranging from various degrees of a humans testing features to fully automated testing. Indeed automated testing is incredibly important for the continued quality of our software. A big corner stone of our testing strategy are so called unit tests, they test a specific piece of our software for its behavior in isolation. But for many aspects of our [10:49] schestowitz software we need a much higher level view, testing pieces of Plasmas application launcher in isolation is all good and well but that wont tell us if the entire UI can be easily navigated using the keyboard. For this type of test we require a different testing approach altogether. A couple months ago Ive set set out to create a testing framework for this use case and Im glad to say that it has matured enough to be used for writing tests. [10:49] schestowitz Id like to walk you through the technical building blocks and a simple example.
[10:49] schestowitz
[11:12] schestowitz[11:12] schestowitzThis device serves two purposes: it lets the resident gain entry to the building without needing a key and it lets the resident give access to visitors when they arent home. It listens for a pattern of noise created by the visitor pressing and releasing the talk button on the intercom. When they press that button, audible noise comes througheven when nobody is speaking. In this case, it listens [11:12] schestowitz for noise above a threshold (the button pressed) for one second, no noise (button released) for one second, and then noise again for another second. If it hears that pattern, it uses a servo to press the door unlock button on the intercom.
[11:12] schestowitz
[11:17] schestowitz[11:17] schestowitzIDN works by having apps convert the Unicode name into the ASCII based punycode version under the hood, and then use that with DNS etc. The puny code version of rksmrgs.se becomes xn--rksmrgs-5wao1o.se. A pretty clever solution really.
[11:17] schestowitz
[11:33] schestowitz[11:33] schestowitzGoing from the simple color managed PDF generator discussed in the previous blog post into something more useful requires getting practical. So here is a screenshot of a "print ready" PDF document I generated with the code showing a typical layout you'd use for a softcover book. As printers can't really print all the way to the edges of paper, the cover needs to be printed to a larger sheet and then cut to [11:33] schestowitz its final size.
[11:33] schestowitz