Don't use tier3 frameworks in unit tests
ClosedPublic

Authored by svuorela on Feb 5 2017, 4:06 PM.

Details

Summary

Port away from tier2 and 3 frameworks in the unit tests

Test Plan

Tests still passes

Diff Detail

Repository
R266 Breeze Icons
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
svuorela updated this revision to Diff 10942.Feb 5 2017, 4:06 PM
svuorela retitled this revision from to Don't use tier3 frameworks in unit tests.
svuorela updated this object.
svuorela edited the test plan for this revision. (Show Details)
svuorela set the repository for this revision to R266 Breeze Icons.
Restricted Application added a project: Frameworks. · View Herald TranscriptFeb 5 2017, 4:06 PM
Restricted Application added a subscriber: Frameworks. · View Herald Transcript
dfaure accepted this revision.Feb 12 2017, 8:45 AM
dfaure added a reviewer: dfaure.
This revision is now accepted and ready to land.Feb 12 2017, 8:45 AM
sitter accepted this revision.Feb 14 2017, 10:47 AM
sitter edited edge metadata.

Ah! I hadn't even thought of QSettings. Love the change.

FWIW if you fancy more work: seeing as the test now has its own enums you could align the Context enum values' names with their string representation allowing parseContext to work like parseType by letting the metaobject do the mapping.

This revision was automatically updated to reflect the committed changes.