Software Testing Incompressible Navies-Stokes Plan

Software Testing Reference Documents

In addition to the Chombo design document [CGL+00] and the in viscid algorithm described in [MC00], we will also refer to the \Incompressible Navies-Stokes Software Design" and Incompressible Navies-Stokes Requirements" documents.

Software Testing Level

In general, most of computer software testing outlined in this text file will be component software testing. System-level testing will also be carried out on the entire AMRINS code. It is expectable that integrating software testing is not necessary at this time, so of small size of design team.

Planned Testing

In section, we outline the testing planned for AMRINS code, broke down by Functional algorithm unit. All software testing program code is written in C++.

Software testing AMRINS system regression

Ensuring that Chombo library changes, errors and related code changes do not cause undesirable changes in the code results, a regression test system will be used AMRINS. AMRINS The code runs with the reference inputs (a detailed description of the problem of reference and entries can be found in the reference documents of performance), and two diagnostic quantities reported at the end of the race (the total number updated cell and the integral of the kinetic energy in the problem domain. Changeling these diagnostic quantities indicates the changes that need to be investigated. The total number of cells in the race update is sensitive to changes in the hierarchy of AMR network during the race, while the kinetic energy integral is sensitive to changes in the solution itself.

Bug Tracking

The AMRINS developers (and the Chombo developers) use the ttpro system for bug tracking. When a bug or unexpected behavior in the code is identi¯ed, a description is entered in the ANAG ttpro database. As the bug is investigated and ¯xed, the description is updated and expanded. Once a bug has been ¯xed, the bug report is closed" in ttpro, but it remains in the database for future reference if needed. Also, after a bug ¯x, the regression test (Test # 7) is re-run to ensure that no unanticipated e have been added.