It doesn't look bad. I only used the standard "unitest" framework from python.
It doesn't only look like a good way to keep the API binding/contract checked, but to do pcbnew unit testing from python-land. http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/revision/4336 + http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/revision/4335 just after building pcbnew, it can be tested this way (from pcbnew build directory): build/pcbnew$ make qa running qa test_pcb_load (test_001_pcb_load.TestPCBLoad) ... ok test_pcb_module_references (test_001_pcb_load.TestPCBLoad) ... ok test_pcb_modules (test_001_pcb_load.TestPCBLoad) ... ok test_pcb_netcount (test_001_pcb_load.TestPCBLoad) ... ok test_pcb_track_count (test_001_pcb_load.TestPCBLoad) ... ok test_assert_equal (test_000_qa_works.TestQAWorks) ... ok test_assert_true (test_000_qa_works.TestQAWorks) ... ok ---------------------------------------------------------------------- Ran 7 tests in 0.318s OK Built target qa Miguel Angel Ajo Pelayo http://www.nbee.es +34 636 52 25 69 skype: ajoajoajo
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
