[web2py] Re: web2py 1.88.1 is OUT
i'm seeing appadmin break for my auth_user table with a picture. when i have a photo, update works fine. when the photo is not there, i get an error: KeyError: 'picture_blob' and from top to bottomw: gluon/restricted.py line 188 init/controllers/appadmin.py:update line 410 gluon/globals.py line 96 init/controllers/appadmin.py:update line 275 gluon/sqlhtml.py line 1105 in accepts value = fields[fieldname] matt On Nov 1, 10:56 am, Jonathan Lundell jlund...@pobox.com wrote: On Nov 1, 2010, at 10:52 AM, mdipierro wrote: I think this is a good idea. Me too. I rather expect, though, that it will be necessary, and perhaps desirable regardless, for this to be a suite of applications rather than a single app. On Nov 1, 7:24 am, Martín Mulone mulone.mar...@gmail.com wrote: I'm going to start an w2p-app, called app by an example or testing app. The idea is to have in one app some code for testing pourpose, that make for example insert,select,delete like the code in the bottom of sql.py. What do you think?. 2010/10/30 rochacbruno rochacbr...@gmail.com At my company we started to use this http://www.reviewboard.org/ Integrated with hg I suggest to start using this integrated with the main web2py repository. Enviado via iPhone Em 30/10/2010, às 21:33, mart msenecal...@gmail.com escreveu: BTW - have you seen Mondrian? - is built on Perforce. http://video.google.com/videoplay?docid=-8502904076440714866# Mart On Oct 30, 7:24 pm, mart msenecal...@gmail.com wrote: Hey, Would it make sense not to pull the apps that get built against #head revision (unless the goal is to test the apps themselves) and preferably just pull the code line it self @ #head revision? (follow up on this in next paragraph) And also, I don't know where things stand wrt bug tracking, but an important consideration are the bug fixes (does this build contain the fix for Bug X?). Typically when bugs get resolved/closed, they get verified on a clean slate, then once validated blessed (or rejected), the fix can be made public. I think the process is pretty close to what Thadeus mentioned, but would add the integration to bug tracking (this data is usually made part of the release notes specifically instead of a description typed in @ commit time). if the desire is automation (smoke tests) that I would store the raw data of the generic app in some dedicated tables, then re-populate the all-encompassing app with current data. By always grabbing latest_row, you keep the previous data for the previous build/release intact and in the correct place (so you don't need to change the test process from release to release, and you have the the build process insert a new set of records @ build time referencing the current build. With this, you also have reproducibility if needed. Last point, and I know I am persistently annoying with this, but mercurial, IMHO, sucks, sucks a lot. Personally I would use nothing less then the best out there, Perforce, specially if considering automated testing (again IMHO, but at least a fairly well supported statement :)). web2py is Open source, Perforce does give additional user licenses to open source projects (I'm sure Massimo would only need to make the request (which is online @ perforce .com btw). I mention that here because, good testing processes should be well integrated to source control. and for the web2py user, offering time for testing, a local instance of the perforce server can be installed, absolutely free of charge (with a max of 2 user licenses per server - more than enough for remote workers who can very easily keep in sync with the main web2py server (I work from home (Quebec, Canada), work for an American based company (HQ in Sunnyvale) - and that is how I do my work, with my local p4D. works like a charm). Anyways, enough of that, just thought I'd find another reason to slide that in ;) regards, Mart :) On Oct 30, 2:58 pm, Luther Goh Lu Feng elf...@yahoo.com wrote: 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 thade...@thadeusb.com 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 thade...@thadeusb.comwrote: 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
[web2py] Re: web2py 1.88.1 is OUT
This was fixed in trunk. On Nov 11, 5:49 pm, mattynoce mattyn...@gmail.com wrote: i'm seeing appadmin break for my auth_user table with a picture. when i have a photo, update works fine. when the photo is not there, i get an error: KeyError: 'picture_blob' and from top to bottomw: gluon/restricted.py line 188 init/controllers/appadmin.py:update line 410 gluon/globals.py line 96 init/controllers/appadmin.py:update line 275 gluon/sqlhtml.py line 1105 in accepts value = fields[fieldname] matt On Nov 1, 10:56 am, Jonathan Lundell jlund...@pobox.com wrote: On Nov 1, 2010, at 10:52 AM, mdipierro wrote: I think this is a good idea. Me too. I rather expect, though, that it will be necessary, and perhaps desirable regardless, for this to be a suite of applications rather than a single app. On Nov 1, 7:24 am, Martín Mulone mulone.mar...@gmail.com wrote: I'm going to start an w2p-app, called app by an example or testing app. The idea is to have in one app some code for testing pourpose, that make for example insert,select,delete like the code in the bottom of sql.py. What do you think?. 2010/10/30 rochacbruno rochacbr...@gmail.com At my company we started to use this http://www.reviewboard.org/ Integrated with hg I suggest to start using this integrated with the main web2py repository. Enviado via iPhone Em 30/10/2010, às 21:33, mart msenecal...@gmail.com escreveu: BTW - have you seen Mondrian? - is built on Perforce. http://video.google.com/videoplay?docid=-8502904076440714866# Mart On Oct 30, 7:24 pm, mart msenecal...@gmail.com wrote: Hey, Would it make sense not to pull the apps that get built against #head revision (unless the goal is to test the apps themselves) and preferably just pull the code line it self @ #head revision? (follow up on this in next paragraph) And also, I don't know where things stand wrt bug tracking, but an important consideration are the bug fixes (does this build contain the fix for Bug X?). Typically when bugs get resolved/closed, they get verified on a clean slate, then once validated blessed (or rejected), the fix can be made public. I think the process is pretty close to what Thadeus mentioned, but would add the integration to bug tracking (this data is usually made part of the release notes specifically instead of a description typed in @ commit time). if the desire is automation (smoke tests) that I would store the raw data of the generic app in some dedicated tables, then re-populate the all-encompassing app with current data. By always grabbing latest_row, you keep the previous data for the previous build/release intact and in the correct place (so you don't need to change the test process from release to release, and you have the the build process insert a new set of records @ build time referencing the current build. With this, you also have reproducibility if needed. Last point, and I know I am persistently annoying with this, but mercurial, IMHO, sucks, sucks a lot. Personally I would use nothing less then the best out there, Perforce, specially if considering automated testing (again IMHO, but at least a fairly well supported statement :)). web2py is Open source, Perforce does give additional user licenses to open source projects (I'm sure Massimo would only need to make the request (which is online @ perforce .com btw). I mention that here because, good testing processes should be well integrated to source control. and for the web2py user, offering time for testing, a local instance of the perforce server can be installed, absolutely free of charge (with a max of 2 user licenses per server - more than enough for remote workers who can very easily keep in sync with the main web2py server (I work from home (Quebec, Canada), work for an American based company (HQ in Sunnyvale) - and that is how I do my work, with my local p4D. works like a charm). Anyways, enough of that, just thought I'd find another reason to slide that in ;) regards, Mart :) On Oct 30, 2:58 pm, Luther Goh Lu Feng elf...@yahoo.com wrote: 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 thade...@thadeusb.com 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 thade...@thadeusb.comwrote: Someone writes a script to automate the process.
Re: [web2py] Re: web2py 1.88.1 is OUT
I'm going to start an w2p-app, called app by an example or testing app. The idea is to have in one app some code for testing pourpose, that make for example insert,select,delete like the code in the bottom of sql.py. What do you think?. 2010/10/30 rochacbruno rochacbr...@gmail.com At my company we started to use this http://www.reviewboard.org/ Integrated with hg I suggest to start using this integrated with the main web2py repository. Enviado via iPhone Em 30/10/2010, às 21:33, mart msenecal...@gmail.com escreveu: BTW - have you seen Mondrian? - is built on Perforce. http://video.google.com/videoplay?docid=-8502904076440714866# Mart On Oct 30, 7:24 pm, mart msenecal...@gmail.com wrote: Hey, Would it make sense not to pull the apps that get built against #head revision (unless the goal is to test the apps themselves) and preferably just pull the code line it self @ #head revision? (follow up on this in next paragraph) And also, I don't know where things stand wrt bug tracking, but an important consideration are the bug fixes (does this build contain the fix for Bug X?). Typically when bugs get resolved/closed, they get verified on a clean slate, then once validated blessed (or rejected), the fix can be made public. I think the process is pretty close to what Thadeus mentioned, but would add the integration to bug tracking (this data is usually made part of the release notes specifically instead of a description typed in @ commit time). if the desire is automation (smoke tests) that I would store the raw data of the generic app in some dedicated tables, then re-populate the all-encompassing app with current data. By always grabbing latest_row, you keep the previous data for the previous build/release intact and in the correct place (so you don't need to change the test process from release to release, and you have the the build process insert a new set of records @ build time referencing the current build. With this, you also have reproducibility if needed. Last point, and I know I am persistently annoying with this, but mercurial, IMHO, sucks, sucks a lot. Personally I would use nothing less then the best out there, Perforce, specially if considering automated testing (again IMHO, but at least a fairly well supported statement :)). web2py is Open source, Perforce does give additional user licenses to open source projects (I'm sure Massimo would only need to make the request (which is online @ perforce .com btw). I mention that here because, good testing processes should be well integrated to source control. and for the web2py user, offering time for testing, a local instance of the perforce server can be installed, absolutely free of charge (with a max of 2 user licenses per server - more than enough for remote workers who can very easily keep in sync with the main web2py server (I work from home (Quebec, Canada), work for an American based company (HQ in Sunnyvale) - and that is how I do my work, with my local p4D. works like a charm). Anyways, enough of that, just thought I'd find another reason to slide that in ;) regards, Mart :) On Oct 30, 2:58 pm, Luther Goh Lu Feng elf...@yahoo.com wrote: 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 thade...@thadeusb.com 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 thade...@thadeusb.comwrote: 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.comwrote: 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,
[web2py] Re: web2py 1.88.1 is OUT
I think this is a good idea. On Nov 1, 7:24 am, Martín Mulone mulone.mar...@gmail.com wrote: I'm going to start an w2p-app, called app by an example or testing app. The idea is to have in one app some code for testing pourpose, that make for example insert,select,delete like the code in the bottom of sql.py. What do you think?. 2010/10/30 rochacbruno rochacbr...@gmail.com At my company we started to use this http://www.reviewboard.org/ Integrated with hg I suggest to start using this integrated with the main web2py repository. Enviado via iPhone Em 30/10/2010, às 21:33, mart msenecal...@gmail.com escreveu: BTW - have you seen Mondrian? - is built on Perforce. http://video.google.com/videoplay?docid=-8502904076440714866# Mart On Oct 30, 7:24 pm, mart msenecal...@gmail.com wrote: Hey, Would it make sense not to pull the apps that get built against #head revision (unless the goal is to test the apps themselves) and preferably just pull the code line it self @ #head revision? (follow up on this in next paragraph) And also, I don't know where things stand wrt bug tracking, but an important consideration are the bug fixes (does this build contain the fix for Bug X?). Typically when bugs get resolved/closed, they get verified on a clean slate, then once validated blessed (or rejected), the fix can be made public. I think the process is pretty close to what Thadeus mentioned, but would add the integration to bug tracking (this data is usually made part of the release notes specifically instead of a description typed in @ commit time). if the desire is automation (smoke tests) that I would store the raw data of the generic app in some dedicated tables, then re-populate the all-encompassing app with current data. By always grabbing latest_row, you keep the previous data for the previous build/release intact and in the correct place (so you don't need to change the test process from release to release, and you have the the build process insert a new set of records @ build time referencing the current build. With this, you also have reproducibility if needed. Last point, and I know I am persistently annoying with this, but mercurial, IMHO, sucks, sucks a lot. Personally I would use nothing less then the best out there, Perforce, specially if considering automated testing (again IMHO, but at least a fairly well supported statement :)). web2py is Open source, Perforce does give additional user licenses to open source projects (I'm sure Massimo would only need to make the request (which is online @ perforce .com btw). I mention that here because, good testing processes should be well integrated to source control. and for the web2py user, offering time for testing, a local instance of the perforce server can be installed, absolutely free of charge (with a max of 2 user licenses per server - more than enough for remote workers who can very easily keep in sync with the main web2py server (I work from home (Quebec, Canada), work for an American based company (HQ in Sunnyvale) - and that is how I do my work, with my local p4D. works like a charm). Anyways, enough of that, just thought I'd find another reason to slide that in ;) regards, Mart :) On Oct 30, 2:58 pm, Luther Goh Lu Feng elf...@yahoo.com wrote: 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 thade...@thadeusb.com 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 thade...@thadeusb.comwrote: 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.comwrote: 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.
Re: [web2py] Re: web2py 1.88.1 is OUT
On Nov 1, 2010, at 10:52 AM, mdipierro wrote: I think this is a good idea. Me too. I rather expect, though, that it will be necessary, and perhaps desirable regardless, for this to be a suite of applications rather than a single app. On Nov 1, 7:24 am, Martín Mulone mulone.mar...@gmail.com wrote: I'm going to start an w2p-app, called app by an example or testing app. The idea is to have in one app some code for testing pourpose, that make for example insert,select,delete like the code in the bottom of sql.py. What do you think?. 2010/10/30 rochacbruno rochacbr...@gmail.com At my company we started to use this http://www.reviewboard.org/ Integrated with hg I suggest to start using this integrated with the main web2py repository. Enviado via iPhone Em 30/10/2010, às 21:33, mart msenecal...@gmail.com escreveu: BTW - have you seen Mondrian? - is built on Perforce. http://video.google.com/videoplay?docid=-8502904076440714866# Mart On Oct 30, 7:24 pm, mart msenecal...@gmail.com wrote: Hey, Would it make sense not to pull the apps that get built against #head revision (unless the goal is to test the apps themselves) and preferably just pull the code line it self @ #head revision? (follow up on this in next paragraph) And also, I don't know where things stand wrt bug tracking, but an important consideration are the bug fixes (does this build contain the fix for Bug X?). Typically when bugs get resolved/closed, they get verified on a clean slate, then once validated blessed (or rejected), the fix can be made public. I think the process is pretty close to what Thadeus mentioned, but would add the integration to bug tracking (this data is usually made part of the release notes specifically instead of a description typed in @ commit time). if the desire is automation (smoke tests) that I would store the raw data of the generic app in some dedicated tables, then re-populate the all-encompassing app with current data. By always grabbing latest_row, you keep the previous data for the previous build/release intact and in the correct place (so you don't need to change the test process from release to release, and you have the the build process insert a new set of records @ build time referencing the current build. With this, you also have reproducibility if needed. Last point, and I know I am persistently annoying with this, but mercurial, IMHO, sucks, sucks a lot. Personally I would use nothing less then the best out there, Perforce, specially if considering automated testing (again IMHO, but at least a fairly well supported statement :)). web2py is Open source, Perforce does give additional user licenses to open source projects (I'm sure Massimo would only need to make the request (which is online @ perforce .com btw). I mention that here because, good testing processes should be well integrated to source control. and for the web2py user, offering time for testing, a local instance of the perforce server can be installed, absolutely free of charge (with a max of 2 user licenses per server - more than enough for remote workers who can very easily keep in sync with the main web2py server (I work from home (Quebec, Canada), work for an American based company (HQ in Sunnyvale) - and that is how I do my work, with my local p4D. works like a charm). Anyways, enough of that, just thought I'd find another reason to slide that in ;) regards, Mart :) On Oct 30, 2:58 pm, Luther Goh Lu Feng elf...@yahoo.com wrote: 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 thade...@thadeusb.com 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 thade...@thadeusb.comwrote: 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.comwrote: 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
[web2py] Re: web2py 1.88.1 is OUT
Still an issue with list:string. Whem the update form loads it´s normal. When I submit it and back to it the list:string fields display as ['string','string']. Maybe because I loading the update form via LOAD function without ajax. I tested list:string with the wizard and it works perfectly. On Oct 30, 1:41 am, Thadeus Burgess thade...@thadeusb.com wrote: Can we make some sort of massive web2py app that makes use of every single feature in web2py (as much as possible). If the index page of the app returns OK then everything is working. ??? Kind of like a unit test without a unit test. -- Thadeus On Fri, Oct 29, 2010 at 6:05 PM, 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 On Oct 29, 5:32 pm, Bruno Rocha rochacbr...@gmail.com wrote: I have a question: From Trunk it is going directly to Stable, or is passing throught Nighly Built for testing before going Stable? What is the roadmap/timeline for release cycle? 2010/10/29 Branko Vukelic bg.bra...@gmail.com On Sat, Oct 30, 2010 at 12:05 AM, mdipierro mdipie...@cs.depaul.edu wrote: Fixed. 1.88.2 but please check it Woah! Two releases in a few hours! :D -- Branko Vukelić bg.bra...@gmail.com stu...@brankovukelic.com Check out my blog:http://www.brankovukelic.com/ Check out my portfolio:http://www.flickr.com/photos/foxbunny/ Registered Linux user #438078 (http://counter.li.org/) I hang out on identi.ca:http://identi.ca/foxbunny Gimp Brushmakers Guild http://bit.ly/gbg-group -- http://rochacbruno.com.br
[web2py] Re: web2py 1.88.1 is OUT
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?
Re: [web2py] Re: web2py 1.88.1 is OUT
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 thade...@thadeusb.comwrote: 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.comwrote: 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?
Re: [web2py] Re: web2py 1.88.1 is OUT
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.comwrote: 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?
[web2py] Re: web2py 1.88.1 is OUT
Hey, Would it make sense not to pull the apps that get built against #head revision (unless the goal is to test the apps themselves) and preferably just pull the code line it self @ #head revision? (follow up on this in next paragraph) And also, I don't know where things stand wrt bug tracking, but an important consideration are the bug fixes (does this build contain the fix for Bug X?). Typically when bugs get resolved/closed, they get verified on a clean slate, then once validated blessed (or rejected), the fix can be made public. I think the process is pretty close to what Thadeus mentioned, but would add the integration to bug tracking (this data is usually made part of the release notes specifically instead of a description typed in @ commit time). if the desire is automation (smoke tests) that I would store the raw data of the generic app in some dedicated tables, then re-populate the all-encompassing app with current data. By always grabbing latest_row, you keep the previous data for the previous build/release intact and in the correct place (so you don't need to change the test process from release to release, and you have the the build process insert a new set of records @ build time referencing the current build. With this, you also have reproducibility if needed. Last point, and I know I am persistently annoying with this, but mercurial, IMHO, sucks, sucks a lot. Personally I would use nothing less then the best out there, Perforce, specially if considering automated testing (again IMHO, but at least a fairly well supported statement :)). web2py is Open source, Perforce does give additional user licenses to open source projects (I'm sure Massimo would only need to make the request (which is online @ perforce .com btw). I mention that here because, good testing processes should be well integrated to source control. and for the web2py user, offering time for testing, a local instance of the perforce server can be installed, absolutely free of charge (with a max of 2 user licenses per server - more than enough for remote workers who can very easily keep in sync with the main web2py server (I work from home (Quebec, Canada), work for an American based company (HQ in Sunnyvale) - and that is how I do my work, with my local p4D. works like a charm). Anyways, enough of that, just thought I'd find another reason to slide that in ;) regards, Mart :) On Oct 30, 2:58 pm, Luther Goh Lu Feng elf...@yahoo.com wrote: 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 thade...@thadeusb.com 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 thade...@thadeusb.comwrote: 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.comwrote: 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?
[web2py] Re: web2py 1.88.1 is OUT
BTW - have you seen Mondrian? - is built on Perforce. http://video.google.com/videoplay?docid=-8502904076440714866# Mart On Oct 30, 7:24 pm, mart msenecal...@gmail.com wrote: Hey, Would it make sense not to pull the apps that get built against #head revision (unless the goal is to test the apps themselves) and preferably just pull the code line it self @ #head revision? (follow up on this in next paragraph) And also, I don't know where things stand wrt bug tracking, but an important consideration are the bug fixes (does this build contain the fix for Bug X?). Typically when bugs get resolved/closed, they get verified on a clean slate, then once validated blessed (or rejected), the fix can be made public. I think the process is pretty close to what Thadeus mentioned, but would add the integration to bug tracking (this data is usually made part of the release notes specifically instead of a description typed in @ commit time). if the desire is automation (smoke tests) that I would store the raw data of the generic app in some dedicated tables, then re-populate the all-encompassing app with current data. By always grabbing latest_row, you keep the previous data for the previous build/release intact and in the correct place (so you don't need to change the test process from release to release, and you have the the build process insert a new set of records @ build time referencing the current build. With this, you also have reproducibility if needed. Last point, and I know I am persistently annoying with this, but mercurial, IMHO, sucks, sucks a lot. Personally I would use nothing less then the best out there, Perforce, specially if considering automated testing (again IMHO, but at least a fairly well supported statement :)). web2py is Open source, Perforce does give additional user licenses to open source projects (I'm sure Massimo would only need to make the request (which is online @ perforce .com btw). I mention that here because, good testing processes should be well integrated to source control. and for the web2py user, offering time for testing, a local instance of the perforce server can be installed, absolutely free of charge (with a max of 2 user licenses per server - more than enough for remote workers who can very easily keep in sync with the main web2py server (I work from home (Quebec, Canada), work for an American based company (HQ in Sunnyvale) - and that is how I do my work, with my local p4D. works like a charm). Anyways, enough of that, just thought I'd find another reason to slide that in ;) regards, Mart :) On Oct 30, 2:58 pm, Luther Goh Lu Feng elf...@yahoo.com wrote: 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 thade...@thadeusb.com 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 thade...@thadeusb.comwrote: 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.comwrote: 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?
Re: [web2py] Re: web2py 1.88.1 is OUT
Hi , Not playing in the same league as everyone here , but definitely think that providing better unit tests + ui tests will definitely serve many purposes . First will ensure that release goes smoother and also will be a distinctive advantage over concurrence ( not sure if anyone else has some sort of ui testing framework ). It can also serve as simple example of the many features web2py offers ( more or less what we all have read once in the quick examples section). So i am voting a big YES on this
Re: [web2py] Re: web2py 1.88.1 is OUT
On Oct 30, 2010, at 4:24 PM, mart wrote: Last point, and I know I am persistently annoying with this, but mercurial, IMHO, sucks, sucks a lot. Personally I would use nothing less then the best out there, Perforce, specially if considering automated testing (again IMHO, but at least a fairly well supported statement :)). Not digress too far, but as a long-time Perforce user, I'm pretty much committed (!) to using hg for my future projects. If we were discussing p4 vs svn, I'd agree, but I confess to being a little baffled by the hg sucks a lot assertion.
[web2py] Re: web2py 1.88.1 is OUT
Yes, agreed , that may have been a little too strong of an opinion, in fact, WAS too strong, so I'll take that back since the intention was not to offend, so apologies for that one. I'll say instead: I think P4 is much better suited when comes time to integrate to processes/ automation such QA automation, but again, that's just my opinion based on my own experience. Mart :) On Oct 30, 8:17 pm, Jonathan Lundell jlund...@pobox.com wrote: On Oct 30, 2010, at 4:24 PM, mart wrote: Last point, and I know I am persistently annoying with this, but mercurial, IMHO, sucks, sucks a lot. Personally I would use nothing less then the best out there, Perforce, specially if considering automated testing (again IMHO, but at least a fairly well supported statement :)). Not digress too far, but as a long-time Perforce user, I'm pretty much committed (!) to using hg for my future projects. If we were discussing p4 vs svn, I'd agree, but I confess to being a little baffled by the hg sucks a lot assertion.
Re: [web2py] Re: web2py 1.88.1 is OUT
At my company we started to use this http://www.reviewboard.org/ Integrated with hg I suggest to start using this integrated with the main web2py repository. Enviado via iPhone Em 30/10/2010, às 21:33, mart msenecal...@gmail.com escreveu: BTW - have you seen Mondrian? - is built on Perforce. http://video.google.com/videoplay?docid=-8502904076440714866# Mart On Oct 30, 7:24 pm, mart msenecal...@gmail.com wrote: Hey, Would it make sense not to pull the apps that get built against #head revision (unless the goal is to test the apps themselves) and preferably just pull the code line it self @ #head revision? (follow up on this in next paragraph) And also, I don't know where things stand wrt bug tracking, but an important consideration are the bug fixes (does this build contain the fix for Bug X?). Typically when bugs get resolved/closed, they get verified on a clean slate, then once validated blessed (or rejected), the fix can be made public. I think the process is pretty close to what Thadeus mentioned, but would add the integration to bug tracking (this data is usually made part of the release notes specifically instead of a description typed in @ commit time). if the desire is automation (smoke tests) that I would store the raw data of the generic app in some dedicated tables, then re-populate the all-encompassing app with current data. By always grabbing latest_row, you keep the previous data for the previous build/release intact and in the correct place (so you don't need to change the test process from release to release, and you have the the build process insert a new set of records @ build time referencing the current build. With this, you also have reproducibility if needed. Last point, and I know I am persistently annoying with this, but mercurial, IMHO, sucks, sucks a lot. Personally I would use nothing less then the best out there, Perforce, specially if considering automated testing (again IMHO, but at least a fairly well supported statement :)). web2py is Open source, Perforce does give additional user licenses to open source projects (I'm sure Massimo would only need to make the request (which is online @ perforce .com btw). I mention that here because, good testing processes should be well integrated to source control. and for the web2py user, offering time for testing, a local instance of the perforce server can be installed, absolutely free of charge (with a max of 2 user licenses per server - more than enough for remote workers who can very easily keep in sync with the main web2py server (I work from home (Quebec, Canada), work for an American based company (HQ in Sunnyvale) - and that is how I do my work, with my local p4D. works like a charm). Anyways, enough of that, just thought I'd find another reason to slide that in ;) regards, Mart :) On Oct 30, 2:58 pm, Luther Goh Lu Feng elf...@yahoo.com wrote: 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 thade...@thadeusb.com 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 thade...@thadeusb.comwrote: 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.comwrote: 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?
[web2py] Re: web2py 1.88.1 is OUT
Fixed. 1.88.2 but please check it
On Oct 29, 3:47 pm, Martín Mulone mulone.mar...@gmail.com wrote:
I mail you the app.
this is the app
*in db.py*
db.define_table('posts',
Field('id', 'id'),
Field('title', 'string', length=255),
Field('keywords', 'list:string'),
migrate=True)
posts = db(db.posts.id0).select()
if not posts:
nid=db.posts.insert(title=The Moon,keywords=['moon','space','dark'])
nid=db.posts.insert(title=The
Earth,keywords=['earth','blue','humans'])
*in controller/default.py*
posts=db(db.posts.keywords.contains('moon')).select()
return dict(posts=posts)
Now in this version return nothing, and in previous version work.
2010/10/29 Martín Mulone mulone.mar...@gmail.com
Massimo, seems there are a problem with list: string, and using contains.
Iam going to make an example. Or do you change anything about using contains
in list string?. Because sentence like
db(db.posts.keywords.contains('tag')).select() is returning nothing
2010/10/29 mdipierro mdipie...@cs.depaul.edu
Give it a try...
Changelog
## 1.88.1
- better list: string support, thanks Bob
- jquery 1.4.3
- scripts/autoroutes.py
- new admin wizard
- added retrieve_username to navbar (if username)
- internal rewrite for arbitrary paths (abspath), thanks Jonathan
- populate support for list: and decimal, thanks Chirstian
- markmin2latex has extra attribute
- better mercual admin allows list of files, versions and retrieve
- new error report system, thanks Thadeus and Selecta
- SQLFORM.accepts(detect_record_change).record_changed
- fixed cron for bytecode compiled apps, thanks Álvaro J. Iradier Muro
- other bugs fixes and pep8 compliant fixes
--
My blog:http://martin.tecnodoc.com.ar
My portfolio *spanish*:http://www.tecnodoc.com.ar
Checkout my last proyect instant-press:http://www.instant2press.com
--
My blog:http://martin.tecnodoc.com.ar
My portfolio *spanish*:http://www.tecnodoc.com.ar
Checkout my last proyect instant-press:http://www.instant2press.com
Re: [web2py] Re: web2py 1.88.1 is OUT
On Sat, Oct 30, 2010 at 12:05 AM, mdipierro mdipie...@cs.depaul.edu wrote: Fixed. 1.88.2 but please check it Woah! Two releases in a few hours! :D -- Branko Vukelić bg.bra...@gmail.com stu...@brankovukelic.com Check out my blog: http://www.brankovukelic.com/ Check out my portfolio: http://www.flickr.com/photos/foxbunny/ Registered Linux user #438078 (http://counter.li.org/) I hang out on identi.ca: http://identi.ca/foxbunny Gimp Brushmakers Guild http://bit.ly/gbg-group
Re: [web2py] Re: web2py 1.88.1 is OUT
I have a question: From Trunk it is going directly to Stable, or is passing throught Nighly Built for testing before going Stable? What is the roadmap/timeline for release cycle? 2010/10/29 Branko Vukelic bg.bra...@gmail.com On Sat, Oct 30, 2010 at 12:05 AM, mdipierro mdipie...@cs.depaul.edu wrote: Fixed. 1.88.2 but please check it Woah! Two releases in a few hours! :D -- Branko Vukelić bg.bra...@gmail.com stu...@brankovukelic.com Check out my blog: http://www.brankovukelic.com/ Check out my portfolio: http://www.flickr.com/photos/foxbunny/ Registered Linux user #438078 (http://counter.li.org/) I hang out on identi.ca: http://identi.ca/foxbunny Gimp Brushmakers Guild http://bit.ly/gbg-group -- http://rochacbruno.com.br
[web2py] Re: web2py 1.88.1 is OUT
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 On Oct 29, 5:32 pm, Bruno Rocha rochacbr...@gmail.com wrote: I have a question: From Trunk it is going directly to Stable, or is passing throught Nighly Built for testing before going Stable? What is the roadmap/timeline for release cycle? 2010/10/29 Branko Vukelic bg.bra...@gmail.com On Sat, Oct 30, 2010 at 12:05 AM, mdipierro mdipie...@cs.depaul.edu wrote: Fixed. 1.88.2 but please check it Woah! Two releases in a few hours! :D -- Branko Vukelić bg.bra...@gmail.com stu...@brankovukelic.com Check out my blog:http://www.brankovukelic.com/ Check out my portfolio:http://www.flickr.com/photos/foxbunny/ Registered Linux user #438078 (http://counter.li.org/) I hang out on identi.ca:http://identi.ca/foxbunny Gimp Brushmakers Guild http://bit.ly/gbg-group -- http://rochacbruno.com.br
Re: [web2py] Re: web2py 1.88.1 is OUT
Can we make some sort of massive web2py app that makes use of every single feature in web2py (as much as possible). If the index page of the app returns OK then everything is working. ??? Kind of like a unit test without a unit test. -- Thadeus On Fri, Oct 29, 2010 at 6:05 PM, 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 On Oct 29, 5:32 pm, Bruno Rocha rochacbr...@gmail.com wrote: I have a question: From Trunk it is going directly to Stable, or is passing throught Nighly Built for testing before going Stable? What is the roadmap/timeline for release cycle? 2010/10/29 Branko Vukelic bg.bra...@gmail.com On Sat, Oct 30, 2010 at 12:05 AM, mdipierro mdipie...@cs.depaul.edu wrote: Fixed. 1.88.2 but please check it Woah! Two releases in a few hours! :D -- Branko Vukelić bg.bra...@gmail.com stu...@brankovukelic.com Check out my blog:http://www.brankovukelic.com/ Check out my portfolio:http://www.flickr.com/photos/foxbunny/ Registered Linux user #438078 (http://counter.li.org/) I hang out on identi.ca:http://identi.ca/foxbunny Gimp Brushmakers Guild http://bit.ly/gbg-group -- http://rochacbruno.com.br
