> >>> Meson is a nice system in many aspects, but its support for tests is very > >>> limited. IIUC, it can only run a single binary and check the error codes. > >>> Most of our tests starts several daemons and performs several fairly > >>> complex > >>> operations and checks. I'm afraid that we will end up writing our own > >>> separate testing framework that will mimic autotest in order to be able to > >>> run our tests from meson. > >>> > >>> Did you think about this problem? Do you have a solution in mind? > >> > >> Thanks, we thought about it but I don't have a solution in mind at this > >> moment. > > PoC of the build process is fine and I had no doubts that it can be done. > I'd suggest to make a PoC for at least one unit test that we have (e.g. > "ofproto-dpif - MPLS handling with goto_table") or two tests to actually > figure out what we need to do with them. > Thanks! That makes sense.
Sergey is looking for two possible solutions: Avocado testing framework https://avocado-framework.readthedocs.io/en/90.0/quickstart/index.html or Unity test framework https://docs.unity3d.com/Packages/com.unity.test-framework@1.1/manual/index.html or any suggestions are welcome! Regards, William _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
