Bug 13002

Summary:	Create a set of tests to run after upgrading patchtest
Product:	[Yocto Project Subprojects] Patchwork/Patchtest	Reporter:	Michael Halstead <mhalstead>
Component:	Patchtest	Assignee:	Trevor Gamblin <tgamblin>
Status:	ACCEPTED ---	QA Contact:
Severity:	enhancement
Priority:	Medium+	CC:	randy.macleod
Version:	2.7
Target Milestone:	6.2
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

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.