Re^9: Why is it in some other popular languages fewer steps and potential issues when installing libraries no testing needed and no compilation of C/C++ code done

Crud! You know what I just realized...we can't really trust the tests that come from CPAN modules in all cases. Take the following example from GoogleProvisioningAPI:

Google-ProvisioningAPI-0.11/t/Google-ProvisioningAPI.t
# Before `make install' is performed this script should be runnable wi
+th
# `make test'. After `make install' it should work as `perl Google-Pro
+visioningA
PI.t'

#########################

# change 'tests => 1' to 'tests => last_test_to_print';

use Test::More tests => 1;
BEGIN { use_ok('Google::ProvisioningAPI') };

#########################

# Insert your test code below, the Test::More module is use()ed here s
+o read
# its man page ( perldoc Test::More ) for help writing this test scrip
+t.
[download]

That's it. Given such scant testing it is impossible to determine whether updates or changes to the module will break existing code.

Celebrate Intellectual Diversity

Comment on Re^9: Why is it in some other popular languages fewer steps and potential issues when installing libraries no testing needed and no compilation of C/C++ code done Download Code

Replies are listed 'Best First'.
Re^10: Why is it in some other popular languages fewer steps and potential issues when installing libraries no testing needed and no compilation of C/C++ code done by Anonymous Monk on Apr 12, 2011 at 16:46 UTC
That's it. Given such scant testing it is impossible to determine whether updates or changes to the module will break existing code. Um, that is why your existing code should include tests :)	[reply]