<\/span><\/h3>\n <\/p>\n
Statick\u00e9 a dynamick\u00e9 testov\u00e1n\u00ed jsou dva r\u016fzn\u00e9 p\u0159\u00edstupy k ov\u011b\u0159ov\u00e1n\u00ed softwaru, kter\u00e9 maj\u00ed sv\u00e9 siln\u00e9 a slab\u00e9 str\u00e1nky a jsou u\u017eite\u010dn\u00e9. P\u0159\u00edm\u00e1 volba mezi jedn\u00edm a druh\u00fdm nen\u00ed re\u00e1ln\u00e1, proto\u017ee maj\u00ed r\u016fzn\u00e9 funkce.<\/p>\n
Statick\u00e9 testov\u00e1n\u00ed je o proaktivit\u011b a co nej\u010dasn\u011bj\u0161\u00ed identifikaci probl\u00e9m\u016f. Jde o to naj\u00edt a vy\u0159e\u0161it probl\u00e9my d\u0159\u00edve, ne\u017e za\u010dnou.<\/p>\n
Dynamick\u00e9 testov\u00e1n\u00ed je reaktivn\u011bj\u0161\u00ed, proto\u017ee hled\u00e1 chyby spu\u0161t\u011bn\u00edm k\u00f3du. Ano, obecn\u011b je to \u010dasov\u011b i zdrojov\u011b n\u00e1ro\u010dn\u011bj\u0161\u00ed ne\u017e statick\u00e9 testov\u00e1n\u00ed. Najde v\u0161ak chyby, kter\u00e9 by jinak byly odhaleny pouze statick\u00fdm testov\u00e1n\u00edm.<\/p>\n
Skute\u010dnou odpov\u011bd\u00ed je, \u017ee d\u00edky spole\u010dn\u00e9mu statick\u00e9mu a dynamick\u00e9mu testov\u00e1n\u00ed m\u016f\u017eete zajistit, \u017ee v\u00e1\u0161 k\u00f3d a souvisej\u00edc\u00ed dokumenty jsou v po\u0159\u00e1dku a \u017ee software odpov\u00edd\u00e1 o\u010dek\u00e1v\u00e1n\u00edm zainteresovan\u00fdch stran.<\/p>\n
<\/p>\n
<\/span>Co se testuje b\u011bhem statick\u00e9ho testov\u00e1n\u00ed?<\/strong><\/span><\/h2>\n![\"R\u016fzn\u00e9](\"https:\/\/www.zaptest.com\/wp-content\/uploads\/2023\/09\/api-testing-1-jpg.webp\")
<\/p>\n
Statick\u00e9 testov\u00e1n\u00ed se zab\u00fdv\u00e1 n\u00e1vrhem, k\u00f3dem a dokumenty, kter\u00e9 tvo\u0159\u00ed v\u00e1\u0161 projekt. Poj\u010fme si rozebrat, na co si mus\u00ed teste\u0159i d\u00e1vat pozor, aby zajistili komplexn\u00ed p\u0159\u00edstup ke statick\u00e9mu testov\u00e1n\u00ed.<\/p>\n
<\/span>1. Kontrola dokumentace<\/strong><\/span><\/h3>\nJednou z prvn\u00edch \u010d\u00e1st\u00ed statick\u00e9ho testov\u00e1n\u00ed je d\u016fkladn\u00e1 kontrola dokumentace. Zde jsou n\u011bkter\u00e9 z dokument\u016f, kter\u00e9 se dostanou pod drobnohled.<\/p>\n
<\/span>Dokumenty s obchodn\u00edmi po\u017eadavky<\/strong><\/span><\/h4>\nTeste\u0159i prov\u011b\u0159\u00ed dokument s obchodn\u00edmi po\u017eadavky a zajist\u00ed, aby v\u011brn\u011b zachycoval pot\u0159eby zainteresovan\u00fdch stran a byl v souladu s obchodn\u00edmi c\u00edli.<\/p>\n
<\/span>Specifikace po\u017eadavk\u016f na software (SRS)<\/strong><\/span><\/h4>\nDokument specifikace po\u017eadavk\u016f na software (SRS) popisuje funkci a u\u017eite\u010dnost softwaru. Statick\u00e9 testov\u00e1n\u00ed prov\u011b\u0159\u00ed tento dokument a zajist\u00ed, \u017ee p\u0159esn\u011b popisuje funk\u010dnost softwaru, v\u010detn\u011b z\u00e1vislost\u00ed a u\u017eivatelsk\u00fdch rozhran\u00ed.<\/p>\n
<\/span>Projektov\u00e1 dokumentace<\/strong><\/span><\/h4>\nKontroluje se tak\u00e9, zda projektov\u00e1 dokumentace spl\u0148uje po\u017eadavky a specifikace. Teste\u0159i kontroluj\u00ed unifikovan\u00fd modelovac\u00ed jazyk (UML), datov\u00e9 toky a architektonick\u00e9 diagramy, aby se ujistili, \u017ee odpov\u00eddaj\u00ed po\u017eadavk\u016fm projektu.<\/p>\n
<\/span>Dokumenty p\u0159\u00edpad\u016f u\u017eit\u00ed a u\u017eivatelsk\u00e9 p\u0159\u00edb\u011bhy<\/strong><\/span><\/h4>\nStatick\u00e9 testov\u00e1n\u00ed tak\u00e9 zkoum\u00e1 dokumenty u\u017eivatelsk\u00fdch p\u0159\u00edpad\u016f a u\u017eivatelsk\u00e9 p\u0159\u00edb\u011bhy, aby zjistilo, jak odpov\u00eddaj\u00ed funk\u010dn\u00edm a nefunk\u010dn\u00edm aspekt\u016fm softwaru. Tyto dokumenty popisuj\u00ed \u0161\u0165astn\u00e9 cesty (zam\u00fd\u0161len\u00e9 \u00fasp\u011b\u0161n\u00e9 pou\u017eit\u00ed), alternativn\u00ed toky, okrajov\u00e9 p\u0159\u00edpady a mo\u017en\u00e9 chyby.<\/p>\n
<\/span>Testovac\u00ed p\u0159\u00edpady<\/strong><\/span><\/h4>\nTato ran\u00e1 f\u00e1ze testov\u00e1n\u00ed je p\u0159\u00edle\u017eitost\u00ed k prov\u011b\u0159en\u00ed testovac\u00edch p\u0159\u00edpad\u016f, aby bylo zaji\u0161t\u011bno jejich dostate\u010dn\u00e9 pokryt\u00ed, zdroje, vhodn\u00e9 techniky, realistick\u00e9 \u010dasov\u00e9 pl\u00e1ny atd. Nav\u00edc se v r\u00e1mci p\u0159ezkum\u016f bude zkoumat, zda jsou v\u00fdsledky testovac\u00edch p\u0159\u00edpad\u016f podrobn\u00e9 a realistick\u00e9.<\/p>\n
<\/p>\n
<\/span>2. Revize k\u00f3du<\/strong><\/span><\/h3>\nD\u00e1le bude p\u0159ezkoum\u00e1n k\u00f3d pou\u017eit\u00fd pro aplikaci. Zde jsou n\u011bkter\u00e9 z oblast\u00ed, na kter\u00e9 se testovac\u00ed t\u00fdmy zam\u011b\u0159\u00ed.<\/p>\n
<\/span>Chyby syntaxe<\/strong><\/span><\/h4>\nTeste\u0159i a v\u00fdvoj\u00e1\u0159i si k\u00f3d prohl\u00e9dnou a zkontroluj\u00ed, zda v n\u011bm nejsou chyby v syntaxi, p\u0159eklepy, nespr\u00e1vn\u00e9 n\u00e1zvy prom\u011bnn\u00fdch, chyb\u011bj\u00edc\u00ed interpunk\u010dn\u00ed znam\u00e9nka a jak\u00e9koli drobn\u00e9 \u010di v\u011bt\u0161\u00ed chyby, kter\u00e9 zp\u016fsob\u00ed chyby p\u0159i kone\u010dn\u00e9m spu\u0161t\u011bn\u00ed k\u00f3du.<\/p>\n
<\/span>Mrtv\u00fd k\u00f3d<\/strong><\/span><\/h4>\nMrtv\u00fd k\u00f3d, ozna\u010dovan\u00fd tak\u00e9 jako nedosa\u017eiteln\u00fd k\u00f3d, je \u010d\u00e1st zdrojov\u00e9ho k\u00f3du programu, kterou nelze spustit kv\u016fli probl\u00e9m\u016fm s cestou toku \u0159\u00edzen\u00ed.<\/p>\n
<\/span>Nepou\u017eit\u00e9 prom\u011bnn\u00e9<\/strong><\/span><\/h4>\nStatick\u00e9 testov\u00e1n\u00ed se zam\u011b\u0159uje tak\u00e9 na nepou\u017e\u00edvan\u00e9 prom\u011bnn\u00e9, kter\u00e9 jsou deklarov\u00e1ny, ale kompil\u00e1tor je nikdy neprovede.<\/p>\n
<\/span>Poru\u0161en\u00ed standard\u016f k\u00f3dov\u00e1n\u00ed<\/strong><\/span><\/h4>\nStandardy k\u00f3dov\u00e1n\u00ed ozna\u010duj\u00ed soubor osv\u011bd\u010den\u00fdch postup\u016f, pravidel a pokyn\u016f pro k\u00f3dov\u00e1n\u00ed v ur\u010dit\u00e9m jazyce. Statick\u00e9 testov\u00e1n\u00ed zaji\u0161\u0165uje dodr\u017eov\u00e1n\u00ed osv\u011bd\u010den\u00fdch postup\u016f, co\u017e ostatn\u00edm usnad\u0148uje \u00fapravy, opravy a aktualizace k\u00f3du.<\/p>\n
<\/span>Logick\u00e9 chyby<\/strong><\/span><\/h4>\nLogick\u00e9 chyby mohou znamenat, \u017ee zdrojov\u00fd k\u00f3d funguje nespr\u00e1vn\u011b, ale nedojde k jeho p\u00e1du. Statick\u00e9 kontroly se sna\u017e\u00ed tyto probl\u00e9my identifikovat a vy\u0159e\u0161it je\u0161t\u011b p\u0159ed spu\u0161t\u011bn\u00edm k\u00f3du.<\/p>\n
<\/span>Datov\u00e9 toky<\/strong><\/span><\/h4>\nTeste\u0159i tak\u00e9 zkoumaj\u00ed, jak data proud\u00ed do syst\u00e9mu a ze syst\u00e9mu. Tato kontrola zahrnuje v\u0161echny interakce, kter\u00e9 budou data v softwaru vyvol\u00e1vat.<\/p>\n
<\/span>\u0158\u00eddic\u00ed toky<\/strong><\/span><\/h4>\nDal\u0161\u00ed zkoumanou oblast\u00ed je tok \u0159\u00edzen\u00ed. Tato kontrola zkoum\u00e1 po\u0159ad\u00ed prov\u00e1d\u011bn\u00ed p\u0159\u00edkaz\u016f k\u00f3du a zaji\u0161\u0165uje, \u017ee se v\u011bci prov\u00e1d\u011bj\u00ed ve spr\u00e1vn\u00e9m po\u0159ad\u00ed, aby se software choval tak, jak bylo zam\u00fd\u0161leno.<\/p>\n
<\/span>Bezpe\u010dnostn\u00ed zranitelnosti<\/strong><\/span><\/h4>\nStatick\u00e9 testov\u00e1n\u00ed tak\u00e9 prozkoum\u00e1 p\u0159\u00edpadn\u00e9 bezpe\u010dnostn\u00ed chyby ve zdrojov\u00e9m k\u00f3du.<\/p>\n
<\/p>\n
<\/span>Statick\u00e9 techniky testov\u00e1n\u00ed softwaru<\/strong><\/span><\/h2>\n![\"v\u00fdhody](\"https:\/\/www.zaptest.com\/wp-content\/uploads\/2023\/09\/pexels-thisisengineering-3862619-jpg.webp\")
<\/p>\n
Nyn\u00ed, kdy\u017e v\u00edte, jak\u00e9 v\u011bci se zkoumaj\u00ed v r\u00e1mci statick\u00e9ho testov\u00e1n\u00ed, je \u010das pod\u00edvat se, jak se tyto kontroly prov\u00e1d\u011bj\u00ed.<\/p>\n
Pro komplexn\u00ed testov\u00e1n\u00ed softwaru je t\u0159eba zn\u00e1t dv\u011b z\u00e1kladn\u00ed techniky statick\u00e9ho testov\u00e1n\u00ed. Jedn\u00e1 se o proces p\u0159ezkoum\u00e1n\u00ed a statickou anal\u00fdzu.<\/p>\n
<\/p>\n
<\/span>1. Proces p\u0159ezkoum\u00e1n\u00ed p\u0159i statick\u00e9m testov\u00e1n\u00ed<\/strong><\/span><\/h3>\nProces p\u0159ezkoum\u00e1n\u00ed je prvn\u00ed \u010d\u00e1st\u00ed implementace statick\u00fdch technik v testov\u00e1n\u00ed softwaru. C\u00edlem je naj\u00edt a odstranit chyby v n\u00e1vrhu softwaru. Proces kontroly statick\u00e9ho testov\u00e1n\u00ed obvykle prob\u00edh\u00e1 ve \u010dty\u0159ech hlavn\u00edch f\u00e1z\u00edch.<\/p>\n
<\/span>Neform\u00e1ln\u00ed p\u0159ezkum<\/strong><\/span><\/h4>\nNeform\u00e1ln\u00ed revize je p\u0159esn\u011b to, co se pod t\u00edmto pojmem skr\u00fdv\u00e1: nestrukturovan\u00fd kulat\u00fd st\u016fl, kde mohou v\u00fdvoj\u00e1\u0159i, teste\u0159i a z\u00fa\u010dastn\u011bn\u00e9 strany zkoumat potenci\u00e1ln\u00ed probl\u00e9my a p\u0159edkl\u00e1dat ot\u00e1zky a n\u00e1vrhy t\u00fdkaj\u00edc\u00ed se softwaru. Je to p\u0159\u00edle\u017eitost identifikovat p\u0159\u00edpadn\u00e9 velk\u00e9 nedostatky nebo probl\u00e9my, ne\u017e p\u0159ejdete do dal\u0161\u00edch f\u00e1z\u00ed.<\/p>\n
<\/span>Pr\u016fchody<\/strong><\/span><\/h4>\nProch\u00e1zky jsou pro testovac\u00ed t\u00fdmy p\u0159\u00edle\u017eitost\u00ed j\u00edt do hloubky. \u010casto se jedn\u00e1 o experta nebo experty na danou oblast, kte\u0159\u00ed proch\u00e1zej\u00ed dokumentaci, aby se ujistili, \u017ee v\u0161e odpov\u00edd\u00e1 obchodn\u00edm a syst\u00e9mov\u00fdm po\u017eadavk\u016fm.<\/p>\n
<\/span>Vz\u00e1jemn\u00e9 hodnocen\u00ed<\/strong><\/span><\/h4>\nTento dal\u0161\u00ed krok zahrnuje vz\u00e1jemn\u00e9 zkoum\u00e1n\u00ed zdrojov\u00fdch k\u00f3d\u016f in\u017een\u00fdry, aby zjistili, zda mohou odhalit chyby, kter\u00e9 je t\u0159eba opravit p\u0159ed spu\u0161t\u011bn\u00edm softwaru.<\/p>\n
<\/span>Inspekce<\/strong><\/span><\/h4>\n