tests/auto/solutions/tasking/tasking.qbs

QtcAutotest {
    name: "Tasking autotest"

    Depends { name: "Qt"; submodules: ["concurrent", "network"] }
    Depends { name: "Tasking" }

    files: "tst_tasking.cpp"
}
Solutions: Long live Solutions! Short live Tasking in Solutions! Add src/libs/solutions/README.md with the motivation and hints. Move TaskTree and Barrier from Utils into Tasking object lib, the first solution in Solutions project. Tasking: Some more work is still required for adapting auto and manual tests. Currently they use Async task, which stayed in Utils. For Qt purposed we most probably need to have a clone of Async task inside the Tasking namespace that is more Qt-like (no Utils::FutureSynchronizer, no priority field, global QThreadPool instead of a custom one for Creator). Change-Id: I5d10a2d68170ffa467d8c299be5995b9aa4f8f77 Reviewed-by: Cristian Adam <cristian.adam@qt.io> Reviewed-by: hjk <hjk@qt.io> Reviewed-by: Eike Ziller <eike.ziller@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> 2023-05-10 21:38:41 +02:00			`QtcAutotest {`
			`name: "Tasking autotest"`

TaskTree tests: Add stress test for storages Run the same recipe concurrently. Test whether handling the same storage concurrently works properly. This addresses the 24th point in the master task below. Task-number: QTCREATORBUG-28741 Change-Id: Ic3358bef335b96b7dc2b88ad8102c440db5dafbf Reviewed-by: hjk <hjk@qt.io> 2023-11-06 08:29:33 +01:00			`Depends { name: "Qt"; submodules: ["concurrent", "network"] }`
TaskTree tests: De-utils-ize TaskTree tests Make the TaskTree tests dependent only on Tasking lib. Introduce simple Timeout and Delay tasks for tests. Using Timeout and Delay has a big advantage for these tests, since e.g. when scheduling two parallel tasks with the same timeout, we can expect the proper order in which they finish. With AsyncTask it wasn't possible. Now, the tests should be much more reliable and shouldn't exibit flakiness anymore. Use TickAndDone for Barrier tests. Limit the tests' execution time from ~100ms into ~30ms. Change-Id: Ifa08fd62c1a2759a877231c2220e353c1a26364f Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io> 2023-05-27 17:20:40 +02:00			`Depends { name: "Tasking" }`
Solutions: Long live Solutions! Short live Tasking in Solutions! Add src/libs/solutions/README.md with the motivation and hints. Move TaskTree and Barrier from Utils into Tasking object lib, the first solution in Solutions project. Tasking: Some more work is still required for adapting auto and manual tests. Currently they use Async task, which stayed in Utils. For Qt purposed we most probably need to have a clone of Async task inside the Tasking namespace that is more Qt-like (no Utils::FutureSynchronizer, no priority field, global QThreadPool instead of a custom one for Creator). Change-Id: I5d10a2d68170ffa467d8c299be5995b9aa4f8f77 Reviewed-by: Cristian Adam <cristian.adam@qt.io> Reviewed-by: hjk <hjk@qt.io> Reviewed-by: Eike Ziller <eike.ziller@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> 2023-05-10 21:38:41 +02:00
			`files: "tst_tasking.cpp"`
			`}`