> 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).
Yes, we're very well aware of that.
Also, our current test-suite *does* run the individual tests in parallel.
> Why to maintain own test suite framework? 🤔
Because nobody has gotten around to porting the whole test-suite written in
Autotest to another framework yet? It's not an easy task.
For the record, we have an open ticket to evaluate other test frameworks
including ctest: https://github.com/rpm-software-management/rpm/issues/2098
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2648#issuecomment-1711434690
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2648/1711434...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
