Bug 13008

Summary: toaster testing
Product: [QA/Testing] Runtime Testing Reporter: Armin Kuster <akuster>
Component: generalAssignee: David Reyna <david.reyna>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Medium+ CC: david.reyna, randy.macleod, richard.purdie
Version: 2.7   
Target Milestone: 4.3 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Armin Kuster 2018-11-11 19:00:07 UTC 
toaster - David Reyna is looking into selenium automation but likely
won't be tested without automation

Bug 9132 has some previous discussions.
Comment 1 David Reyna 2018-11-13 06:15:00 UTC 
This was also discussed under Bug 12972.

My current strategy is to get the Selenium test under Travis working again, and then go from there.
Comment 2 David Reyna 2018-11-15 15:52:14 UTC 
Also, see about adding the test to auto-builder since it is documented and in-house.
Comment 3 David Reyna 2023-06-22 09:47:58 UTC 
I plan to leverage as a fundamental command line unit test to install and run Toaster against "quilt-native". 

This unit test easy to wrap with a trivial ptest, but still covers the most vulnerable and shift-able part of the Toaster interface, that being its basic connection to bitbake and the ability to execute build commands.

Getting the Selinium test suite running is a secondary task, and will require more effort.
Comment 4 David Reyna 2023-11-16 08:59:40 UTC 
This case is replaced by full testing support via STF effort.