On Thu, 2023-04-20 at 09:27 +0200, Frederic Martinsons wrote: > Hello, > > I would like to build and ship tests for recipes which uses cargo and > in the process, three questions arose (maybe more when I will > progress). > I would like to have your opinions on them. > > 1) should we ship cargo-native in ptest images or should we just > build and ship test binaries alone ?
ptests run in target images so they'd depend on "cargo" and cargo- native wouldn't be appropriate. > 2) should we place the cargo ptest specifics in a dedicated class > (e.g ptest-cargo.bbclass, like already existing ptest-gnome or ptest- > perl) or put this in cargo.bbclass itself ? If ptests for cargo all follow a common format and a class can enable them for a large set of recipes, a class is appropriate. If would only be in cargo.bbclass itself if all cargo recipes had standard ptests. > 3) should we embed all kind of tests (unit, integration and doc > tests, see > https://doc.rust-lang.org/book/ch11-03-test-organization.html) or > just the unit tests ? I don't know about the rust specific details but unit and integration tests are both appropriate. I've no strong opinion on doc tests. They're probably fine if they don't add large dependency chains and run quickly. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#180245): https://lists.openembedded.org/g/openembedded-core/message/180245 Mute This Topic: https://lists.openembedded.org/mt/98384286/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
