QtCS2017 UnitTesting: Difference between revisions
Jump to navigation
Jump to search
(Created page with "* QTestLib has some legacy ** Need to use a class for test functions ** QASSERT and QCOMPARE all over, but little description ** Written with various flavours of QTestLib ** h...") |
(No difference)
|
Latest revision as of 15:20, 9 October 2017
- QTestLib has some legacy
- Need to use a class for test functions
- QASSERT and QCOMPARE all over, but little description
- Written with various flavours of QTestLib
- https://bugreports.qt.io/browse/QTBUG-63146
- Running tests
- Assuming synchroneous
- QWaitFor, QWaitForWindowActive etc. are used a lot, sometimes perhaps with little understanding?
- Specific to UI testing
- Need to handle asynchroneous behaviour better
- Use (more) mocks?
- Testing framework (used for Qt development)
- Stay with QTestLib as is
- Modify QTestLib
- Replace QTestLib with new framework
- Write from scratch (NIH)
- Use existing
- (Can pull reusable components out of QTestLib)
- Catch (https://github.com/philsquared/Catch)
- GoogleTest (https://github.com/google/googletest)
- Cucumbercpp with Qt integration
- Could we use Squish more for this?