The same article you refer to says" "A frequent characteristic of a smoke test is that it runs quickly, often in the order of a few minutes and thus provides much quicker feedback and faster turnaround than the running of full test suites which can take hours or even days."
I would think that if your current unit & functional tests run completely within the order of minutes, then adding smoke tests as well may be redundant. There are also tools to help speed up those tests, which might be worth investigating before adding another test layer. On Saturday, 24 January 2015 17:22:04 UTC+2, Tomáš Ehrlich wrote: > > 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), 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), 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/67192287-6a60-40ce-9260-bf76c1836942%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
