Hi Trevor,
It's great that we can continue discussing CD releases for testing projects. In my mind, there are mainly two kinds of deliverables for a specific testing project: 1) test framework; 2) test cases. As to the continuous delivery of testing project, I tent to include both of the deliverables. Validation of a test framework consists of validations of the abilities to do unit test (and maybe style check), to adapt to different community installers/scenarios, to be compatible to at least 2 OPNFV releases, etc. Validation of test cases requires validating its integrity, successfully running on latest releases, clear and concrete testing scopes/purpose, etc. So, I guess we could have 2 delivery gates for the testing project: 1) test framework ready; 2) test cases ready. Just some preliminary thoughts, please comments. As a side notes, Yardstick and Bottlenecks are working on transforming themselves into services on cloud native CD pipeline in Clover project. Maybe we could discuss more towards that direction. Best, Gabriel -----Original Message----- From: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] On Behalf Of Trevor Bramwell Sent: Wednesday, August 08, 2018 7:13 AM To: opnfv-tech-discuss@lists.opnfv.org Subject: [opnfv-tech-discuss] Continuously Releasing Test Projects Hi all, Today me and Mark Beirel started a discussion during the release call[1] that I wanted to continue here regarding what the process could look like for releasing testing projects or testing tools in a continuous manner. (NFVBench, StorPerf, Yardstick, Functest, Bottlenecks, Dovetail, etc) This could also be seen as a continuation of the discussion we started at the Plugfest in France regarding gating in the CD process[2], but aimed specifically at the testing tools. The question I'm hoping we can collectively come to answer is: What does a continuous release process look like for OPNFV test tools? As I don't work on a testing project myself, obviously I'm not the best one to answer this question, so instead of imposing my views on a process, I'd rather hear the thoughts from our community. I think by laying out some of the issues projects have with the current release process, and listing what a successful release process might look like to you will definitely help move this discussion in the right direction. Regards, Trevor Bramwell [1] http://meetbot.opnfv.org/meetings/opnfv-release/2018/opnfv-release.2018-08-07-14.01.log.html [2] https://etherpad.opnfv.org/p/minum_test_sets_gating_cd -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21731): https://lists.opnfv.org/g/opnfv-tech-discuss/message/21731 Mute This Topic: https://lists.opnfv.org/mt/24225095/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
