- 17 Mar, 2020 40 commits
-
-
Make sleep time on verification dependent on the environment, so that it's different when under valgrind
-
Avoid using a temporary file for reading the utilities output, so we can read it as it comes, ignoring the previous one, and avoiding open/closing the file. To keep the output printing on cleanup working, adding an utility function that reads the output and save it for later printing
-
This is particularly useful when using valgrind or address sanitizer to read the output log
-
Avoid repeating the same operation to launch the utilities all the times, but provide instead a function that allows to start a process and saves its output without having to handle this in every test. Simplify the operation when we just want the final output, still reusing the same code.
-
-
Add support to run fprintd-utils to test fprint daemon, and ensure that a device is released and its operation cancelled once a caller goes away. Related to libfprint/fprintd#37
-
-
-
Throw a NoEnrolledPrints error if the requested finger isn't present in the gallery.
-
-
-
When starting an enroll when verification is in progress (and vice-versa) we emit an AlreadyInUse error, however when calling VerifyStop() during an enrollment (and vice-versa) we just return a NoActionInProgress error, which is not the case. So let's be consistent and change the error type.
-
-
-
-
-
-
-
Given we don't support adding devices after we created the manager (yet) we must ensure that once the name appeared we have them all
-
-
This may be used by any class inheriting FPrintdTest, so let's move it at lower level.
-
When we run tests in a system with real devices, we may try to initialize the real ones, while we can just ignore them all in tests. We do it in setUp instead of setUpClass to allow tests to change this if they need to, but just for temporary.
-
Ensure that we properly handle all the errors that a driver may return us
-
The tests are repeated for both verify and identify actions
-
-
Respect protocol, and use proper name
-
Use proper names for enroll retry errors, fixing a copy/paste error from the verify code.
-
-
Avoid doing fo reach test the Claim/Release procedure manually if it is just a prerequisite for the test.
-
-
Ensure that the daemons are always terminated after each test, even on failure, so that we don't have to do hacks such as always trying to stop them
-
-
Unset the dbus environment that may affect the dbus tests using GTestDBus utility, instead of doing it manually.
-
When creating a new unit we used to get the system bus via Gio.bus_get_sync, however this has a singleton implementation, and so would always return the same connection, creating issues in tests when a new test suite is added because the newly got connection would be already closed. So, just manually create a new bus connection, also close the bus and cleanup the test bus in dbus.
-
-
-
Ensure we nullify them when the test is done.
-
-
Since we rely on meson now to do this, we don't need to have manual management of the timeout
-
Ensure that we get an error when releasing a device that is in process of enrollment, verification or identification
-
