Hi Richard. I don't know how to create an in-memory db with postgres, but if you don't use any direct SQL command, you shouldn't have problems using SQLite to test purposes.
No web2py.test doesn't manage any db replication. It just supply a web2py environment usable to your tests. You should manage your test data by yourself, as in any other test infrastructure. I use in my tests gluon/populate.py/populate() to create test data to help me with tests. It's really useful. On Mon, Jun 3, 2013 at 11:46 AM, Richard Vézina <ml.richard.vez...@gmail.com> wrote: > Sorry to revive this old thread that get pretty long... But this one si for > Vinicius... > > I have some time to explore and test web2py.test you publish... > > The only thing, I would know for now is how to use in memory if I use > postgres in my app... Should I mock database with SQLite in memory as sugget > Anthony? Does web2py.test manage the database replication or do I am > responsible to create a subset of the main database for testing purpose? > > Thanks. > > Richard > > > On Sun, May 26, 2013 at 7:41 PM, Anthony <abasta...@gmail.com> wrote: >> >> Arnon, it is more than a little frustrating having a discussion with you, >> as it appears you don't really pay much attention to what others are saying. >> If you go back, you will see I have already addressed your argument. You are >> correct that we make different assumptions, but the differences are not >> where you think. My only assumption is that it is better to have a given >> feature sooner rather than later. On the contrary, you seem to be completely >> indifferent between having a feature available now and having it available >> at some indefinite future time. In your world, I suppose it would make sense >> to find the single most productive programmer on the planet, and let that >> person write all the software for all of humanity. Unfortunately, I think >> you're the only guy living in your world. If you can't see why it would be >> better to have software available sooner rather than later (or at least >> comprehend why most other people would have that preference), then I'm >> afraid you are beyond any help we can provide to you here. >> >>> As for users=developers - yes you are right. I may have a different >>> expectation than what in expected/accepted in the web2py community. That >>> would be a flaw of communication on the part of the web2py >>> community/developers/maintainers/managers etc. >> >> >> No, I believe the flaw lies elsewhere in this case. I will leave it as an >> exercise for you to figure it out. ;-) >> >> 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. >> >> > > > -- > > --- > 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. > > -- --- 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.
