Hi guys.

I just published an example application with runnable test cases [1].

I don't like doctests, so I used py.test due to some reasons:
- I don't need to subclass anything to make my test cases.
- py.test understands unittest and nose tests.
- py.test fixtures schema is (really) very flexible, allowing me to
inject external dependencies. That's the case with Web2py's env().
- I can make assertions using simple Python, with assert statement.

This way implements a mix between WebClient and env(), allowing test
cases to execute a controller/function() and immediately check with
DAL commands if the action was properly executed (i.e, database
updated).

More details are in docs and inside code.

Feel free to fork, collaborate and use it. But give us feedback.

[1] https://github.com/viniciusban/web2py.test

--
Vinicius Assef

-- 

--- 
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.


Reply via email to