we're working on having a better recommended (and documented, and simple) way to run tests.
Until recently I didn't think about tests at all: this speeded up greatly the productivity but on the long run a lot of time has been "wasted" on worrying too much if, e.g., I can upgrade web2py (or for what matters, any other component inside my deployment, such as the db, redis, jquery, bootstrap, etc). This made me think that if what you're going to do needs to be (even seldomly) updated, you'd better find time to write those tests. If instead is something that you do just for you, and you know you're never going to touch it again, then you can continue to avoid writing tests alltogether. When the next jquery update will be out, I'll just slip it into my test server, run all the tests and see if something breaks. If I had no tests, I'd be forced to fire up all the features of my app by hand, probably missing something crucial (and I'll loose a few night sleeps) :P -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
