[Merge] lp:~phablet-team/qt-halide/unit-tests into lp:qt-halide

[Ugo Riboni]

> > > 9) is there any way to have a test/check target and possibly a coverage
> > > target appearing in QtCreator?
> >
> > Not that I know of, sorry. Zoltan seems to agree that there is no way to add
> > targets there from cmake.
> 
> It does not seem hard to add an entry target in QtC: I see all the generators
> AOT targets showing up in QtC.

These are added with add_executable(), but we add our check target with add_custom_target() which is not recognized by qtcreator, so it will not appear there.

> > >  21) output is unreadable due to the many QDEBUG & QWARN
> > 
> > "-silent" is not the solution. qdebug should be disabled but qwarnings should not and be tested instead http://doc.qt.io/qt-5/qml-qttest-testcase.html#ignoreWarning-method

When not in debug build mode all qDebug() output is now disabled.
Regarding using ignoreWarning to catch the the warnings during tests, this can be done in a few cases, but there are other cases when not possible, i.e.:
- when the warning is generated during test init or cleanup it is still reported as part of the next function that is run, but there is no way to catch it
- there are some mysterious warnings generated from qmltestrunner::UnknownTestFunc(). my guess is that they are generated when the QML is being initialized. I don't think there is a way to catch them 


-- 
https://code.launchpad.net/~phablet-team/qt-halide/unit-tests/+merge/254064
Your team Ubuntu Phablet Team is subscribed to branch lp:~phablet-team/qt-halide/unit-tests.