Automatic testing of solvers using PyFoam - If your ... - OpenFOAMWiki

More documents

Recommendations

Info

Introduction The tools: pyFoam in 3 minutes The tools: swak4Foam - 3 more minutes Case study: Taylor-Green vortex Case study: Pitz-Daily CTest Conclusion This presentation Other information The importance of software-testing From Wikipedia: Software testing can be stated as the process of validating and verifying that a software program/application/product: 1 meets the requirements that guided its design and development 2 works as expected 3 can be implemented with the same characteristics 4 satisfies the needs of stakeholders Bernhard F.W. Gschaider Automatic testing of solvers using PyFoam 6/164
Introduction The tools: pyFoam in 3 minutes The tools: swak4Foam - 3 more minutes Case study: Taylor-Green vortex Case study: Pitz-Daily CTest Conclusion Scopes of testing This presentation Other information Unit testing Testing single components • for OpenFOAM this would involve writing tests for classes like List to fvPatchField . . . • hard to do after the main development has happened but a valuable tool during development Integration testing Testing the correct interaction of the components • This is the level we’ll be working on: seeing how it all comes together in a single solver System testing Test the integrated system to see that it meets the requirements • In our case the difference to integration testing is not completely clear System integration testing Test interaction with third-party software in the deployment environment • This has to do by every organization individually Bernhard F.W. Gschaider Automatic testing of solvers using PyFoam 7/164
Page 1 and 2: Introduction The tools: pyFoam in 3
Page 3 and 4: Outline Introduction The tools: pyF
Page 5: Introduction The tools: pyFoam in 3
Page 9 and 10: Warning Introduction The tools: pyF
Page 23 and 24: Running Introduction The tools: pyF
Page 25 and 26: Plotting Introduction The tools: py
Page 57 and 58:
Introduction The tools: pyFoam in 3
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
The runInfo Introduction The tools:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Comparisons Introduction The tools:
Page 103 and 104:
Outline Introduction The tools: pyF
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
show all

Automatic testing of solvers using PyFoam - If your ... - OpenFOAMWiki

Create successful ePaper yourself

Delete template?

Save as template?