Another long time user here (at some point I'd love to make the jump to contributor, just need to find more time) - out of interest, is there a reason we don't use Travis? I wonder if that might help those with commit access, since pre-tested pull requests would mean you could have confidence that the tests at least pass. Apologies if this has been discussed before (there are a few contributors to this group called Travis, which made searching a bit tricky!).
Dom On Sunday, October 28, 2012 2:11:56 AM UTC, ptone wrote: > > Thanks Jan for the contributions. > > I'll add a couple bits to Russ's excellent reply. > > I generally will run just a specific test, or a subset of the tests while > developing the patch initially, this is much faster and can let you iterate > much more quickly. > > Julien has put together a great tool for running the full test suite - > allowing you to test more python versions including the GIS stuff: > > https://github.com/jphalip/djangocore-box > > Finally - note that for some work, you will occasionally hit test > interaction issues, where global state causes unintended failures to happen > in apparently unrelated tests. Hopefully this won't happen, but if it does > and you're stumped, reach out for help. > > -Preston > > On Saturday, October 27, 2012 4:33:35 PM UTC-7, Jan Bednařík wrote: >> >> Hi all, >> >> I'm using Django for more than four years and last week I started >> contributing. >> >> In docs about contributing I didn't find how detailed should be my >> testing while I'm writing or reviewing patch? Is enough to run tests only >> for patched module? Or should I run full test suite for each patch? Which >> combinations of Python versions and database engines are mandatory? >> >> So far I was running Python 2.7 & SQLite3 for development/review testing >> of module. Python 3.2 & SQLite3, Python 2.7 & PostgreSQL for patched module >> and in the end Python 2.7 & SQLite3 full test suite (with selenium, etc.). >> Is this workflow ok? >> >> Jan Bednařík aka Architekt >> > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/ZZkz9Q6B9BAJ. 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.
