Regarding Martin's response for anyone who is learning the ropes like me, I removed the execfile() line and placed my unit_test.py script in the module folder.
On Monday, July 23, 2012 12:13:07 PM UTC-7, Martin.Mulone wrote: > > I'm following http://www.web2py.com/AlterEgo/default/show/260 >> > > that guide is too old, have execfile() :S. Search in the group on how to > use modules in your app. > > 2012/7/22 Mark Li <[email protected]> > >> I'm fairly new to test-driven development and have decided it is the best >> way to go for my new webapp. While functional tests with selenium seem to >> be more straightforward (as far as what the tests want to accomplish), I'm >> lost on what unit tests for the database should test for. >> >> For example, if I have a database table with columns id, 'dogowner', and >> 'dogname', and have a controller returning a dict with 'dogowners', what >> should I be testing in the unit tests for the database and controller? >> >> The database table will be fixed with a limited number of 'dogowner' >> entries, about 10, so should I be testing whether the database has 10 >> entries, and if the len of the dict returned by the controller is 10? This >> datatable may not be fixed in the future, so what functionality of the >> database would I be testing for? >> >> >> >> I'm following http://www.web2py.com/AlterEgo/default/show/260 , but >> while that page explains HOW to go about unit testing, it doesn't explain >> what I should be testing for. Anyone experienced with TDD in web2py want to >> point me in the right direction? Thanks in advance! >> >> -- >> >> >> >> > > > > -- > http://www.tecnodoc.com.ar > > --
