Hey, so its Week 2 of the 'get to know things and people' phase, and things are going well. I have submitted a patch with tests to the following ticket: http://code.djangoproject.com/ticket/8968 as my 'learn the system' patch. In addition, I have been looking into how to best handle the following 2 issues (which I have targeted as my first serious design hurdle): 1) Give Django's runner enough information about the windmill tests state (and if we should even try) so that we can accurately report which windmill tests have passed. 2) Is the dream of tandem testing feasible and/or worthwhile. While its already very much possible to use the WindmillTestClient class on its own, being run from the django test runner, these are functionally separate 'scopes'. I see there being a few key things I want to have access to/provide in the Windmill context (Which will inherently be special, the pure-django unittest context will not have anything added to it) a. Access to models/fixtures so that we can: Test that page is empty in windmill Add data via Django model Test that data is on page with windmill Delete data via Django model Add same data with windmill Test that data is on page with windmill, same as before.
b. Allow some sort of awareness regarding fixtures and current execution state. I haven't worked out exactly what this will look like, but in theory, I should not need to be duplicating test data for assertions. c. Lastly, multithreading in the test server. I mentioned this in my last mail. I also made contact with Ned (the author/maintainer of coverage.py) and discussed coverage.py's future. He will be meeting us more than halfway on a few points, making our lives a bit easier. Thats it for this week! Have fun at EuroDjangoCon all! -- Kevin Kubasik http://kubasik.net/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
