Project

General

Profile

Support #6862

build conversion regression testing tooling

Added by Greg Shah over 1 year ago. Updated 10 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:

History

#2 Updated by Roger Borrello 10 months ago

Some apps build the archive.incremental target of a project. This could also be extended to have a archive.conv-regression target, which would collect all the things pertinent artifacts. The zip filename itself contains the branch/revision used to perform the conversion (or perhaps the p2j.jar used to convert could be stored in it, or version.properties if it is setup), so that you would know what version of FWD was used. FWD could contain the conv-regression script to compare:
  1. the artifacts in the project it is linked into with path to the baseline conversion zip file, or
  2. 2 zips containing the artifacts to compare

I'm not a fan of how we hook into zip files being unzipped prior to conversion. I would think that a branch should just have the revisions checked into it.

Also available in: Atom PDF