Preparing a new release for a package as portable as MPICH requires testing on a wide variety of platforms. To help test a new release of MPICH, we use several programs and scripts that build and test the release on a new platform. The doc/port program included in the MPICH distribution performs a build, checking for errors from the make, followed by both performance and correctness tests. The output from this program is a postscript file that describes the results of the build and tests; this postscript file is then made available on the WWW in a table at http://www.mcs.anl.gov/mpi/mpich1/porting/port version-number.html. Another program then is used to do an installation and to check that both MPICH and the other tools (such as upshot and mpicc) work correctly. For networks of workstations, additional tests (also managed by a separate program) test heterogeneous collections of workstations. By automating much of the testing, we ensure that the testing is reasonably complete and that the most glaring oversights are caught before a release goes out. Unfortunately, because the space of possible tests is so large, these programs and scripts have been built primarily by testing for past mistakes.