11206 2017-03-21 23:36:09 +0000 QA: Validate Reference kit supports integrity protection 2017-05-23 20:18:45 +0000 1 1 10 QA/Testing IoT Reference OS Kit Testing intel-iot-refkit-automated-build-testing 2.3 x86 Multiple RESOLVED FIXED Medium enhancement 2.3 M4 11072 1 jair.de.jesus.gonzalez.plascencia francisco.j.pedraza.gonzalez patrick.ohly jair.de.jesus.gonzalez.plascencia --- --- No (bug/feature does not impact docs) oldest_to_newest 71552 0 jair.de.jesus.gonzalez.plascencia 2017-03-21 23:36:09 +0000 Add a test suite to validate Reference kit supports integrity protection using dm-verity (currently limited to the installer image). 71958 1 patrick.ohly 2017-03-31 10:28:42 +0000 We need two kinds of tests: a) enough tests to merge the feature and b) additional feature that can be added later as time permits (open ended). We agreed to treat this QA work items as a), i.e. they block the feature completion. I don't know how QA wants to track part b). Filing issues is not particularly useful because of the open scope. At this point, https://github.com/intel/intel-iot-refkit/pull/97 has one test which covers this functionality, which I consider good enough to close this issue once the PR is merged. 72105 2 francisco.j.pedraza.gonzalez 2017-04-05 19:40:56 +0000 (In reply to comment #1) > We need two kinds of tests: a) enough tests to merge the feature and b) > additional feature that can be added later as time permits (open ended). > > We agreed to treat this QA work items as a), i.e. they block the feature > completion. > > I don't know how QA wants to track part b). Filing issues is not > particularly useful because of the open scope. > > At this point, https://github.com/intel/intel-iot-refkit/pull/97 has one > test which covers this functionality, which I consider good enough to close > this issue once the PR is merged. Hi Patrick, This also can be closed once the patch got acceptance right? 72569 3 jair.de.jesus.gonzalez.plascencia 2017-04-17 21:36:24 +0000 After an agreement with the Refkit team, the progress on the minimal required sanity tests to release a feature will be tracked on the same bug issue used to track the feature's development. Analogous QA bugs like this one may be created if required, and will be used to track the development of more extensive test cases. According to this, the dependence will be inverted in relation to the feature bug. 73454 4 francisco.j.pedraza.gonzalez 2017-05-23 20:18:45 +0000 Test Cases implemented at: "~/meta-refkit/lib/oeqa/selftest/secureboot.py"