20,741
edits
Software testing: Difference between revisions
Jump to navigation
Jump to search
→Nasal scripting (comments)
| Line 140: | Line 140: | ||
identified in the old [[Nasal Unit Testing Framework]] wiki article and the discussions it points to | identified in the old [[Nasal Unit Testing Framework]] wiki article and the discussions it points to | ||
and provide the full framework required.<ref>https://sourceforge.net/p/flightgear/mailman/message/36990615/</ref> | and provide the full framework required.<ref>https://sourceforge.net/p/flightgear/mailman/message/36990615/</ref> | ||
have some very simple tests running now for the route-manager, which rely on Nasal. we're skipping a few of the bigger Nasal modules (local-weather, jetways) and have a few lingering issues in some other modules but the basic concept is working. | |||
A very interesting further step, which you might wish to discuss with Edward, is writing test checks *in* Nasal, since this could be quite a fast way to test some area of the code. There’s several ways that could work, and I don’t know if Edward has always planned something around this, so I won’t preempt that conversation. | |||
<ref>https://sourceforge.net/p/flightgear/mailman/message/36764781/</ref> | |||
we have route-manager tests which validate route_manager.nas is working correctly, and we have Canavs tests ({{fg src file|path=test_suite/simgear_tests/canvas|}}) which poke the Nasal API. <ref>https://sourceforge.net/p/flightgear/mailman/message/36991200/</ref> | we have route-manager tests which validate route_manager.nas is working correctly, and we have Canavs tests ({{fg src file|path=test_suite/simgear_tests/canvas|}}) which poke the Nasal API. <ref>https://sourceforge.net/p/flightgear/mailman/message/36991200/</ref> | ||