Because ctest is standard cmake tool and it is supported directly by cmake
files allowing OOTB for example parallelisation of ctest units execution (it
allows as well exclude some exact units paralel execution
https://www.scivision.dev/cmake-resource-lock-ctest/ .. .if it was the cause of
not choosing ctest).
Why to maintain own test suite framework? 🤔
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2648#issuecomment-1711411289
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2648/1711411...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
