20,741
edits
Software testing: Difference between revisions
Jump to navigation
Jump to search
m
→References: https://sourceforge.net/p/flightgear/mailman/message/36985403/
(Minor copy editing; Slight change in disposition; +cat: Core development) |
m (→References: https://sourceforge.net/p/flightgear/mailman/message/36985403/) |
||
| Line 29: | Line 29: | ||
* Low code quality and standards. This is related to the learning point. As long as a test compiles on all OSes without warning, it passes, and Valgrind gives you an ok, it is good enough. You dont need to be a C++ expert to dive into this shallow end of the pool. | * Low code quality and standards. This is related to the learning point. As long as a test compiles on all OSes without warning, it passes, and Valgrind gives you an ok, it is good enough. You dont need to be a C++ expert to dive into this shallow end of the pool. | ||
== Bootstrapping new tests == | |||
To start diving strait into the test suite code, firstly copy what has | |||
been done in this commit: https://sourceforge.net/u/edauvergne/flightgear/ci/8474df | |||
Just modify all names for a JSBSim test (or any other test fixture you | |||
want to code). You should then be able to compile and check that your | |||
new testDummy() test passes as expected. You can then slowly build up | |||
from this basic infrastructure as you learn the fgfs internals, c++, | |||
and git skills required for implementing your test on your fork's new | |||
development branch :) | |||
== References == | == References == | ||