| Summary: | oeqa tests are incompatible with python's unittest runner | ||
|---|---|---|---|
| Product: | [QA/Testing] Build Testing | Reporter: | Benjamin Esquivel <benjamin.esquivel> |
| Component: | general | Assignee: | Mariano Lopez <mariano.lopez> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | anibal.limon, leonardo.sandoval.gonzalez |
| Version: | 2.2 | ||
| Target Milestone: | 2.4 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
| Bug Depends on: | |||
| Bug Blocks: | 10230 | ||
|
Description
Benjamin Esquivel
2016-09-22 01:00:31 UTC
M1 missed. Moved to M2. 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. |