On Mar 1, 11:04 am, "C. Titus Brown" <[email protected]> wrote:
> However, I think it's really important from a testing perspective to > make a new directory for each test run. Otherwise you can end up with > data that incorrectly persists across test runs & causes test boggles. I do partially agree, but there are two separate issues. One is about creating a new directory the other is about the location and naming of the directory. Normal temporary files are both ephemeral but also meant to store intermediary data that people do not need to see. The results of a test run are not temporary data in this sense, we are always interested in what they contain, especially when things break. How would one even do test driven developement if the actual output of the tests are somewhere hidden? This just bit me right now, when you run pygrtestserver it now writes its output to a temporary data but when it fails (now) I have no way of quickly seeing what it actually wrote out. A separate flag to turn this on behavior on/off does not seem right either as I don't see any obvious benefit for stashing these files out of sight when deleting them yourself is just as simple. I have added a series of commits to, the current temporary file seems to work fine, so that's a good change: http://github.com/ctb/pygr/commits/psu-tests-branch I still got unresolved issues with pygrdataserver tests (see above) and sqlsequence_test.py now breaks as well. Not sure yet what that's about. I'll try to keep fixes one per commit to keep things in some traceable form. Istvan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" 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/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
