Hi Andrew, A couple of questions?
Firstly, about unit testing aka make test. This is the salient passage in your guide: "foo_message_v2 is tested in "make test" to the same extent as the foo_message" IMHO "to the same extent" implies everywhere v1 is used v2 should now be used in its place. One would hope that in most cases a simple find and replace through all test cases would do the job. However, once one has created such a fork and verified (presumably through some objective measure like lcov) that it is the same extent of coverage, what becomes of it? V1 and V2 APIs must co-exist for some time, so how do we continue to run the v1 original tests and the v2 fork? Given that between any two releases multi APIs may go through a version upgrade, there will be many such forks to manage. Additionally, are we also going to test all combinations of messages and their versions, e.g. foo_v2 with bar_v2. Secondly, what's the process for determining the initial categorization of existing APIs? /neale tpyed by my fat tumhbs
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16752): https://lists.fd.io/g/vpp-dev/message/16752 Mute This Topic: https://lists.fd.io/mt/74956323/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
