Autotest to simulate that no screens are available
ClosedPublic

Authored by graesslin on Jul 18 2016, 1:10 PM.

Details

Summary

The test creates a Wayland display, locks the screen and destroys
the output. In this situation kscreenlocker_greet should not crash
or exit. The screen should stay locked.

Diff Detail

Repository
R133 KScreenLocker
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
graesslin updated this revision to Diff 5272.Jul 18 2016, 1:10 PM
graesslin retitled this revision from to Autotest to simulate that no screens are available.
graesslin updated this object.
graesslin edited the test plan for this revision. (Show Details)
graesslin added reviewers: Plasma, bshah.
Restricted Application added a project: Plasma. · View Herald TranscriptJul 18 2016, 1:10 PM
Restricted Application added a subscriber: plasma-devel. · View Herald Transcript

Most likely the test won't work on build.kde.org due to the known problems of no OpenGL

autotests/noscreens.cpp
139

without the timeout kscreenlocker_greet crashes, but I fail to get the backtrace. DrKonqi shows weird stuff for me

bshah accepted this revision.Jul 18 2016, 1:15 PM
bshah edited edge metadata.
This revision is now accepted and ready to land.Jul 18 2016, 1:15 PM
This revision was automatically updated to reflect the committed changes.