Advanced FreeCAD test system: Difference between revisions
No edit summary |
|||
| Line 4: | Line 4: | ||
FreeCAD as an CAE application has a high level of complexity, both in its source code and also in its user interaction. To ensure a certain level of quality automatic testing is essentail. However, as an open source application with spare time coders only this part of the project has not seen very much attention. One of the major reasons is the low-level handling required to write test cases. All actions to trigger, every result fetching and every single comparison needs to be hand coded. This makes it cumbersome to provide a test for every created functionality and patially impossible to do so if deep document comparisons are needed. For example he Part an PartDesign workbench: An automated test for document objects require the resulting topology shape to be analysed. This is an tremendous part and cannot be handled on a per test basis. |
FreeCAD as an CAE application has a high level of complexity, both in its source code and also in its user interaction. To ensure a certain level of quality automatic testing is essentail. However, as an open source application with spare time coders only this part of the project has not seen very much attention. One of the major reasons is the low-level handling required to write test cases. All actions to trigger, every result fetching and every single comparison needs to be hand coded. This makes it cumbersome to provide a test for every created functionality and patially impossible to do so if deep document comparisons are needed. For example he Part an PartDesign workbench: An automated test for document objects require the resulting topology shape to be analysed. This is an tremendous part and cannot be handled on a per test basis. |
||
This project aims at reducing the work required to write |
This project aims at reducing the work required to write meaningful tests. This should be accomplished by providing a infrastructure for result file storage and special "comparators" which compare the stored result files with the test result for equality. |
||
==Details== |
==Details== |
||
Revision as of 09:00, 22 January 2016
This page is dedicated to the Google Summer of Code project regarding the enhancement of FreeCADs test system.
Outline
FreeCAD as an CAE application has a high level of complexity, both in its source code and also in its user interaction. To ensure a certain level of quality automatic testing is essentail. However, as an open source application with spare time coders only this part of the project has not seen very much attention. One of the major reasons is the low-level handling required to write test cases. All actions to trigger, every result fetching and every single comparison needs to be hand coded. This makes it cumbersome to provide a test for every created functionality and patially impossible to do so if deep document comparisons are needed. For example he Part an PartDesign workbench: An automated test for document objects require the resulting topology shape to be analysed. This is an tremendous part and cannot be handled on a per test basis.
This project aims at reducing the work required to write meaningful tests. This should be accomplished by providing a infrastructure for result file storage and special "comparators" which compare the stored result files with the test result for equality.