This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Fortran testing strategies
- From: Andreas Voellmy <andreas dot voellmy at gmail dot com>
- To: fortran at gcc dot gnu dot org
- Date: Thu, 28 Jul 2005 08:36:32 -0600
- Subject: Fortran testing strategies
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; b=ex+lWU58mg5V/umcO1MvkIjYN9Pa/4HgZU+0jcrULH4POAvR4PYM4mDgPZqo76J3t/7Yo1lKUxYzAsLiG+zifkbhlF5ERBb2OuOA2ZM1BU8jMNqr8EYcD8vH8eRjYIQ4CrWuU3xKRDt2+5rhJKceoO/V95xfZiaLoU8Hf9/Jv3M=
- References: <20050728141222.869B01DC0BB@bromo.msbb.uc.edu>
Hi,
I'm pretty new to this list. I've noticed a lot of posts mentioning
test suites. I'm wondering if someone could describe how the fortran
test suites are implemented. Are they written with the help of a test
framework, maybe something like the xUnit frameworks? Are there some
useful utility functions people have developed?
I'm asking because I am adding some new features on a large fortran
project and I'd like to incorporate unit testing on these new
features. It would be great if anyone can share their test strategies
here.
Thanks, Andreas