wilderjds/kwin - kwin - gitea-jacopods

14463 Commits

36 Branches

0 Tags

96 MiB

Tag: Branch: Tree: 8a85cc5f9c

Commit Graph

Author	SHA1	Message	Date
Martin Gräßlin	53004b95ff	Port left over qDebug to qCDebug	11 years ago
Martin Gräßlin	a7cf808dea	Improve the TestScreens autotest	12 years ago
Martin Gräßlin	4eadc9daef	[auto-tests] Add an initial test for Screens This is a very interesting auto test as Screens uses both Workspace and Client. Thus it operates in the "impossible to mock" area. The solution is to provide mock includes in autotests and ensure that when building the auto-test the mock header includes will be picked first. There is now a mock class for Workspace and Client providing just the API pieces used inside Screens. As Screens is abstract and we cannot properly interact with QDesktopWidget there is also a MockScreens class inheriting from Screens and mocking the required functionality (by just operating on a list of QRects). The auto-test itself is only performing checks on the abstract class. The mock class is indirectly tested by Screens calling into the virtual methods. The test case is not yet complete, but looking quite good already.	12 years ago

Author

SHA1

Message

Date

Martin Gräßlin

53004b95ff

Port left over qDebug to qCDebug

11 years ago

Martin Gräßlin

a7cf808dea

Improve the TestScreens autotest

12 years ago

Martin Gräßlin

4eadc9daef

[auto-tests] Add an initial test for Screens

This is a very interesting auto test as Screens uses both Workspace
and Client. Thus it operates in the "impossible to mock" area.

The solution is to provide mock includes in autotests and ensure that
when building the auto-test the mock header includes will be picked
first. There is now a mock class for Workspace and Client providing
just the API pieces used inside Screens.

As Screens is abstract and we cannot properly interact with
QDesktopWidget there is also a MockScreens class inheriting from Screens
and mocking the required functionality (by just operating on a list of
QRects).

The auto-test itself is only performing checks on the abstract class.
The mock class is indirectly tested by Screens calling into the virtual
methods. The test case is not yet complete, but looking quite good
already.

12 years ago

3 Commits (8a85cc5f9c600b5df3e868a4d0524a418ce5447f)