in reply to Test Failure Best Practices, or when is it ok to "force install"
Sometimes the failure may be cause by a difference in the system that the module is designed on versus where you are running it. I.e. it was designed on a Linux machine, but you are installing it on a Windows machine. In this case failed tests could indicate bugs that the author didn't know about. It is always a good practice to check the bug list for that module and see if this is a known issue.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Test Failure Best Practices, or when is it ok to "force install"
by hsmyers (Canon) on Jun 26, 2006 at 16:11 UTC |