Cppunit effort: Difference between revisions

Jump to navigation Jump to search
Line 28: Line 28:
== Challenges ==
== Challenges ==
The hardest one would be to set up and run only a small subset of subsystems and other infrastructure. But it is possible to write unit tests now. Writing a system/functional test is much more difficult but, with a bit of work, it should be possible.<ref>{{cite web
The hardest one would be to set up and run only a small subset of subsystems and other infrastructure. But it is possible to write unit tests now. Writing a system/functional test is much more difficult but, with a bit of work, it should be possible.<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/36281748/
  |title  =  <nowiki> Re: [Flightgear-devel] Questions about TestSuite </nowiki>
  |author =  <nowiki> Edward d'Auvergne </nowiki>
  |date  =  Apr 1st, 2018
  |added  =  Apr 1st, 2018
  |script_version = 0.36
  }}</ref>
== Roadmap ==
The idea is to make it possible to set up a single subsystem and all its dependencies in a few lines of test code. Then it should be easy to write a test. This is the dependency arrays, subsystem manager/factory fusion, and dynamic dependency resolution algorithm discussed in another thread. Edward is currently working on some ideas, he is also working on subsystem robustness testing for the test suite. This will make it much easier to work with isolated subsystems or sets of subsystems, as many subsystems are quite brittle and if you run them in a way unintended compared to how they are run in fgfs, you see segfaults all over the place.<ref>{{cite web
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/36281748/  
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/36281748/  
   |title  =  <nowiki> Re: [Flightgear-devel] Questions about TestSuite </nowiki>  
   |title  =  <nowiki> Re: [Flightgear-devel] Questions about TestSuite </nowiki>  

Navigation menu