good chemistry is complicated,
and a little bit messy -LW
Autotesting dependencies compatibilityby vsespb (Chaplain)
|on Jun 19, 2013 at 17:42 UTC||Need Help??|
I know there is a CPANTesters tool.
It tests a distribution with different perl versions (+different compile options) on different platforms (+ different distros/versions).
It's great to detect:
1. incompatibility of code with certains perl versions
2. integration tests failure (when tests involve system calls that act differently on different platforms)
3. incompatibility with different versions of core modules
However it looks useless to test accuracy of CPAN dependencies versions (prereqs/build_requires in META).
For example, we test module XYZ. It requires module ABC with "version=0".
Cpan testers will install _latest_ version of ABC, if ABC is not installed, or use existing version if ABC is installed as core module, or it's a dependency of CPAN Testers itself, or by chance was installed on the box.
I wrote script for myself which tests my code with all versions of all dependencies that I use (in turn, not all possible combinations).
Result looks useful, I found couple of old versions of modules that are not compatible with my code, couple of bug in 3rd party modules prereqs specifications. Several 3rd party module versions that don't build due to a bug which was later fixed (that part is useless for me).
I also was checking BACKPAN versions. If module is on backpan it can still be installed on user machines (installed in the past), or it can be distributed with OS package manager (without CPAN).
Now I am wondering is there similar feature in CPAN testers ?
Or any other existing service ?
Should such functionality be added to CPAN testers or it's just different from CPAN testers project goal?