It is reasonable to suggest a universal test app that will assist in the quality assurance of web2py. But I wonder if this will always have 100% test coverage, given that bugs may appear even when writing test cases. This is still a good idea compared to not having a test suite.
However, I think I would have a greater sense of security if I am able to test the apps I have written against the nightly/trunk build. On Oct 31, 1:46 am, Thadeus Burgess <[email protected]> wrote: > Where should the list of apps come from? I think this is the biggest > question. > > -- > Thadeus > > On Sat, Oct 30, 2010 at 12:46 PM, Thadeus Burgess > <[email protected]>wrote: > > > > > > > > > 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 <[email protected]>wrote: > > >> On Oct 30, 7:05 am, mdipierro <[email protected]> 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?
