Hello everyone, After some trial and error yesterday, mostly related to trying to fix too many things at the same time (mental note - don't!), I've completed a minimal-effort rewrite of old megatests for the new test framework. See the 'megatests' branch of my GitHub repository:
http://github.com/mkszuba/pygr/commit/41c325463ebb004c60450b7103febba13778bcb7 (the files are in tests/) Some comments: - like I said above, this has been a minimal-effort rewrite. All tasks such as reducing code redundancy (the tests appear to share a lot of common code), using worldbase instead of pygr.Data, improving PEP-8 compliance and so on have been skipped on purpose; - changing the framework has made megatests rather noisy. I'll try to quieten them a bit soon; - I was worried whether the __init__() -> setUp() transition could mess up creation of temporary directories, possibly destroying separation between tests. I've had a look at the output of annotation_dm2_megatests and it seems each test still uses its own temporary directory, i.e. nothing's broken - still, it would be great if someone double-checked this; - it seems that in its present form, the method test_seqdb() present in most megatests (the purpose of which has been to check whether the necessary sequence data is present in the system) isn't particularly useful - it always ends up being run as the last, i.e. after all tests which actually rely on this data to be present have already been run. What do you think we should do with it? As always, all questions or comments are welcome. Cheers, -- MS --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
