I thinks I may have figured out what seems to be a good way. I create the models in the top of the test.py file. This is working and the table are only there for testing so I'm no polluting my database with these tables after the tests are finished. Still looking for feedback on best practice though.
Thanks Again, Mark On Dec 4, 5:37 am, "Mark (Nosrednakram)" <nosrednak...@gmail.com> wrote: > Hello Django Users, > > I have a few applications that don't have defined models but that > interact with other models. The most recent is a full text search > engine based on Whoosh. Whoosh has it own back end for storing > indexes. The application indexes models but doesn't have any of it's > own models defined. What is the best way to create a test I have the > following ideas: > > * Create test models if settings.py has DEBUG=True but not sure how > to remove table when DEBUG !=True > * Create a testing application that has seeded data and models for > this type of situation > * Create tables from within the test script > > Is there a standard way to do this I haven't found? If not any > suggestions on the ideas? Thoughts on above? Other examples are > online table exporter, chat. > > Thank you, > Mark -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
