You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, unit tests look like a list of popular Qt scenarios and their ideal results after deployment.
The tests simply compare matching results.
But this is too complicated, because Qt is currently a truly large framework with numerous scenarios and numerous modules.
Moreover, modules are constantly changing, so maintaining tests in cqtdeployr is a real challenge.
We need to come up with a new way to test the utility that prevents regression while avoiding the need to constantly update test cases with the release of new Qt versions.
If anyone has any ideas, I'd love to hear them.
Until then, I'm disabling old tests, as I don't have the time to maintain them right now.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Currently, unit tests look like a list of popular Qt scenarios and their ideal results after deployment.
The tests simply compare matching results.
But this is too complicated, because Qt is currently a truly large framework with numerous scenarios and numerous modules.
Moreover, modules are constantly changing, so maintaining tests in cqtdeployr is a real challenge.
We need to come up with a new way to test the utility that prevents regression while avoiding the need to constantly update test cases with the release of new Qt versions.
If anyone has any ideas, I'd love to hear them.
Until then, I'm disabling old tests, as I don't have the time to maintain them right now.
All reactions