20,741
edits
Software testing: Difference between revisions
Jump to navigation
Jump to search
m
→Why write unit tests?: https://sourceforge.net/p/flightgear/mailman/message/36951247/
m (→Why write unit tests?: https://sourceforge.net/p/flightgear/mailman/message/36951247/) |
|||
| Line 55: | Line 55: | ||
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> | 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> | ||
It'd be better jumping into a specific area of interest to you, and submitting merge-requests. That would naturally trigger some C++ feedback when reviewed but we aren’t looking for perfection here, more to increase the overall pool of knowledge of what best-practice looks like, even if a given commit is less than perfect. | |||
I,e It’s more important to have 10 or 20 people actively contributing correct-and-reasonable code than three people contributing absolutely perfect, micro-optimised C++. <ref>https://sourceforge.net/p/flightgear/mailman/message/36951247/</ref> | |||
=== Benefits of unit testing === | === Benefits of unit testing === | ||