It seems that the tests are trying to do something odd... What does your test.cfg look like?
On Feb 8, 6:18 pm, [EMAIL PROTECTED] wrote: > I'm a new turbogears user. I've been following this mailing list > for a couple weeks. I'm trying to get some traction on my current > project, that I want to deploy in turbogears. I've played around > with TG enough now to know I like the basic concepts and how easy > it is to turn python code into working web pages. > > I like test driven development, so now that I'm ready to start > serious development the first thing I did was run the nosetests. > They failed. I tried it again in a fresh quickstart project, > and they still failed. > > This is tg 1.0.1 with Identity enabled, and the identity tests appear > to be the problem. There's also the capitalization issue with the > tags that I heard mentioned here earlier. I also remember some > stuff about tests failing with DB errors, but I believe that had > to do with SQL Alchemy, and I'm using SO. > > I'm surprised that a release went out the door with tests that fail > out of the box. > > If these bugs have been fixed, what's the best way to track the > "production" version of TG (I presume that's 1.0.1 right now, > since that's what comes up when I do an easy_install of TG) > with bug fixes applied? > > I did not get any hits when I searched on the particular error > message I'm getting from the nosetests. They look like this: > > ====================================================================== > ERROR: A user can reset their password. > ---------------------------------------------------------------------- > Traceback (most recent call last): > File ".../sample/tests/test_registration.py", line 51, in setUp > self.create_identity_tables() > File ".../sample/tests/test_registration.py", line 186, in > create_identity_tables > > register_model.user_class_finder.user_class.createTable(createJoinTables=False) > File ".../SQLObject-0.7.1dev_r1860-py2.4.egg/sqlobject/main.py", line > 1322, in createTable > conn.createTable(cls) > File ".../SQLObject-0.7.1dev_r1860-py2.4.egg/sqlobject/dbconnection.py", > line 527, in createTable > self.query(self.createTableSQL(soClass)) > File ".../SQLObject-0.7.1dev_r1860-py2.4.egg/sqlobject/dbconnection.py", > line 752, in query > return self._dbConnection._query(self._connection, s) > File ".../SQLObject-0.7.1dev_r1860-py2.4.egg/sqlobject/dbconnection.py", > line 303, in _query > self._executeRetry(conn, conn.cursor(), s) > File ".../SQLObject-0.7.1dev_r1860-py2.4.egg/sqlobject/dbconnection.py", > line 298, in _executeRetry > return cursor.execute(query) > OperationalError: table tg_user already exists > > Should I file a trac case for this? I haven't tried looking for the bug > yet since given the recent discussions about failing tests I'm hoping > the bugs have been fixed and I just need to update my version somehow... > > --David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
