Re: am i choosing write way of producing stuf?
Usually, you put the unit tests in one directory (because they're not part of your source code), then you just develop modules in the source code directly and add unit tests as you go. That said, the only part of this that's odd is that you're copying files in after testing them and not just developing them in place, which is fine, just unusual. Eventually that'll stop working though, as soon as you start having relatively complicated modules that need to import other modules.
If you haven't yet found py.test you might like a package like that at this point. It takes:
assert thing1 == thing2and basically any other assert, and can break it down and show you all the values in the _expression_, among many other features. You just write a bunch of files in a tests directory with functions that start with the word test, use normal Python asserts, and done.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
