Re: How to organize and install test files

Why would you want to do this? (This is no implicit "don't do it!" question, but a serious question).

As long as you don't change the modules the test results shouldn't change.

And if you change the modules you do an installation - and you can execute the tests along the way.

Comment on Re: How to organize and install test files

Replies are listed 'Best First'.
Re^2: How to organize and install test files by roman (Monk) on Oct 12, 2007 at 13:28 UTC
Because the unchanged module may depend on other modules which were just changed. For example after refactoring and reinstallation of base class for call statements (I work in the telecommunications) it would be nice to check whether the derived classes (incoming call statements, outgoing call statements, ...) are still working. Another real (my) world example is the upgrade of SOAP::Lite and XML::LibXML which we use extensively. I wish I checked our modules before this upgrade.	[reply]

Replies are listed 'Best First'.

Re^2: How to organize and install test files
by roman (Monk) on Oct 12, 2007 at 13:28 UTC

Because the unchanged module may depend on other modules which were just changed.

For example after refactoring and reinstallation of base class for call statements (I work in the telecommunications) it would be nice to check whether the derived classes (incoming call statements, outgoing call statements, ...) are still working.

Another real (my) world example is the upgrade of SOAP::Lite and XML::LibXML which we use extensively. I wish I checked our modules before this upgrade.

[reply]