Bug 13002 - Create a set of tests to run after upgrading patchtest
Summary: Create a set of tests to run after upgrading patchtest
Status: ACCEPTED
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchtest (show other bugs)
Version: 2.7
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 6.2
Assignee: Trevor Gamblin
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-11-09 13:38 UTC by Michael Halstead
Modified: 2026-10-29 15:06 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Halstead 2018-11-09 13:38:13 UTC 
After making changes to patchtest itself we need a plan to ensure all functionality is still in place.

Can it poll patchwork?
Can it update patchwork?
Is the guest machine running with the needed permissions?
Are all expected tests running?

A script or even a simple checklist to go over after making changes would be very helpful.
Comment 1 Michael Halstead 2018-11-09 15:01:02 UTC 
I'd also like to rerun the test suite on a known good and known bad patch after making changes. I'd like advice on which sort of patches to run these test with so we don't annoy anyone with unwanted test e-mail.
Comment 2 Randy MacLeod 2023-10-24 14:24:49 UTC 
Bulk move from 4.99 or 0.00 to 5.99
Comment 3 Trevor Gamblin 2024-10-03 15:07:46 UTC 
Moving this to 5.3 for now, as it's still relevant but probably needs larger-scale changes to the current version of patchtest to be addressed.