Bug 10599 - oeqa: migrate selftest's test to use the new framework
Summary: oeqa: migrate selftest's test to use the new framework
Status: RESOLVED FIXED
Alias: None
Product: Build Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 2.4 M2
Assignee: Leonardo Sandoval Gonzalez
QA Contact:
URL:
Whiteboard:
: 9931 10689 (view as bug list)
Depends on: 10689
Blocks: oeqa2
  Show dependency tree
 
Reported: 2016-11-03 22:45 UTC by Mariano Lopez
Modified: 2017-12-06 17:13 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mariano Lopez 2016-11-03 22:45:40 UTC
As part of the refactor of oeqa, selftest needs to migrate all its test to use the new framework
Comment 1 Mariano Lopez 2016-11-03 22:47:16 UTC
*** Bug 9931 has been marked as a duplicate of this bug. ***
Comment 2 Benjamin Esquivel 2016-11-04 18:17:40 UTC
Mariano, I understand that this is some work that might not be complete in M1 and that conflicts with blocking bug 10230 which is targeted M1. If the rest of the bug 10230 will be delivered in M1 but selftest perhaps you could notify there that selftest will be worked in this bug instead and not make it dependent.
Comment 3 Mariano Lopez 2016-11-16 19:45:33 UTC
A good idea would be to split this bug for every OE framework currently used (runtime, selftest, sdk). So we can have a better tracking and better milestones for every framework.
Comment 4 Benjamin Esquivel 2016-11-16 22:05:24 UTC
Agreed, thanks for splitting this work.
Comment 5 Leonardo Sandoval Gonzalez 2017-06-05 18:53:33 UTC
The series [1] including the migration has been sent to the mailing list.

[1] http://lists.openembedded.org/pipermail/openembedded-core/2017-May/137195.html
Comment 6 Aníbal Limón 2017-06-07 22:01:24 UTC
*** Bug 10689 has been marked as a duplicate of this bug. ***