I think part of the problem is a lack of dog food. I started looking last night at the state of web2py testing, and was amazed that the gluon/tests directory is not included in any of the 'source' distributions. In fact it's not in the Google code build either. After downloading the bazaar trunk from ~mdipierro/web2py/devel I see that it only exists there. Further there are only 38 tests in that repository. I had originally intended to shadow the changes in Google code by seeing what changed, writing the test that would fail, syncing to the change list and verifying that it now passed, but getting even to that point will be a huge amount of work. If nothing else because now there is a requirement to only use launchpad. Is there a reason why the tests aren't including in any other distribution?
I'd be curious to see what the Lines of Code vs Lines of Test graph would look like for Web2py http://www.cuberick.com/2010/06/lines-of-code-vs-lines-of-test.html and how we can improve it. On Sun, Jun 20, 2010 at 8:45 AM, Thadeus Burgess <[email protected]> wrote: > I agree with most of these points. > > http://packages.python.org/web2py_utils/test_runner.html > > That is about as far as you will get with testing on web2py. You need > very hacky code just to run your tests properly. Web2py was just not > designed with testing in mind, and due to backwards compatibility > never can be. > > One of the things I dislike about web2py are the conventions! I am > tired of software assuming what I want it to do (grrr microsoft > paperclip), half the time I have to hack around things the framework > "assumes" I want to get it to do what I really want. > > -- > Thadeus > > > > > > On Sun, Jun 20, 2010 at 2:26 AM, Giuseppe Luca Scrofani > <[email protected]> wrote: >> I am a totally noob so I am not the best person to tell this, however, >> I think web2py is the best python software I ever tried, after python >> itself. I tried only django in this field before, my experience in >> limited, but I just can't imagine something better for the development >> of web application. Maybe Ruby On Rails, in the scene from a long >> time, can be more "mature". But I think with some exposition web2py >> can grow to be the industry standard, now it seems to be in a niche >> waiting to explode. You Bihn made some good service to address >> weakness and propose improvements, so thanks. When I've had enough >> experience and skill to contribute to this project Im surely will and >> if this gaps arent yet solved (very improbable) I will try to solve >> the most easy :D >> >> For the point 3 I can say conventions dont'have to be this rigid, I >> create always css, img, swf ecc. folders on static. I think it is >> automatic to do this, but if dont want to do this for any reason I >> dont like to be forced. Maybe I'm wrong, maybe without all present >> conventions learning will be much difficult and web2py would be more >> like cherrypy where you can do all what you want how you want (if you >> know your stuff) with a higher learning curve. >> >> What I think is another area, in my humble opinion, of improvement is >> the manual, it is very good, but more example, a clearer API and a >> better search function can make my searches for information more easy. >> >> Please excuse me for my bad english. >> >
