Applying Software Testing Metrics to Lapack

  • David J. Barnes
  • Tim R. Hopkins
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3732)

Abstract

We look at how the application of software testing metrics affects the way in which we view the testing of the Lapack suite of software. We discuss how we may generate a test suite that is easily extensible and provides a high degree of confidence that the package has been well tested.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Anderson, E., Bai, Z., Bischof, C., Blackford, S., Demmel, J., Dongarra, J.J., Du Croz, J., Greenbaum, A., Hammarling, S., McKenney, A., Sorensen, D.: LAPACK: users’ guide, 3rd edn. SIAM, Philadelphia (1999)CrossRefGoogle Scholar
  2. 2.
    Barker, V.A., Blackford, L.S., Dongarra, J., Du Croz, J., Hammarling, S., Marinova, M., Waśniewski, J., Yalamov, P.: LAPACK95: Users’ Guide. SIAM, Philadelphia (2001)CrossRefGoogle Scholar
  3. 3.
    Barnes, D.J., Hopkins, T.R.: The evolution and testing of amediumsized numerical package. In: Langtangen, H.P., Bruaset, A.M., Quak, E. (eds.) Advances in Software Tools for Scientific Computing. Lecture Notes in Computational Science and Engineering, vol. 10, pp. 225–238. Springer, Berlin (2000)Google Scholar
  4. 4.
    Beizer, B.: Software System Testing and Quality Assurance. Van Nostrand Reinhold, New York (1984)Google Scholar
  5. 5.
    Gunnels, J.A., Gustavson, F.G., Henry, G.M., van de Geijn, R.A.: FLAME: Formal Linear Algebra Methods Environment. ACM Transactions on Mathematical Software 27(4), 422–455 (2001)MATHCrossRefGoogle Scholar
  6. 6.
    Hayhurst, K.J., Veerhusen, D.S., Chilenski, J.J., Rierson, L.K.: A practical tutorial on modified condition/decision coverage.Technical Report TM-2001-210876, NASA, Langley Research Center, Hampton, Virginia 23681-2199 (May 2001)Google Scholar
  7. 7.
    Hopkins, T.: A comment on the presentation and testing of CALGO codes and a remark on Algorithm 639:To integrate some infinite oscillating tails. ACM Transactions on Mathematical Software 28(3), 285–300 (2002)MATHCrossRefMathSciNetGoogle Scholar
  8. 8.
    ISO, Geneva, Switzerland. ISO/IEC 9899:1990 Information technology - Programming Language C (1990) Google Scholar
  9. 9.
    ISO/IEC. Information Technology – Programming Languages – Fortran - Part 1: Base Language (ISO/IEC 1539-1:1997). ISO/IEC Copyright Office, Geneva (1997)Google Scholar
  10. 10.
    Kaner, C., Falk, J., Nguyen, H.Q.: Testing Computer Software. Wiley, Chichester (1999)Google Scholar
  11. 11.
    Lahey Computer Systems, Inc., Incline Village, NV, USA. Lahey/Fujitsu Fortran 95 User’s Guide, Revision C edition (2000)Google Scholar
  12. 12.
    LDRA Ltd, Liverpool, UK. LDRA Testbed: Technical Description v7.0 (2000)Google Scholar
  13. 13.
    Numerical Algorithms Group Ltd., Oxford, UK. NAGWare Fortran Tools (Release 4.0) (September 1999)Google Scholar
  14. 14.
    Numerical Algorithms Group Ltd., Oxford, UK. NAGWare f95 Compiler (Release 5.0) (November 2003)Google Scholar
  15. 15.
    Offut, A.J., Lee, A., Rothermel, G., Untch, R.H., Zapf, C.: An experimental determination of sufficient mutant operators. ACM Transactions on Software Engineering Methodology 5(2), 99–118 (1996)CrossRefGoogle Scholar
  16. 16.
    SunMicrosystems, Inc., Santa Clara, CA. FortranUser’sGuide (ForteDeveloper 7), Revision A edn. (May 2002)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • David J. Barnes
    • 1
  • Tim R. Hopkins
    • 1
  1. 1.Computing LaboratoryUniversity of KentCanterbury, KentUK

Personalised recommendations