SoftwareTesting:SoftwareUpdateTesting: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
 
No edit summary
Line 24: Line 24:


--[[User:Davel|Davel]] 10:22, 24 Jan 2006 (PST)
--[[User:Davel|Davel]] 10:22, 24 Jan 2006 (PST)
== Testing The Update Process ==
One thing which I suspect is time-consuming is actually testing the generated updates against all the builds they are supposed to apply to. Can we produce an automated system which, for various values of "old build", downloads and silently installs the full build, and then installs the old build and patches it to see if the bits are exactly the same?
This tests the update mechanism and URLs, and the integrity and correctness of the updates.
Would this obviate the need for a human to do the same process? If so, if you have 40 localisations and 3 platforms and 3 older versions, it might save a heck of a lot of time!
--[[User:Gerv|Gerv]]
Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925

edits

Navigation menu