System Tests

[smiths]

System Tests

[EmilSoleymani]

Appendix F of the settlements book gives a few examples of uses of the VDISPL program, including their VDIN.dat and VDOU.dat files. Recreating these would be a good start. Furthermore, we could come up with some more inputs ourselves if we see certain options weren't covered in the given test cases, and run them through the original FORTRAN code to get our expected results

[smiths]

Excellent! Yes, Appendix F sounds great. What we want to have is an argument for completeness. If possible, we want to cover all combinations of the different input options.

I haven't created an issue for requirements yet, but once we document the requirements more system tests will become apparent. I doubt the Settlement book explicitly says the range of expected inputs, but there is an implicit range. The software is written for practical geotechnical problems. This puts limitations on the inputs that we will want to make as explicit as we can. These limitations will give us bounds for additional system tests.

[EmilSoleymani]

I have began with some system tests. I first copied down all the example input files from the textbook (there were 4 examples, 1 of which being the input file we already use). Already from trying to parse the first one I found a little mistake in the InputParser module.

[smiths]

Great! We should have an artifact in our repo that contains this information. Please create a LaTeX document with the title "Verification and Validation Plan." You don't need to worry about organizing it to begin with, just put your system test information in there. (You shouldn't actually copy the contents of the files. You can just put hyperlinks to where they are located.)

Glad to hear that working with the files has helped you debug your code.

[EmilSoleymani]

Added document VerifcationAndValidationPlan.pdf in this commit.