Bug 10317 - oeqa tests are incompatible with python's unittest runner
Summary: oeqa tests are incompatible with python's unittest runner
Status: RESOLVED WONTFIX
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 M3
Assignee: Mariano Lopez
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: oeqa2
  Show dependency tree
 
Reported: 2016-09-22 01:00 UTC by Benjamin Esquivel
Modified: 2017-03-28 21:48 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Esquivel 2016-09-22 01:00:31 UTC 
oeqa tests are based in unittest yet they are incompatible for running via unittest's runner.

The purpose of this bug is to investigate if the base test class can be adapted for running both via plain unittest and oe-selftest.

Future enabling of other runners, i.e. pytest, benefit from this compatibility check.
Comment 1 Leonardo Sandoval Gonzalez 2016-12-21 21:35:49 UTC 
M1 missed. Moved to M2.
Comment 2 Mariano Lopez 2017-03-28 21:48:55 UTC 
After the migration of runtime, sdk, and esdk frameworks we found that in order to use decorator as the way we are doing right now (execute decorator code when discovering the tests) it is not possible to use vanilla unittest.

Also, the cases needs to get custom arguments in their init method, making this more complicated.

Now is possible to discover test using vanilla unittest but it is not possible to execute them.