Bug 115869 - Autobibisecting import/export regressions
Summary: Autobibisecting import/export regressions
Status: NEW
Alias: None
Product: QA Tools
Classification: Unclassified
Component: General (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-20 05:14 UTC by Aron Budea
Modified: 2023-09-06 06:01 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

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 Aron Budea 2018-02-20 05:14:40 UTC 
Let me get this written down before I forget about the details.

The idea is to enhance office-interoperability-tools [1] (or create a separate tool) to do the heavy lifting when bibisecting file format import/export regressions resulting in different layouts. In this case the point is not to look for regressions, but to automatically bibisect an identified one.

Scenario:
- the regression is that the test document looks different after opening, or opening-saving-reopening (should be able to handle both cases),
- the version (required bibisect repo) has been identified.

Optionally a good or bad version of the PDF export can be specified, but technically it should be able to generate one based on latest(master HEAD)/oldest state, and compare for differences during bibisection.
If a difference, and the responsible commit has been identified, it should be possible to continue looking for the next difference in the reduced range (in case there were multiple changes that affected the sample in the original range).

[1] https://github.com/x1sc0/office-interoperability-tools
Comment 1 alisha oberoi 2023-09-06 06:01:58 UTC Comment hidden (spam)