> Just as an example to how the absent of communication has led to > porrer-and-unnecessary implementation(s): > > In we2py_utils, I've seen Thadeus used 'sqlight:memory' in the > connection-string. This completely circumvent the entire issue that many > implementations I had seen have been hammering on - the issue of having to > clear-out the fixtures on each test-session-setup, and the issue of having > an sqlight-file locked by another process. When you use an in-memory > instance of sqlight in your setup-implementation, you are completely > avoiding such issues, AND it's faster AND simpler. >
Note, web2py_utils is linked from http://www.web2py.com/init/default/documentation, so it is discoverable, and it's not clear that others who have implemented testing solutions were unaware of it. There's also no reason other solutions couldn't use sqlite:memory if desired. In some cases, though, you might want to have a test database populated with real data, so you wouldn't want to use sqlite:memory. It's not clear what you're looking for, though. You don't seem to think information about testing belongs in the book, but I don't see why not (particularly since there are some complications introduced by the web2py execution environment). Aside from that, you seem to want to know what other people are working on and what they have learned. Often when people have learned something, they post it on web2pyslices, and there are a couple of recipes there related to testing. That's generally the place for sharing solutions. As for what people are working on, certainly they can and do make announcements here and on the developers' list. What else should there be? Anthony -- --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
