You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tag: Branch: Tree: a3366d5a42

wilder

wilder-5.14

wilder-5.17

wilder-5.18

wilder-5.19

wilder-5.22

wilder-5.24

wilder-5.25

wilder-5.26

wilder-5.26-rebase

wilder-broken-krunner

wilder-portage

wilder-portage-prov

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'a3366d5a42'

${ noResults }

plasma-workspace/ksmserver/screenlocker/greeter/autotests

History

Martin Gräßlin 7b69bdc753 Add unit test for kscreenlocker_greet to test all signals ... The idea behind this unit test is to verify that no matter which signal is sent to the greeter it doesn't return an exit code of 0 which would indicate a successful authentication. The test starts the greeter (needs to be installed) and waits 5 sec to make sure that the greeter is really up and running. If the signal is sent to early it's causing a CrashExit, which is fine but not the expected result. There's an additional test to verify that the early sent signal results in CrashExit. REVIEW: 117893		12 years ago
..
CMakeLists.txt	Add unit test for kscreenlocker_greet to test all signals	12 years ago
authenticatortest.cpp	Add password checking to screenlocker	12 years ago
fakekcheckpass.c	Add password checking to screenlocker	12 years ago
killtest.cpp	Add unit test for kscreenlocker_greet to test all signals	12 years ago