<\/span><\/h2>\nSanity testov\u00e1n\u00ed \u0161et\u0159\u00ed mnoho \u010dasu a \u00fasil\u00ed, proto\u017ee zabra\u0148uje t\u00fdm\u016fm QA ztr\u00e1cet \u010das hlub\u0161\u00edmi testy, ne\u017e se ujist\u00ed, \u017ee z\u00e1kladn\u00ed funkce sestaven\u00e9ho softwaru funguj\u00ed tak, jak maj\u00ed.<\/p>\n
Sanity testov\u00e1n\u00ed je rychl\u00e9, n\u00e1kladov\u011b efektivn\u00ed a nezbytn\u00e9, pokud cht\u011bj\u00ed v\u00fdvojov\u00e9 a testovac\u00ed t\u00fdmy efektivn\u011b a rychle vytv\u00e1\u0159et software bez chyb.<\/p>\n
\u25cf \u0160et\u0159\u00ed \u010das a zdroje
\n\u25cf Nen\u00ed t\u0159eba \u017e\u00e1dn\u00e9 dokumentace
\n\u25cf M\u016f\u017ee pomoci identifikovat chyb\u011bj\u00edc\u00ed p\u0159edm\u011bty
\n\u25cf P\u0159edch\u00e1z\u00ed pozd\u011bj\u0161\u00edm z\u00e1va\u017en\u00fdm probl\u00e9m\u016fm<\/p>\n
<\/h3>\n<\/span>Je efektivn\u00ed a rychl\u00fd<\/span><\/h3>\nSanity testov\u00e1n\u00ed je rychl\u00fd a efektivn\u00ed zp\u016fsob, jak zjistit, zda kl\u00ed\u010dov\u00e9 funkce sestaven\u00e9ho softwaru funguj\u00ed podle o\u010dek\u00e1v\u00e1n\u00ed.<\/p>\n
Jednoduch\u00e9 testy spr\u00e1vnosti m\u016f\u017eete prov\u00e9st za m\u00e9n\u011b ne\u017e hodinu, a pokud test spr\u00e1vnosti projde, d\u00e1 to va\u0161emu t\u00fdmu QA zelenou k dal\u0161\u00edmu testov\u00e1n\u00ed.<\/p>\n
<\/h3>\n<\/span>Nevy\u017eaduje dokumentaci<\/span><\/h3>\nV\u011bt\u0161ina sanity test\u016f je neskriptovan\u00e1, co\u017e znamen\u00e1, \u017ee teste\u0159i nemaj\u00ed p\u0159\u00edsn\u00e9 po\u017eadavky na vypisov\u00e1n\u00ed krit\u00e9ri\u00ed \u00fasp\u011b\u0161nosti\/ne\u00fasp\u011b\u0161nosti jednotliv\u00fdch test\u016f nebo na psan\u00ed dokumentace, kter\u00e1 by prezentovala v\u00fdsledky sanity testu. To znamen\u00e1, \u017ee ji lze prov\u00e9st relativn\u011b rychle a nenucen\u011b, ani\u017e by do\u0161lo k v\u00fdrazn\u00e9mu naru\u0161en\u00ed pr\u00e1ce.<\/p>\n
<\/h3>\n<\/span>Dok\u00e1\u017ee identifikovat chyb\u011bj\u00edc\u00ed objekty<\/span><\/h3>\nSanity testov\u00e1n\u00ed m\u016f\u017ee tester\u016fm pomoci identifikovat souvisej\u00edc\u00ed nebo chyb\u011bj\u00edc\u00ed objekty, kter\u00e9 by mohly b\u00fdt pro funkci sestaven\u00ed kl\u00ed\u010dov\u00e9. Proto\u017ee se sanity testov\u00e1n\u00ed pou\u017e\u00edv\u00e1 k individu\u00e1ln\u00edmu testov\u00e1n\u00ed konkr\u00e9tn\u00edch funkc\u00ed, je p\u0159i sanity testov\u00e1n\u00ed snaz\u0161\u00ed identifikovat jednotliv\u00e9 chyby a probl\u00e9my ne\u017e p\u0159i prov\u00e1d\u011bn\u00ed smoke test\u016f a dal\u0161\u00edch \u00favodn\u00edch test\u016f softwaru.<\/p>\n
<\/h3>\n<\/span>P\u0159edch\u00e1z\u00ed to pozd\u011bj\u0161\u00edm z\u00e1va\u017en\u00fdm probl\u00e9m\u016fm<\/span><\/h3>\nKontrola spr\u00e1vnosti testov\u00e1n\u00ed v\u00e1m pom\u016f\u017ee identifikovat probl\u00e9my ji\u017e v po\u010d\u00e1te\u010dn\u00ed f\u00e1zi testov\u00e1n\u00ed a zabr\u00e1nit v\u00fdskytu z\u00e1va\u017en\u00fdch chyb, kter\u00e9 by pozd\u011bji p\u0159i v\u00fdvoji mohly zp\u016fsobit probl\u00e9my. V\u010dasn\u00e1 identifikace probl\u00e9m\u016f v\u00e1m pom\u016f\u017ee dodr\u017eet harmonogram v\u00fdvoje a zabr\u00e1nit n\u00e1kladn\u00fdm chyb\u00e1m.<\/p>\n
<\/h2>\n<\/span>V\u00fdzvy testov\u00e1n\u00ed p\u0159\u00edpustnosti<\/strong><\/span><\/h2>\nTestov\u00e1n\u00ed spr\u00e1vnosti nen\u00ed bez probl\u00e9m\u016f. Software pro testov\u00e1n\u00ed spr\u00e1vnosti m\u016f\u017ee tester\u016fm pomoci identifikovat n\u011bkter\u00e9 hlavn\u00ed chyby v sestaven\u00ed p\u0159ed pokra\u010dov\u00e1n\u00edm v dal\u0161\u00edm testov\u00e1n\u00ed, ale nen\u00ed to spolehliv\u00fd zp\u016fsob, jak identifikovat v\u0161echny probl\u00e9my, kter\u00e9 by mohly nastat.<\/p>\n
Mezi probl\u00e9my testov\u00e1n\u00ed spr\u00e1vnosti pat\u0159\u00ed:<\/p>\n
\u25cf M\u00e1 pom\u011brn\u011b \u00fazk\u00fd rozsah a m\u016f\u017ee n\u011bkter\u00e9 probl\u00e9my p\u0159ehl\u00e9dnout.
\n\u25cf Testov\u00e1n\u00ed p\u0159\u00ed\u010detnosti nen\u00ed skriptov\u00e1no.
\n\u25cf V\u00fdvoj\u00e1\u0159i ne v\u017edy v\u011bd\u00ed, jak opravit chyby nalezen\u00e9 p\u0159i testov\u00e1n\u00ed spr\u00e1vnosti.
\n\u25cf Testov\u00e1n\u00ed spr\u00e1vnosti se zam\u011b\u0159uje pouze na p\u0159\u00edkazy a funkce softwaru.<\/p>\n
<\/h3>\n<\/span>M\u00e1 \u00fazkou p\u016fsobnost<\/span><\/h3>\nTestov\u00e1n\u00ed spr\u00e1vnosti m\u00e1 ve srovn\u00e1n\u00ed s mnoha jin\u00fdmi typy testov\u00e1n\u00ed velmi \u00fazk\u00fd rozsah. \u00da\u010delem testov\u00e1n\u00ed spr\u00e1vnosti je otestovat konkr\u00e9tn\u00ed funkce nebo zm\u011bny a ujistit se, \u017ee funguj\u00ed spr\u00e1vn\u011b. Krom\u011b t\u011bchto zm\u011bn nenab\u00edz\u00ed testov\u00e1n\u00ed spr\u00e1vnosti \u017e\u00e1dn\u00fd pohled na celkovou funk\u010dnost sestaven\u00ed softwaru.<\/p>\n
<\/h3>\n<\/span>Je to bez sc\u00e9n\u00e1\u0159e<\/span><\/h3>\nN\u011bkte\u0159\u00ed teste\u0159i to sice mohou pova\u017eovat za v\u00fdhodu, ale skute\u010dnost, \u017ee sanity testy nejsou skriptovan\u00e9, znamen\u00e1, \u017ee neexistuje \u017e\u00e1dn\u00e1 dokumentace, do kter\u00e9 by se mohli v budoucnu pod\u00edvat, pokud by v\u00fdvoj\u00e1\u0159i nebo teste\u0159i cht\u011bli zkontrolovat v\u00fdsledky sanity testu. Testov\u00e1n\u00ed spr\u00e1vnosti m\u00e1 jen omezen\u00e9 vyu\u017eit\u00ed, kter\u00e9 p\u0159esahuje jeho bezprost\u0159edn\u00ed dopad.<\/p>\n
<\/h3>\n<\/span>Testuje pouze funkce a p\u0159\u00edkazy<\/span><\/h3>\nTestov\u00e1n\u00ed spr\u00e1vnosti se pou\u017e\u00edv\u00e1 pouze k testov\u00e1n\u00ed funkc\u00ed a p\u0159\u00edkaz\u016f v sestaven\u00ed softwaru. P\u0159i testov\u00e1n\u00ed spr\u00e1vnosti nelze testovat fungov\u00e1n\u00ed softwaru na \u00farovni struktury n\u00e1vrhu, co\u017e znamen\u00e1, \u017ee pro v\u00fdvoj\u00e1\u0159e nen\u00ed v\u017edy snadn\u00e9 ur\u010dit, kde vznikaj\u00ed probl\u00e9my a jak je odstranit.<\/p>\n
<\/h2>\n<\/span>Charakteristiky testov\u00e1n\u00ed spr\u00e1vnosti<\/strong><\/span><\/h2>\nSanity testov\u00e1n\u00ed lze odli\u0161it od ostatn\u00edch forem testov\u00e1n\u00ed softwaru na z\u00e1klad\u011b jeho kl\u00ed\u010dov\u00fdch vlastnost\u00ed a charakteristik. Testov\u00e1n\u00ed p\u0159\u00ed\u010detnosti je mo\u017en\u00e9 definovat na z\u00e1klad\u011b jeho charakteristik, kter\u00fdmi jsou:<\/p>\n
\u25cf Jednoduch\u00e9
\n\u25cf Bez sc\u00e9n\u00e1\u0159e
\n\u25cf Nedokumentovan\u00e9
\n\u25cf Hlubok\u00e9
\n\u25cf \u00dazk\u00fd
\n\u25cf Prov\u00e1d\u011bj\u00ed teste\u0159i<\/p>\n
<\/h3>\n<\/span>Jednoduch\u00e9<\/span><\/h3>\nSanity testing je jednoduch\u00e1 forma testov\u00e1n\u00ed softwaru, kter\u00e1 se snadno navrhuje a stejn\u011b snadno prov\u00e1d\u00ed. To znamen\u00e1, \u017ee testov\u00e1n\u00ed spr\u00e1vnosti QA lze prov\u00e1d\u011bt rychle a podle pot\u0159eby, ani\u017e by testovac\u00ed t\u00fdmy musely pl\u00e1novat neform\u00e1ln\u00ed testy.<\/p>\n
<\/h3>\n<\/span>Neskriptovan\u00e9 a nedokumentovan\u00e9<\/span><\/h3>\nSanity testy jsou obvykle neskriptovan\u00e9 a nedokumentovan\u00e9, co\u017e tak\u00e9 p\u0159isp\u00edv\u00e1 k tomu, \u017ee sanity testy lze ve v\u011bt\u0161in\u011b testovac\u00edch prost\u0159ed\u00ed prov\u00e1d\u011bt neform\u00e1ln\u00edm zp\u016fsobem.<\/p>\n
Testov\u00e1n\u00ed spr\u00e1vnosti je neform\u00e1ln\u00ed proces, kter\u00fd slou\u017e\u00ed p\u0159edev\u0161\u00edm ke kontrole spr\u00e1vnosti, zda zm\u011bn\u011bn\u00e9 funkce a vlastnosti funguj\u00ed podle o\u010dek\u00e1v\u00e1n\u00ed.<\/p>\n
<\/h3>\n<\/span>Hlubok\u00e9 a \u00fazk\u00e9<\/span><\/h3>\nSanity testing je typ testov\u00e1n\u00ed softwaru, kter\u00fd je pova\u017eov\u00e1n za hlubok\u00fd a \u00fazk\u00fd. To znamen\u00e1, \u017ee testov\u00e1n\u00ed spr\u00e1vnosti zahrnuje pouze \u00fazk\u00fd pohled na sestaven\u00ed softwaru, ale jde do hloubky t\u011bch aspekt\u016f sestaven\u00ed, kter\u00e9 testuje.<\/p>\n
Nap\u0159\u00edklad teste\u0159i softwaru mohou podrobn\u011b testovat funkci jedn\u00e9 funkce, m\u00edsto aby testovali v\u0161echny z\u00e1kladn\u00ed funkce na z\u00e1kladn\u00ed \u00farovni.<\/p>\n
<\/h3>\n<\/span>Prov\u00e1d\u011bj\u00ed teste\u0159i<\/span><\/h3>\nTestov\u00e1n\u00ed spr\u00e1vnosti t\u00e9m\u011b\u0159 v\u017edy prov\u00e1d\u011bj\u00ed teste\u0159i. T\u00edm se testov\u00e1n\u00ed spr\u00e1vnosti li\u0161\u00ed od jin\u00fdch b\u011b\u017en\u00fdch forem testov\u00e1n\u00ed softwaru, jako je nap\u0159\u00edklad testov\u00e1n\u00ed kou\u0159e, kter\u00e9 mohou prov\u00e1d\u011bt bu\u010f t\u00fdmy QA, nebo v\u00fdvoj\u00e1\u0159i.<\/p>\n
<\/h2>\n<\/span>Sanity testing vs. smoke testing vs. regresn\u00ed testov\u00e1n\u00ed<\/strong><\/span><\/h2>\nO sanity testov\u00e1n\u00ed, smoke testov\u00e1n\u00ed a regresn\u00edm testov\u00e1n\u00ed se \u010dasto mluv\u00ed spole\u010dn\u011b a n\u011bkte\u0159\u00ed lid\u00e9 mohou zam\u011b\u0148ovat r\u016fzn\u00e9 typy testov\u00e1n\u00ed, pokud nech\u00e1pou rozd\u00edly mezi definic\u00ed sanity testov\u00e1n\u00ed a ostatn\u00edmi typy test\u016f.<\/p>\n
Smoke a sanity testing jsou rychl\u00e9 testy prov\u00e1d\u011bn\u00e9 za \u00fa\u010delem zji\u0161t\u011bn\u00ed, zda sestaven\u00ed softwaru funguje spr\u00e1vn\u011b. Testy spr\u00e1vnosti se v\u0161ak li\u0161\u00ed od test\u016f kou\u0159e i regresn\u00edch test\u016f.<\/p>\n