Bug 12777 - oeqa: test suite need to be categorized
Summary: oeqa: test suite need to be categorized
Status: RESOLVED NOTABUG
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: unspecified
Hardware: All Multiple
: Undecided enhancement
Target Milestone: ---
Assignee: Apoorv
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-06-08 06:49 UTC by Lei Yang
Modified: 2018-06-14 14:38 UTC (History)
6 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lei Yang 2018-06-08 06:49:57 UTC
we have kernel,userspace, toolchian tests in oeqa currently, and all of those tests are under the same directory right now, it's kind hard to know which one is for kernel, which one is for toolchain,etc. 

Imaging you're a kernel developer, you did a big change to the kernel code, you want to know the overall impact to the different kernel sub-system, you might want to run all of the exsisting kernel tests without running other tests like toolchain or userspace.  

Imaging you want to know the kernel test report after applying something like meltdow/spectre patches.

how could we do that? 

Lei
Comment 1 Richard Purdie 2018-06-14 14:38:43 UTC
This is a good question but doesn't really lend itself to a bugzilla entry. This is something which should be discussed on the mailing list and then once an approach is agreed we can have a bugzilla entry for it.

The code is structured where similar tests are currently co-located. Rather than restructuring the code by area we may just want to add "tags" to test or some other similar approach so particular groups can be created and run.

Closing as NOTABUG so mailing list discussion can happen and an approach can be agreed.