Someone writes a script to automate the process. Have a list of apps that we want to be sure are tested and working. The script will download web2py testing, copy the apps to the downloaded version, fire a process fork to start that web2py, use urllib or httplib to navigate to each of the apps pages to verify that things are working. If a response code of 500 is ever received then go get the error ticket and store it somewhere central including which app it came from.
-- Thadeus On Sat, Oct 30, 2010 at 9:25 AM, Luther Goh Lu Feng <elf...@yahoo.com>wrote: > > > On Oct 30, 7:05 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > Normally it goes to the nightly build, perhaps not exactly the latest > > but something very close. The bug in question has been there for about > > one week. The problem is that nobody tests the nightly build. > > > > Massimo > > > > > I would love to have a way to test non stable builds easily with my > existing apps. How does one do so besides downloading the trunk/ > nightly build, and then exporting the apps from stable web2py and then > import to the trunk/nightly web2py? >
