20,741
edits
Software testing: Difference between revisions
Jump to navigation
Jump to search
m
more pearls of wisdom
No edit summary |
m (more pearls of wisdom) |
||
| Line 4: | Line 4: | ||
a well tested piece of software will have a much lower bug count/load. An extensive test suite with unit tests, system/functional tests, GUI tests, installer tests, and other categories of tests can significantly help in this regard.<ref>https://sourceforge.net/p/flightgear/mailman/message/36977686/</ref> | a well tested piece of software will have a much lower bug count/load. An extensive test suite with unit tests, system/functional tests, GUI tests, installer tests, and other categories of tests can significantly help in this regard. | ||
The benefits of not just chasing clear "wins" are great: An awesome learning experience for new developers; the ability to catch latent, unreported bugs; making it easier to refactor current code by creating a safety net; making it easier for current developers to accept new contributions (when accompanied with passing tests); helping other test writers by contributing to the common test suite infrastructure; and being able to easily check for memory leaks or other issues via Valgrind. <ref>https://sourceforge.net/p/flightgear/mailman/message/36977686/</ref> | |||
| Line 25: | Line 28: | ||
* 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 don't 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 don't need to be a C++ expert to dive into this shallow end of the pool. | ||
So for new developers, just jump in and write any test! It does not need to catch a bug. Do whatever how ever you wish! Just dive in this shallow end and you'll see that the water is not cold <ref>https://sourceforge.net/p/flightgear/mailman/message/36977465/</ref> | So for new developers, just jump in and write any test! It does not need to catch a bug. Do whatever how ever you wish! Just dive in this shallow end and you'll see that the water is not cold | ||
writing a test as a safety net. You write the test to pass, make your changes, then make sure that the test still passes. Then you push both the test and core changes <ref>https://sourceforge.net/p/flightgear/mailman/message/36977465/</ref> | |||
== References == | == References == | ||
{{Appendix}} | {{Appendix}} | ||