Hello, last few weeks I’ve been thinking about implementing smoke tests into my deployment process. Last week I wrote simple test runner (https://github.com/djentlemen/django-smoked <https://github.com/djentlemen/django-smoked>), but still I’m missing methodology *what* should I test and *how*. Since smoke test has very wide definition for different types of software — https://en.wikipedia.org/wiki/Smoke_testing_(software) <https://en.wikipedia.org/wiki/Smoke_testing_(software)>, my idea is: After every deployment run small subset of tests with *production* settings and just check, that app was deployed successfully. If not, rollback to previous version immediately.
Few such tests might be: — check responses of few URL endpoints (like homepage) — check database settings are valid (since most tests runs on testing/development database) — check cache, email settings, etc (for the same reasons as above) I wonder how do you test your apps? Do you use some kind of „smoke tests“ described above? Cheers, Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/467626FA-A50D-4AF9-991C-5BD05637693F%40gmail.com. For more options, visit https://groups.google.com/d/optout.
