Closed Bug 26499 Opened 25 years ago Closed 15 years ago

task: CVR tool for QA Windows automation

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect, P4)

x86
Windows NT
defect

Tracking

(Not tracked)

RESOLVED INVALID
Future

People

(Reporter: depman1, Assigned: curt)

Details

Client Version Registry tool for Windows needed for automation. Using CVR API. Here what QA needs the tool to do: 1) The tool should be command line accessible (to use with Perl scripts). 2) We need to find the starting point in the registry. If several versions of Communicator have been used, which one do we access (for automation) to find a given package? One thing to keep in mind with this: the /netscape/Communicator # node will be changed to "Mozilla" (bug 23306). 3) For a given package and node, we need callback values for RefCount, Version string, and the pathway where installation occurred. Then, we can use these values for CVR validation.
changed QA contact to depstein.
Assignee: cathleen → ssu
QA Contact: jimmylee → depstein
*** Bug 26500 has been marked as a duplicate of this bug. ***
wont be able to get to this till after beta. seting milestone to M17 for now.
Target Milestone: M17
Status: NEW → ASSIGNED
Target Milestone: M17 → M30
Changing fictional "M30" to reality
Target Milestone: M30 → Future
Priority: P3 → P4
QA Contact: depstein → jimmylee
Updating QA Contact.
over to Curt.
Assignee: ssu → curt
Status: ASSIGNED → NEW
I received this info from Jimmy: This is no longer a priority. We no longer used the Version Registry the way we had once upon a time ago. We don't need this one anymore. Maybe some day we will, but that will only be due to a major design change.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.