| Summary: | QA: devtool: extend oe-selftest testing for devtool upgrade | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Paul Eggleton <bluelightning> |
| Component: | devtools / tool chain | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | akuster, benjamin.esquivel, joshuagloe, juan.m.cruz.alcaraz, meta.mr.watcher, meta.watcher, richard.purdie |
| Version: | 5.99 | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Paul Eggleton
2015-11-11 15:36:13 UTC
For 2.1 the existing test was reworked to test upgrading a recipe pointing to a remote file and do more validation, plus an additional test to upgrade a recipe pointing to a git repository. We should look to see if there are any code paths not tested by these current tests and add tests to cover them. (In reply to comment #1) > For 2.1 the existing test was reworked to test upgrading a recipe pointing > to a remote file and do more validation, plus an additional test to upgrade > a recipe pointing to a git repository. We should look to see if there are > any code paths not tested by these current tests and add tests to cover them. Thanks for the update. I will review latest code and cover it with tests. currently the test for devtool upgrade are covering : - test_devtool_upgrade - test_devtool_upgrade_git - test_devtool_finish_upgrade_origlayer - test_devtool_finish_upgrade_otherlayer I is there any missing scenario that you identify that need to be tested ? I would like to see what the coverage of the upgrade module (scripts/lib/devtool/upgrade.py) is - Jose is that something you have easily available? (In reply to comment #4) > I would like to see what the coverage of the upgrade module > (scripts/lib/devtool/upgrade.py) is - Jose is that something you have easily > available? Unfortunately coverage option is not working on new framework (Bug 11582), I will do some tests on pyro and get back to you with the results. (In reply to comment #5) > (In reply to comment #4) > > I would like to see what the coverage of the upgrade module > > (scripts/lib/devtool/upgrade.py) is - Jose is that something you have easily > > available? > > Unfortunately coverage option is not working on new framework (Bug 11582), I > will do some tests on pyro and get back to you with the results. Unfortunately coverage option is not working on new framework (Bug 11582), I will do some tests on pyro and get back to you with the results. (In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > I would like to see what the coverage of the upgrade module > > > (scripts/lib/devtool/upgrade.py) is - Jose is that something you have easily > > > available? > > > > Unfortunately coverage option is not working on new framework (Bug 11582), I > > will do some tests on pyro and get back to you with the results. > > Unfortunately coverage option is not working on new framework (Bug 11582), I > will do some tests on pyro and get back to you with the results. A Bug 11786 was opened due coverage is not working properly on pyro, util that is resolved I will not be able to check what is the current coverage. Moved to 2.5 due resources constraint this still seems reasonable. devtool upgrade tests were added. The remaining question here was about code coverage. I don't believe we ever figured out correct tools for code coverage of that they are practical with the system so closing the original issue a resolved. If anyone identifies areas needing further testing we will add them. |