| Summary: | BlueZ 5 packs tests in a -tests package | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Cristian Iorga <cristian.iorga> |
| Component: | connectivity | Assignee: | Mihai Prica <mihai.prica> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher, sgw |
| Version: | 1.5 | ||
| Target Milestone: | 1.5 M5 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Cristian Iorga
2013-08-20 16:38:48 UTC
Be sure to split according to which of these things currently in tests that are tools vs what are actually tests. The bluez5 package is an autotools package and the installation can be checked using "make check". Besides these tests, it also provides a set of tools that can be used to test different functionality. I think the solution would be to create a -ptest package that runs the "make check" tests and package the test in another package -testtools. * Renamed package from tests to testtools for better clarity with commit: ea8494350fc8affa8c8a890e4ba1ba4b70a4ff56. Link: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ea8494350fc8affa8c8a890e4ba1ba4b70a4ff56 * Opened bug 5134 for adding ptest functionality to bluez5. Link: https://bugzilla.yoctoproject.org/show_bug.cgi?id=5134 |