| Summary: | Run complete LTP Test, not just a subset | ||
|---|---|---|---|
| Product: | [QA/Testing] Runtime Testing | Reporter: | Saul Wold <sgw> |
| Component: | general | Assignee: | Apoorv <apoorv.sangal> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | akuster, jose.perez.carranza, libertad.gonzalez.de.la.cruz, randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 4.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Saul Wold
2017-10-17 14:42:01 UTC
I added a new layer meta-qa. it has the ability to run ltp as a hole We are going to drop LTP into a hole? That's not good ;-) Maybe if it's a black whole! So does that mean LTP moves out of oe-core into meta-qa? (In reply to comment #2) > We are going to drop LTP into a hole? That's not good ;-) Maybe if it's a > black whole! > > So does that mean LTP moves out of oe-core into meta-qa? no. Meta-qa is a testframe work that sits on top of pytest. I have included ltp and automount tests. I am covering this at OEDEM. It gives you system level test capabilities. its the "mvtest" topic for OEDEM (In reply to comment #2) > We are going to drop LTP into a hole? That's not good ;-) Maybe if it's a > black whole! > > So does that mean LTP moves out of oe-core into meta-qa? lol I have a runtime implementation of this nearly working. Mind if I take this? ltp testing is in oeqa runtime: https://git.openembedded.org/openembedded-core/commit/?id=1ec677549d490a29a7c713610db4a56be7b55e26 I think we can close this LTP test are running successfully in oeqa runtime. Hence closing this bug. |