Bug 8650

Summary: RRS: track ptest-enabled and potentially ptest-enabled status
Product: [Yocto Project Subprojects] Recipe Reporting System (RRS) Reporter: Paul Eggleton <bluelightning>
Component: Recipe Reporting System (RRS)Assignee: Unassigned <unassigned>
Status: NEW --- QA Contact: yeoh ee peng <ee.peng.yeoh>
Severity: enhancement    
Priority: Medium CC: belen.barros.pena, jose.perez.carranza, juan.m.cruz.alcaraz, leonardo.sandoval.gonzalez, richard.purdie, sgw, tim.orling
Version: unspecified   
Target Milestone: 6.99   
Hardware: x86   
OS: Multiple   
Whiteboard: GUI design available
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Bug Depends on: 9746    
Bug Blocks:    
Attachments:
Description Flags
Design - Track ptest-enabled status none

Description Paul Eggleton 2015-11-05 12:24:20 UTC 
Add functionality to the recipe reporting system to track:

1) Whether ptest is enabled for the recipe. This is fairly easy if you piggy-back on the recently added "inherits" code in the layer index master branch

2) Whether ptest could be enabled for the recipe, i.e. the upstream project provides a test suite. I think this is going to need to be settable somewhere in the UI by the maintainer, though for some software we could perhaps detect it in an automated way by looking for certain known things in the source tree (Makefile has a "check" target perhaps?).
Comment 1 Belen Barros Pena 2015-12-11 13:12:40 UTC 
If by the UI you mean the GUI, I had a brief chat with Aníbal, who mentioned the rrs is not currently able to provide any data manipulation options via the web interface. So, apparently, this bit: 

"I think this is going to need to be settable somewhere in the UI by the maintainer"

is currently not possible. We can either do just the "automated way" for the time being, or go all the way and provide a mechanism to set this in the UI as well. Note that this might involve introducing user authentication in the rrs, otherwise we have no way to establish who the maintainer is. 

Just let me know what you'd like to do and I'll design accordingly.

Thanks!
Comment 2 Aníbal Limón 2015-12-11 16:21:25 UTC 
(In reply to comment #0)
> Add functionality to the recipe reporting system to track:
> 
> 1) Whether ptest is enabled for the recipe. This is fairly easy if you
> piggy-back on the recently added "inherits" code in the layer index master
> branch
> 
> 2) Whether ptest could be enabled for the recipe, i.e. the upstream project
> provides a test suite. I think this is going to need to be settable
> somewhere in the UI by the maintainer, though for some software we could
> perhaps detect it in an automated way by looking for certain known things in
> the source tree (Makefile has a "check" target perhaps?).

Hi Paul as Belen said currently the RRS doesn't not support user/maintainer interaction (i added an umbrella bug #8794) for the 2) now i can implement some logic for detect if the recipe can suppport ptest. 

For now we can add if a recipe can support ptest with something that said automatic detected when the user support is available this should change to manually added.

Comments?
Comment 3 Stephen K Jolley 2015-12-21 17:20:22 UTC 
Answer given.
Comment 4 Belen Barros Pena 2015-12-23 11:39:57 UTC 
Created attachment 2910 [details]
Design - Track ptest-enabled status
Comment 5 Randy MacLeod 2023-10-24 14:24:23 UTC 
Bulk move from 4.99 or 0.00 to 5.99
Comment 6 Tim Orling 2026-02-12 16:24:46 UTC 
Still valid. Moving to 6.99