Project

General

Profile

Actions
Copy link

action #166376

closed

[qe-core] Analyze Firefox Upstream Tests for Suitability

Added by fgerling 8 months ago. Updated 24 days ago.

Status:
Rejected
Priority:
Normal
Assignee:
dzedro
Category:
Spike/Research
Target version:
QA (public) - QE-Core: Ready
Start date:
2024-09-05
Due date:
% Done:

0%

Estimated time:
Difficulty:
Sprint:
QE-Core: September Sprint 24 (Sep 05 - Oct 03)

Description

Conduct an analysis of the Firefox upstream tests to determine their suitability for our needs.

Relevant areas should be discussed, but I would suggest something along those lines:
Check how relevant there are for us, if they cover what we already test, how much effort is to be expected to integrate them in openQA, how maintainable they are.

Expected Outcome: A report documenting the findings of the analysis, with recommendations on whether to integrate these tests or even replace existing ones.

Notes

Actions
Copy link
 #1

Updated by szarate 8 months ago

  • Sprint set to QE-Core: September Sprint 24 (Sep 05 - Oct 03)
  • Project changed from QA (public) to openQA Tests (public)
  • Category set to Spike/Research
  • Target version set to QE-Core: Ready
Actions
Copy link
 #2

Updated by szarate 8 months ago

  • Status changed from New to Workable
Actions
Copy link
 #3

Updated by szarate 8 months ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by szarate 8 months ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by dzedro 7 months ago

  • Status changed from Workable to In Progress
  • Assignee set to dzedro
Actions
Copy link
 #6

Updated by mgrifalconi 2 months ago

Hey @dzedro just cheking if you are you working on it or not :)

Actions
Copy link
 #7

Updated by dzedro 2 months ago

No, I'm working on other more important stuff.
I wanted to ask maintainer, what can be done.
I guess the testsuite is part of firefox, and you have to compile everything.
No idea if it's possible to somehow separate it.

Actions
Copy link
 #8

Updated by dzedro 24 days ago

  • Status changed from In Progress to Rejected

I got reply from Martin.
TL;DR
Upstream tests were never used, there are multiple reasons.
FF is a beast, this tests would be build with firefox and build time without tests is huge, with tests it would at least double.
IMO it's not worth the effort, we use upstream FF with some SUSE branding.
Tests we have are more than enough.

Actions
Copy link

Also available in: Atom PDF