{"id":29843,"date":"2022-07-08T16:29:33","date_gmt":"2022-07-08T16:29:33","guid":{"rendered":"https:\/\/www.zaptest.com\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia"},"modified":"2022-07-08T16:29:33","modified_gmt":"2022-07-08T16:29:33","slug":"co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia","status":"publish","type":"post","link":"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia","title":{"rendered":"\u010co je agiln\u00e9 testovanie? Proces, \u017eivotn\u00fd cyklus, met\u00f3dy a implement\u00e1cia"},"content":{"rendered":"<p>Pri agilnom v\u00fdvoji softv\u00e9ru je testovanie rozhoduj\u00face pre zabezpe\u010denie pripravenosti softv\u00e9ru na produkciu. \u010co je v\u0161ak agiln\u00e1 metodika v testovan\u00ed? Agiln\u00e1 metodika testovania v porovnan\u00ed s vodop\u00e1dovou metodikou m\u00e1 podstatn\u00e9 koncep\u010dn\u00e9 rozdiely.<\/p>\n<p>Nau\u010di\u0165 sa, ako funguje \u017eivotn\u00fd cyklus agiln\u00e9ho testovania, met\u00f3dy, <a href=\"https:\/\/www.zaptest.com\/?page_id=4060\">n\u00e1stroje agiln\u00e9ho testovania softv\u00e9ru<\/a> a ako ich implementova\u0165, to v\u0161etko s\u00fa z\u00e1kladn\u00e9 faktory na vykon\u00e1vanie tohto typu testovania softv\u00e9ru.<\/p>\n<h2><\/h2>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #b90000;color:#b90000\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #b90000;color:#b90000\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 eztoc-toggle-hide-by-default' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Vyhody_agilneho_testovania_softveru\" >V\u00fdhody agiln\u00e9ho testovania softv\u00e9ru<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Setri_cas_a_peniaze\" >\u0160etr\u00ed \u010das a peniaze<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Znizuje_dokumentaciu\" >Zni\u017euje dokument\u00e1ciu<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Je_flexibilny\" >Je flexibiln\u00fd<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Poskytovanie_pravidelnej_spatnej_vazby\" >Poskytovanie pravidelnej sp\u00e4tnej v\u00e4zby<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Jednoduchsie_identifikovanie_problemov\" >Jednoduch\u0161ie identifikovanie probl\u00e9mov<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Bezne_problemy_s_agilnym_testovanim_softveru\" >Be\u017en\u00e9 probl\u00e9my s agiln\u00fdm testovan\u00edm softv\u00e9ru<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Existuje_vyssia_pravdepodobnost_chyby\" >Existuje vy\u0161\u0161ia pravdepodobnos\u0165 chyby<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Casto_sa_pridavaju_nove_funkcie\" >\u010casto sa prid\u00e1vaj\u00fa nov\u00e9 funkcie<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Prechod_od_tradicneho_k_agilnemu_testovaniu\" >Prechod od tradi\u010dn\u00e9ho k agiln\u00e9mu testovaniu<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Co_je_tradicne_testovanie\" >\u010co je tradi\u010dn\u00e9 testovanie?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Co_je_agilne_testovanie\" >\u010co je agiln\u00e9 testovanie?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Agilne_testovanie_vs_vodopadove_testovanie\" >Agiln\u00e9 testovanie vs. vodop\u00e1dov\u00e9 testovanie<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Prechod_z_vodopadoveho_na_agilne_testovanie\" >Prechod z vodop\u00e1dov\u00e9ho na agiln\u00e9 testovanie<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Pochopenie_zivotneho_cyklu_agilneho_testovania_softveru\" >Pochopenie \u017eivotn\u00e9ho cyklu agiln\u00e9ho testovania softv\u00e9ru<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Kvadrant_Jeden\" >Kvadrant Jeden<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Druhy_kvadrant\" >Druh\u00fd kvadrant<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Treti_kvadrant\" >Tret\u00ed kvadrant<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Stvrty_kvadrant\" >\u0160tvrt\u00fd kvadrant<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Agilne_metody_testovania\" >Agiln\u00e9 met\u00f3dy testovania<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Vyvoj_riadeny_spravanim_BDD\" >V\u00fdvoj riaden\u00fd spr\u00e1van\u00edm (BDD)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Vyvoj_riadeny_testovanim_TDD\" >V\u00fdvoj riaden\u00fd testovan\u00edm (TDD)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Vyvoj_riadeny_akceptacnymi_testami_ATDD\" >V\u00fdvoj riaden\u00fd akcepta\u010dn\u00fdmi testami (ATDD)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-24\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Testovanie_na_zaklade_relacie\" >Testovanie na z\u00e1klade rel\u00e1cie<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-25\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Prieskumne_testovanie\" >Prieskumn\u00e9 testovanie<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Strategie_agilneho_testovania\" >Strat\u00e9gie agiln\u00e9ho testovania<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-27\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Iteracia_0\" >Iter\u00e1cia 0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-28\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Iteracie_konstrukcie\" >Iter\u00e1cie kon\u0161trukcie<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-29\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Ukoncenie_vydania_alebo_prechodna_faza\" >Ukon\u010denie vydania alebo prechodn\u00e1 f\u00e1za<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-30\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Vyroba\" >V\u00fdroba<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-31\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#3_priklady_spolocnosti_ktore_implementovali_agilne_testovacie_metodiky\" >3 pr\u00edklady spolo\u010dnost\u00ed, ktor\u00e9 implementovali agiln\u00e9 testovacie metodiky<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-32\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Apple\" >Apple<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-33\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Microsoft\" >Microsoft<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-34\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#IBM\" >IBM<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-35\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Kontrolny_zoznam_planu_agilneho_testovania\" >Kontroln\u00fd zoznam pl\u00e1nu agiln\u00e9ho testovania<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-36\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#1_Kontroly_ciselnych_poli\" >1. Kontroly \u010d\u00edseln\u00fdch pol\u00ed<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-37\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#2_Kontroly_datovych_poli\" >2. Kontroly d\u00e1tov\u00fdch pol\u00ed<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-38\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#3_Kontroly_chyb\" >3. Kontroly ch\u00fdb<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-39\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#4_Kontroly_poli_Alpha\" >4. Kontroly pol\u00ed Alpha<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-40\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#5_Kontrolny_zoznam_pripravenosti_na_planovanie\" >5. Kontroln\u00fd zoznam pripravenosti na pl\u00e1novanie<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-41\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#6_Kontrolny_zoznam_pripravenosti\" >6. Kontroln\u00fd zoznam pripravenosti<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-42\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#7_Kontrolny_zoznam_seminara\" >7. Kontroln\u00fd zoznam semin\u00e1ra<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-43\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#8_Kontrolny_zoznam_epickeho_rozpadu\" >8. Kontroln\u00fd zoznam epick\u00e9ho rozpadu<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-44\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Agilny_testovaci_tim\" >Agiln\u00fd testovac\u00ed t\u00edm<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-45\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Kto_by_mal_byt_sucastou_agilneho_testovacieho_timu\" >Kto by mal by\u0165 s\u00fa\u010das\u0165ou agiln\u00e9ho testovacieho t\u00edmu<\/a><ul class='ez-toc-list-level-5' ><li class='ez-toc-heading-level-5'><a class=\"ez-toc-link ez-toc-heading-46\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#1_Tester\" >1. Tester<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-5'><a class=\"ez-toc-link ez-toc-heading-47\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#2_Vyvojar\" >2. V\u00fdvoj\u00e1r<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-5'><a class=\"ez-toc-link ez-toc-heading-48\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#3_Vlastnik_produktu\" >3. Vlastn\u00edk produktu<\/a><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-49\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Automatizacia_agilneho_testovania_softveru\" >Automatiz\u00e1cia agiln\u00e9ho testovania softv\u00e9ru<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-50\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Vyhody_automatizacie_agilneho_testovania_softveru\" >V\u00fdhody automatiz\u00e1cie agiln\u00e9ho testovania softv\u00e9ru<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-51\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#1_Rychlejsie_vykonavanie\" >1. R\u00fdchlej\u0161ie vykon\u00e1vanie<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-52\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#2_Opakovane_pouzitelne\" >2. Opakovane pou\u017eite\u013en\u00e9<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-53\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Rizika_automatizacie_agilnych_metodik_testovania_softveru\" >Rizik\u00e1 automatiz\u00e1cie agiln\u00fdch metod\u00edk testovania softv\u00e9ru<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-54\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#1_Nemoze_uplne_nahradit_manualne_testovanie\" >1. Nem\u00f4\u017ee \u00faplne nahradi\u0165 manu\u00e1lne testovanie<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-55\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#2_Testy_mozu_byt_nespolahlive\" >2. Testy m\u00f4\u017eu by\u0165 nespo\u013eahliv\u00e9<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-56\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#3_Moze_byt_nedostatok_ucinnych_rieseni\" >3. M\u00f4\u017ee by\u0165 nedostatok \u00fa\u010dinn\u00fdch rie\u0161en\u00ed<\/a><\/li><\/ul><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-57\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Nastroje_na_agilne_testovanie\" >N\u00e1stroje na agiln\u00e9 testovanie<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-58\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Co_robi_dobry_nastroj_na_automatizaciu_agilneho_testovania_dobrym\" >\u010co rob\u00ed dobr\u00fd n\u00e1stroj na automatiz\u00e1ciu agiln\u00e9ho testovania dobr\u00fdm?<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-59\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#1_Adekvatne_zaznamenavanie\" >1. Adekv\u00e1tne zaznamen\u00e1vanie<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-60\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#2_Uprava_testu_bez_jeho_opakovania\" >2. \u00daprava testu bez jeho opakovania<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-61\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#3_Jednoduchost_pouzivania\" >3. Jednoduchos\u0165 pou\u017e\u00edvania<\/a><\/li><\/ul><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-62\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Dalsie_veci_ktore_treba_mat_na_pamati_pri_prechode_na_agilnu_metodiku_testovania\" >\u010eal\u0161ie veci, ktor\u00e9 treba ma\u0165 na pam\u00e4ti pri prechode na agiln\u00fa metodiku testovania<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-63\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Spolupraca_je_klucova\" >Spolupr\u00e1ca je k\u013e\u00fa\u010dov\u00e1<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-64\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Vytvorenie_agilneho_testovacieho_prostredia\" >Vytvorenie agiln\u00e9ho testovacieho prostredia<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-65\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Casto_kladene_otazky\" >\u010casto kladen\u00e9 ot\u00e1zky<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-66\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Ako_funguje_kontrola_kvality_v_agilnom_prostredi\" >Ako funguje kontrola kvality v agilnom prostred\u00ed?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-67\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Ake_zrucnosti_potrebuju_agilni_testeri\" >Ak\u00e9 zru\u010dnosti potrebuj\u00fa agiln\u00ed testeri?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-68\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Ake_su_zasady_agilneho_testovania\" >Ak\u00e9 s\u00fa z\u00e1sady agiln\u00e9ho testovania?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-69\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Ake_testovanie_sa_vykonava_pocas_agile\" >Ak\u00e9 testovanie sa vykon\u00e1va po\u010das agile?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-70\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#Ako_funguje_agilne_testovanie\" >Ako funguje agiln\u00e9 testovanie?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-71\" href=\"https:\/\/www.zaptest.com\/sk\/co-je-agilne-testovanie-proces-zivotny-cyklus-metody-a-implementacia\/#ZAPTEST_pre_agilne_testovanie\" >ZAPTEST pre agiln\u00e9 testovanie<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Vyhody_agilneho_testovania_softveru\"><\/span><strong>V\u00fdhody agiln\u00e9ho testovania softv\u00e9ru<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Sp\u00f4sobov, ako m\u00f4\u017eete profitova\u0165 v\u010faka agiln\u00e9mu <a href=\"https:\/\/www.zaptest.com\/sk\">testovaniu v\u00fdvoja softv\u00e9ru<\/a>, je ve\u013ea. Prechod na agiln\u00fa metodiku v procese testovania a dodr\u017eiavanie osved\u010den\u00fdch postupov agiln\u00e9ho testovania softv\u00e9ru prin\u00e1\u0161a nieko\u013eko k\u013e\u00fa\u010dov\u00fdch v\u00fdhod.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Setri_cas_a_peniaze\"><\/span>\u0160etr\u00ed \u010das a peniaze<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Mnoh\u00e9 agiln\u00e9 testy sa daj\u00fa automatizova\u0165, \u010do v\u00e1m nielen u\u0161etr\u00ed n\u00e1klady na testy, ale je to ove\u013ea r\u00fdchlej\u0161ie ako manu\u00e1lne testovanie.<\/p>\n<p>\u010eal\u0161\u00edm sp\u00f4sobom, ako u\u0161etri\u0165 peniaze pomocou n\u00e1strojov na agiln\u00e9 testovanie softv\u00e9ru, je elimin\u00e1cia potreby duplicitn\u00fdch testov. Bez oh\u013eadu na to, ako efekt\u00edvni s\u00fa va\u0161i testeri QA, manu\u00e1lne testovanie zaberie viac \u010dasu, tak\u017ee ak chcete efekt\u00edvne a r\u00fdchle v\u00fdsledky, agiln\u00e9 metodiky v\u00e1m pom\u00f4\u017eu optimalizova\u0165 \u017eivotn\u00fd cyklus v\u00fdvoja softv\u00e9ru.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Znizuje_dokumentaciu\"><\/span>Zni\u017euje dokument\u00e1ciu<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Hoci agiln\u00e9 testovanie nevylu\u010duje dokument\u00e1ciu, je jej ove\u013ea menej. Namiesto dokumentovania ka\u017edej inform\u00e1cie, ktor\u00e9 m\u00f4\u017ee by\u0165 \u010dasovo n\u00e1ro\u010dn\u00e9, zah\u0155\u0148a stru\u010dn\u00e9 zaznamen\u00e1vanie konkr\u00e9tnych inform\u00e1ci\u00ed, ktor\u00e9 s\u00fa pr\u00ednosom pre testovac\u00ed t\u00edm.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Je_flexibilny\"><\/span>Je flexibiln\u00fd<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Jednou z najlep\u0161\u00edch vec\u00ed na agilnej metodike testovania je jej flexibilita. Je to ve\u013emi prisp\u00f4sobiv\u00e1 testovacia met\u00f3da, ktor\u00e1 v\u00e1m umo\u017e\u0148uje zmeni\u0165 \u010doko\u013evek, \u010do je potrebn\u00e9, aby ste z\u00edskali rie\u0161enie, ktor\u00e9 potrebujete po\u010das procesu testovania.<\/p>\n<p>Agiln\u00e9 testovanie je zalo\u017een\u00e9 na spolupr\u00e1ci v\u0161etk\u00fdch \u010dlenov t\u00edmu, tak\u017ee flexibilita a jednoduch\u00e1 zmena taktiky je v\u00fdznamnou v\u00fdhodou.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Poskytovanie_pravidelnej_spatnej_vazby\"><\/span>Poskytovanie pravidelnej sp\u00e4tnej v\u00e4zby<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Na rozdiel od tradi\u010dn\u00e9ho testovania, pri ktorom trv\u00e1 z\u00edskanie sp\u00e4tnej v\u00e4zby od z\u00e1kazn\u00edkov alebo koncov\u00fdch pou\u017e\u00edvate\u013eov a\u017e 18 mesiacov, agiln\u00e9 testovacie slu\u017eby umo\u017e\u0148uj\u00fa z\u00edska\u0165 sp\u00e4tn\u00fa v\u00e4zbu ka\u017ed\u00fdch nieko\u013eko t\u00fd\u017ed\u0148ov a r\u00fdchlej\u0161ie, v z\u00e1vislosti od situ\u00e1cie, f\u00e1zy v\u00fdvojov\u00e9ho procesu a pod.<\/p>\n<p>Samozrejme, \u010d\u00edm r\u00fdchlej\u0161ia je sp\u00e4tn\u00e1 v\u00e4zba po\u010das v\u00fdvoja, t\u00fdm r\u00fdchlej\u0161ie m\u00f4\u017ee t\u00edm vykona\u0165 potrebn\u00e9 zmeny a op\u00e4tovne nasadi\u0165 softv\u00e9r pre \u010fal\u0161iu sp\u00e4tn\u00fa v\u00e4zbu od z\u00e1kazn\u00edkov.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Jednoduchsie_identifikovanie_problemov\"><\/span>Jednoduch\u0161ie identifikovanie probl\u00e9mov<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Vyu\u017e\u00edvanie agilnej metodiky pri testovan\u00ed v\u00fdrazne u\u013eah\u010duje identifik\u00e1ciu ak\u00fdchko\u013evek probl\u00e9mov s produktom. V\u010faka pravideln\u00e9mu testovaniu a sp\u00e4tnej v\u00e4zbe od z\u00e1kazn\u00edkov m\u00f4\u017ee testovac\u00ed t\u00edm n\u00e1js\u0165 a odstr\u00e1ni\u0165 probl\u00e9my pri v\u00fdvoji r\u00fdchlej\u0161ie ako pri tradi\u010dn\u00fdch met\u00f3dach testovania.<\/p>\n<h2><\/h2>\n<h2><span class=\"ez-toc-section\" id=\"Bezne_problemy_s_agilnym_testovanim_softveru\"><\/span><strong>Be\u017en\u00e9 probl\u00e9my s agiln\u00fdm testovan\u00edm softv\u00e9ru<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Hoci pou\u017e\u00edvanie agiln\u00e9ho testovania softv\u00e9ru prin\u00e1\u0161a viacero v\u00fdhod, pred prechodom z tradi\u010dn\u00e9ho testovania je potrebn\u00e9 zv\u00e1\u017ei\u0165 niektor\u00e9 <a href=\"https:\/\/link.springer.com\/chapter\/10.1007\/978-981-10-7323-6_8\">v\u00fdzvy<\/a>.<\/p>\n<p><iframe loading=\"lazy\" title=\"The Purpose of Testing in Agile - Testing Benefits and Shared Responsibility For Testing\" width=\"1080\" height=\"608\" src=\"https:\/\/www.youtube.com\/embed\/J5hrIsmVA3g?feature=oembed\"  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen><\/iframe><\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Existuje_vyssia_pravdepodobnost_chyby\"><\/span>Existuje vy\u0161\u0161ia pravdepodobnos\u0165 chyby<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Jednou z nev\u00fdhod pou\u017e\u00edvania agilnej metodiky testovania je vy\u0161\u0161ia pravdepodobnos\u0165 v\u00fdskytu ch\u00fdb. Je s\u00edce v\u00fdhodn\u00e9, \u017ee sa kladie men\u0161\u00ed d\u00f4raz na d\u00f4kladn\u00fa dokument\u00e1ciu, ale pr\u00e1ve strata tohto procesu dokument\u00e1cie m\u00f4\u017ee niekedy sp\u00f4sobi\u0165, \u017ee pri testovan\u00ed sa vyskytne viac ch\u00fdb alebo sa prehliadnu.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Casto_sa_pridavaju_nove_funkcie\"><\/span>\u010casto sa prid\u00e1vaj\u00fa nov\u00e9 funkcie<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Ke\u010f\u017ee agiln\u00e9 testovanie prebieha r\u00fdchlo, nov\u00e9 funkcie produktu sa prid\u00e1vaj\u00fa r\u00fdchlej\u0161ie ako pri tradi\u010dnom testovan\u00ed. Nov\u00e9 funkcie m\u00f4\u017eu predstavova\u0165 v\u00fdzvu, preto\u017ee testovac\u00edm t\u00edmom zost\u00e1va menej \u010dasu na identifik\u00e1ciu v\u00fdvojov\u00fdch probl\u00e9mov s predch\u00e1dzaj\u00facimi funkciami pred nov\u00fdmi.<\/p>\n<h2><\/h2>\n<h2><span class=\"ez-toc-section\" id=\"Prechod_od_tradicneho_k_agilnemu_testovaniu\"><\/span><strong>Prechod od tradi\u010dn\u00e9ho k agiln\u00e9mu testovaniu<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Prechod z tradi\u010dn\u00e9ho na agiln\u00e9 testovanie si vy\u017eaduje d\u00f4kladn\u00e9 zv\u00e1\u017eenie. Pochopenie hlavn\u00fdch rozdielov medzi agilnou metodikou testovania a vodop\u00e1dovou metodikou testovania v\u00e1m pom\u00f4\u017ee lep\u0161ie pochopi\u0165, \u010do je pre va\u0161u situ\u00e1ciu lep\u0161ia vo\u013eba, a urobi\u0165 vhodn\u00e9 rozhodnutie.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Co_je_tradicne_testovanie\"><\/span><strong>\u010co je tradi\u010dn\u00e9 testovanie?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Tradi\u010dn\u00e9 testovanie, zn\u00e1me aj ako vodop\u00e1dov\u00e9 testovanie, je viac \u0161trukt\u00farovan\u00e9 ako agiln\u00e9 testovanie a vykon\u00e1va sa inkrement\u00e1lne.<\/p>\n<p>Cel\u00e9 testovanie prebieha na konci v\u00fdvoja produktu, pri\u010dom v tejto f\u00e1ze sa vykon\u00e1vaj\u00fa zmeny, po ktor\u00fdch sa proces testovania za\u010d\u00edna odznova.<\/p>\n<p>Tento vodop\u00e1dov\u00fd pr\u00edstup k testovaniu umo\u017e\u0148uje doda\u0165 v\u0161etky funkcie po f\u00e1ze implement\u00e1cie, a to naraz. Pri vodop\u00e1dovom testovan\u00ed pracuj\u00fa testeri a v\u00fdvoj\u00e1ri naj\u010dastej\u0161ie oddelene a ich cesty sa nikdy alebo len zriedkavo priamo skr\u00ed\u017eia.<\/p>\n<p>V r\u00e1mci vodop\u00e1dov\u00e9ho testovania testeri identifikuj\u00fa chyby a v\u0161etko je d\u00f4kladne zdokumentovan\u00e9, aby sa k nemu testeri a v\u00fdvoj\u00e1ri mohli vr\u00e1ti\u0165 bez toho, aby im unikli potenci\u00e1lne d\u00f4le\u017eit\u00e9 detaily.<\/p>\n<p>Projektov\u00fd mana\u017e\u00e9r je v kone\u010dnom d\u00f4sledku zodpovedn\u00fd za projekt od za\u010diatku a\u017e do konca a testeri a v\u00fdvoj\u00e1ri postupuj\u00fa pod\u013ea vopred stanoven\u00fdch krokov, aby vykonali proces testovania. Tento pr\u00edstup zhora nadol sa \u013eahko dodr\u017eiava, preto\u017ee testeri m\u00f4\u017eu prejs\u0165 do \u010fal\u0161ej f\u00e1zy a\u017e po \u00faplnom dokon\u010den\u00ed predch\u00e1dzaj\u00facej.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Co_je_agilne_testovanie\"><\/span><strong>\u010co je agiln\u00e9 testovanie?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Agiln\u00e9 testovanie sa za\u010d\u00edna po za\u010dat\u00ed v\u00fdvoja projektu. Stru\u010dne povedan\u00e9, integruje testovanie a v\u00fdvoj vo v\u0161etk\u00fdch f\u00e1zach. V\u00e4\u010d\u0161ina v\u00fdvoj\u00e1rov si tento proces predstavuje v s\u00favislosti s agilnou pyram\u00eddou testovania (viac o nej nesk\u00f4r).<\/p>\n<p>Pou\u017e\u00edvanie agilnej metodiky pri testovan\u00ed znamen\u00e1, \u017ee testovanie prebieha nepretr\u017eite po\u010das cel\u00e9ho procesu v\u00fdvoja a zah\u0155\u0148a v\u00fdvoj\u00e1rov, testerov a vlastn\u00edkov takmer v ka\u017edej f\u00e1ze.<\/p>\n<p><iframe loading=\"lazy\" title=\"What Is Agile Testing? A Software Testing FAQ and Definition Overview\" width=\"1080\" height=\"608\" src=\"https:\/\/www.youtube.com\/embed\/6Jnw1jMjSY4?feature=oembed\"  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen><\/iframe><\/p>\n<p>Testovanie sa za\u010d\u00edna pred f\u00e1zou v\u00fdvoja a pokra\u010duje po\u010das cel\u00e9ho <a href=\"https:\/\/link.springer.com\/chapter\/10.1007\/978-981-10-1415-4_2\">agiln\u00e9ho procesu testovania<\/a>, pri\u010dom sp\u00e4tn\u00e1 v\u00e4zba sa poskytuje v ka\u017edom kroku. T\u00e1to nepretr\u017eit\u00e1 sp\u00e4tn\u00e1 v\u00e4zba podporuje proces v\u00fdvoja, preto\u017ee testovac\u00ed t\u00edm nie je obmedzen\u00fd \u010daka\u0165 na produkciu, aby zistil, kde sa mohli vyskytn\u00fa\u0165 chyby.<\/p>\n<p>Zabezpe\u010denie kvality je teraz implementovan\u00e9 do agiln\u00fdch testovac\u00edch slu\u017eieb. Ka\u017ed\u00fd \u010dlen agiln\u00e9ho testovacieho t\u00edmu je zodpovedn\u00fd za identifik\u00e1ciu potenci\u00e1lnych probl\u00e9mov prostredn\u00edctvom stru\u010dnej dokument\u00e1cie a navrhovanie rie\u0161en\u00ed.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Agilne_testovanie_vs_vodopadove_testovanie\"><\/span><strong>Agiln\u00e9 testovanie vs. vodop\u00e1dov\u00e9 testovanie<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Agiln\u00e1 metodika testovania v porovnan\u00ed s vodop\u00e1dom je jednoduch\u00e1 na pochopenie. Po prv\u00e9, <a href=\"http:\/\/ku-fpg.github.io\/files\/agile-traditional.pdf\">tradi\u010dn\u00e9 testovanie<\/a> sa riadi pevne stanoven\u00fdmi po\u017eiadavkami, zatia\u013e \u010do proces agiln\u00e9ho testovania nie je pevne stanoven\u00fd. V\u010faka agiln\u00e9mu testovaniu m\u00f4\u017eete v priebehu procesu v\u00fdvoja softv\u00e9ru vykon\u00e1va\u0165 zmeny pod\u013ea vlastn\u00e9ho uv\u00e1\u017eenia.<\/p>\n<p>Vodop\u00e1dov\u00e9 testovanie sa riadi predikt\u00edvnym pr\u00edstupom, pri ktorom je \u0165a\u017ek\u00e9 implementova\u0165 zmeny, zatia\u013e \u010do agiln\u00e9 testovanie je ove\u013ea adapt\u00edvnej\u0161ie. Zatia\u013e \u010do vodop\u00e1dov\u00e9 testovanie je pr\u00edstup zhora nadol, modern\u00e9 testovanie si mo\u017eno predstavi\u0165 ako agiln\u00fa testovaciu pyram\u00eddu.<\/p>\n<p>Pyram\u00edda agiln\u00e9ho testovania je graf alebo n\u00e1vod na pou\u017e\u00edvanie automatizovan\u00e9ho testovania softv\u00e9ru. Je rozdelen\u00e1 na tri \u010dasti. V spodnej \u010dasti m\u00e1te jednotkov\u00e9 testy a testy komponentov, v strede akcepta\u010dn\u00e9 testy a v hornej \u010dasti testy grafick\u00e9ho rozhrania. Zvy\u010dajne mus\u00edte za\u010da\u0165 odspodu a postupova\u0165 a\u017e k testom grafick\u00e9ho rozhrania.<\/p>\n<p>Pri vodop\u00e1dovom testovan\u00ed prich\u00e1dza sp\u00e4tn\u00e1 v\u00e4zba a\u017e po ukon\u010den\u00ed cyklu, zatia\u013e \u010do agiln\u00fd proces testovania predpoklad\u00e1 nepretr\u017eit\u00fa sp\u00e4tn\u00fa v\u00e4zbu. Pokia\u013e ide o funk\u010dnos\u0165, tradi\u010dn\u00e9 testovanie potvrdzuje kvalitu produktu, zatia\u013e \u010do agiln\u00e9 testovanie zabezpe\u010duje r\u00fdchle dodanie produktu aj za cenu do\u010dasne ni\u017e\u0161ej funk\u010dnosti.<\/p>\n<p>V agilnom procese testovania v\u0161etci spolupracuj\u00fa v ka\u017edej f\u00e1ze testovania. Naopak, po\u010das cel\u00e9ho procesu vodop\u00e1dov\u00e9ho testovania pracuj\u00fa testeri a v\u00fdvoj\u00e1ri oddelene a pri komunik\u00e1cii sa spoliehaj\u00fa na rozsiahlu dokument\u00e1ciu.<\/p>\n<h2><\/h2>\n<h2><span class=\"ez-toc-section\" id=\"Prechod_z_vodopadoveho_na_agilne_testovanie\"><\/span><strong>Prechod z vodop\u00e1dov\u00e9ho na agiln\u00e9 testovanie<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Prechod z vodop\u00e1du na agiln\u00fa metodiku testovania nie je zlo\u017eit\u00fd, ke\u010f pochop\u00edte z\u00e1kutia agiln\u00e9ho procesu a n\u00e1strojov na testovanie softv\u00e9ru. Agiln\u00e9 testovanie m\u00f4\u017ee by\u0165 menej efekt\u00edvne bez pevn\u00e9ho pochopenia procesu. Nie je napr\u00edklad zriedkav\u00e9, \u017ee agiln\u00e9 testovacie t\u00edmy predpokladaj\u00fa, \u017ee agiln\u00e9 testovanie je viac o r\u00fdchlosti a menej o pl\u00e1novan\u00ed.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Pochopenie_zivotneho_cyklu_agilneho_testovania_softveru\"><\/span><strong>Pochopenie \u017eivotn\u00e9ho cyklu agiln\u00e9ho testovania softv\u00e9ru<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>\u017divotn\u00fd cyklus agiln\u00e9ho testovania softv\u00e9ru sa koncep\u010dne l\u00ed\u0161i od tradi\u010dn\u00e9ho testovania. Predt\u00fdm, ako pochop\u00edte agiln\u00e9 testovanie, je d\u00f4le\u017eit\u00e9 pochopi\u0165 \u017eivotn\u00fd cyklus. \u017divotn\u00fd cyklus agiln\u00e9ho testovania m\u00e1 p\u00e4\u0165 f\u00e1z.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-4102\" src=\"https:\/\/www.zaptest.com\/wp-content\/uploads\/2022\/03\/agile2-1024x622.jpg\" alt=\"osved\u010den\u00e9 postupy pre agiln\u00e9 a funk\u010dn\u00e9 testovanie automatiz\u00e1cie softv\u00e9ru\" width=\"1024\" height=\"622\"><\/p>\n<p>F\u00e1zy \u017eivotn\u00e9ho cyklu agiln\u00e9ho testovania softv\u00e9ru s\u00fa:<\/p>\n<ul>\n<li>Pos\u00fadenie vplyvu<\/li>\n<li>Agiln\u00e9 pl\u00e1novanie testovania<\/li>\n<li>Pripravenos\u0165 na vydanie<\/li>\n<li>Denn\u00e9 s\u00fastredenia<\/li>\n<li>Presk\u00famanie agility<\/li>\n<\/ul>\n<p>Ka\u017ed\u00e1 \u010das\u0165 tohto agiln\u00e9ho \u017eivotn\u00e9ho cyklu testovania je nevyhnutn\u00e1 pre priebeh cel\u00e9ho syst\u00e9mu.<\/p>\n<p>Agiln\u00e9 testovanie vyu\u017e\u00edva \u0161tyri kvadranty, ktor\u00e9 pre proces testovania vytvorili <a href=\"https:\/\/books.google.com\/books?hl=en&amp;lr=&amp;id=3UdsAQAAQBAJ&amp;oi=fnd&amp;pg=PR9&amp;dq=Lisa+Cirspin+and+Janet+Gregory&amp;ots=Drpe9tQms7&amp;sig=spHoMSdB1iGJIoXh3RJ18BYrk-U#v=onepage&amp;q=Lisa%20Cirspin%20and%20Janet%20Gregory&amp;f=false\">Lisa Crispin a Janet Gregory<\/a>. Kvadranty sl\u00fa\u017eia na pomoc agiln\u00fdm testerom pri ur\u010dovan\u00ed, ktor\u00e9 testy by sa mali vykon\u00e1va\u0165 a ako sa tieto testy vykon\u00e1vaj\u00fa.<\/p>\n<p><iframe loading=\"lazy\" title=\"ISTQB Agile Tester #43 - Agile Testing Quadrants and Test Levels\" width=\"1080\" height=\"608\" src=\"https:\/\/www.youtube.com\/embed\/_BUlNzkyH58?start=128&#038;feature=oembed\"  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen><\/iframe><\/p>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Kvadrant_Jeden\"><\/span><strong>Kvadrant<\/strong> <strong>Jeden<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Hlavn\u00fdm cie\u013eom tohto kvadrantu je intern\u00e1 kvalita k\u00f3du. Kvadrant jeden zah\u0155\u0148a v\u0161etky testy, ktor\u00e9 maj\u00fa vz\u0165ah ku kvalite k\u00f3du. Tieto testy zah\u0155\u0148aj\u00fa automatizovan\u00e9 testy, ako napr\u00edklad:<\/p>\n<ul>\n<li>Testy komponentov<\/li>\n<li>Jednotkov\u00e9 testy<\/li>\n<\/ul>\n<p>Oba typy testov s\u00fa zalo\u017een\u00e9 na technol\u00f3gii a m\u00f4\u017eu by\u0165 implementovan\u00e9 na podporu agiln\u00e9ho testovacieho t\u00edmu.<\/p>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Druhy_kvadrant\"><\/span><strong>Druh\u00fd kvadrant<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Druh\u00fd kvadrant sa zameriava na obchodn\u00e9 funkcie testovan\u00fdch produktov, ako s\u00fa automatizovan\u00e9 a manu\u00e1lne funk\u010dn\u00e9 testy pre r\u00f4zne scen\u00e1re. Testy v tomto kvadrante zah\u0155\u0148aj\u00fa:<\/p>\n<ul>\n<li>Testovanie p\u00e1rov<\/li>\n<li>Pr\u00edklady testovania pracovn\u00fdch postupov\/scen\u00e1rov<\/li>\n<li>Testovanie prototypov z h\u013eadiska pou\u017e\u00edvate\u013esk\u00e9ho z\u00e1\u017eitku<\/li>\n<\/ul>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Treti_kvadrant\"><\/span><strong>Tret\u00ed kvadrant<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Tret\u00ed kvadrant poskytuje sp\u00e4tn\u00fa v\u00e4zbu pre v\u0161etky testy vykonan\u00e9 v prvom a druhom kvadrante. V\u0161etci z\u00fa\u010dastnen\u00ed m\u00f4\u017eu produkt otestova\u0165, aby pochopili pou\u017e\u00edvate\u013esk\u00fa sk\u00fasenos\u0165.<\/p>\n<p>Testy v tomto kvadrante s\u00fa \u010dasto \u010diasto\u010dne alebo \u00faplne automatizovan\u00e9. Agiln\u00fd t\u00edm vykon\u00e1va testy ako:<\/p>\n<ul>\n<li>Prieskumn\u00e9 testovanie<\/li>\n<li>P\u00e1rov\u00e9 testovanie so z\u00e1kazn\u00edkmi<\/li>\n<li>Testovanie pou\u017eite\u013enosti<\/li>\n<li>Pou\u017e\u00edvate\u013esk\u00e9 akcepta\u010dn\u00e9 testovanie<\/li>\n<li>Spolo\u010dn\u00e9 testovanie<\/li>\n<\/ul>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Stvrty_kvadrant\"><\/span><strong>\u0160tvrt\u00fd kvadrant<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>\u0160tvrt\u00fd kvadrant je ur\u010den\u00fd pre nefunk\u010dn\u00e9 po\u017eiadavky, ako je kompatibilita, bezpe\u010dnos\u0165 a stabilita. Tento kvadrant pom\u00e1ha testerom zabezpe\u010di\u0165, aby bola aplik\u00e1cia pripraven\u00e1 poskytova\u0165 o\u010dak\u00e1van\u00fa hodnotu a funk\u010dnos\u0165.<\/p>\n<p>Testy, ktor\u00e9 s\u00fa v tomto kvadrante be\u017en\u00e9, zah\u0155\u0148aj\u00fa testovanie \u0161k\u00e1lovate\u013enosti, testovanie infra\u0161trukt\u00fary, testovanie bezpe\u010dnosti, z\u00e1\u0165a\u017eov\u00e9 testy, testovanie z\u00e1\u0165a\u017ee a testovanie migr\u00e1cie \u00fadajov.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Agilne_metody_testovania\"><\/span><strong>Agiln\u00e9 met\u00f3dy testovania<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>V agilnom testovan\u00ed existuje p\u00e4\u0165 met\u00f3d, ktor\u00e9 m\u00f4\u017eete pou\u017ei\u0165 v procese testovania. Ka\u017ed\u00e1 z t\u00fdchto met\u00f3d m\u00e1 vlastn\u00fa metodiku a poskytuje r\u00f4zne inform\u00e1cie o tom, \u010do sa testuje. Scrum testovanie sa d\u00e1 vyu\u017ei\u0165 aj v agiln\u00fdch met\u00f3dach testovania.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"Vyvoj_riadeny_spravanim_BDD\"><\/span><strong>V\u00fdvoj riaden\u00fd spr\u00e1van\u00edm (BDD)<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Prvou met\u00f3dou testovania je <a href=\"https:\/\/ieeexplore.ieee.org\/abstract\/document\/7133548\/\">v\u00fdvoj riaden\u00fd spr\u00e1van\u00edm<\/a> (BDD). BDD podporuje komunik\u00e1ciu medzi r\u00f4znymi zainteresovan\u00fdmi stranami projektu. Tento komunika\u010dn\u00fd proces pom\u00e1ha v\u0161etk\u00fdm z\u00fa\u010dastnen\u00fdm pochopi\u0165 v\u0161etky funkcie pred f\u00e1zou v\u00fdvoja.<\/p>\n<p>Pomocou BDD agiln\u00ed testeri, v\u00fdvoj\u00e1ri a analytici vytv\u00e1raj\u00fa realistick\u00e9 scen\u00e1re, ktor\u00e9 im pom\u00e1haj\u00fa v procese komunik\u00e1cie. Tieto scen\u00e1re nap\u00ed\u0161u pod\u013ea form\u00e1tu Gherkin Given\/When\/Then. V jadre form\u00e1tu je zd\u00f4raznen\u00e9, ako jednotliv\u00e9 funkcie funguj\u00fa v r\u00f4znych scen\u00e1roch s r\u00f4znymi parametrami.<\/p>\n<p><iframe loading=\"lazy\" title=\"What is Behavior Driven Development? (4 minute cartoon on BDD)\" width=\"1080\" height=\"608\" src=\"https:\/\/www.youtube.com\/embed\/ydddSkVz_a8?feature=oembed\"  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen><\/iframe><\/p>\n<p>BDD umo\u017e\u0148uje agiln\u00e9mu testovaciemu t\u00edmu vytv\u00e1ra\u0165 scen\u00e1re na z\u00e1klade predpoved\u00ed a predpokladov o tom, kde by funkcie mohli zlyha\u0165, \u010do im umo\u017e\u0148uje vykona\u0165 zlep\u0161enia e\u0161te pred f\u00e1zou v\u00fdvoja.<\/p>\n<p>V\u0161imnite si, \u017ee t\u00e1to met\u00f3da je podobn\u00e1 v\u00fdvoju riaden\u00e9mu testovan\u00edm (TDD), s t\u00fdm rozdielom, \u017ee t\u00e1to agiln\u00e1 met\u00f3da testuje kompletn\u00fa funkcionalitu, zatia\u013e \u010do TDD testuje jednotliv\u00e9 prvky.<\/p>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Vyvoj_riadeny_testovanim_TDD\"><\/span><strong>V\u00fdvoj riaden\u00fd testovan\u00edm (TDD)<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Pri TDD za\u010dnete testova\u0165 e\u0161te pred vytvoren\u00edm \u010dohoko\u013evek in\u00e9ho. Agiln\u00fd t\u00edm ur\u010d\u00ed, \u010do je potrebn\u00e9 otestova\u0165, a na z\u00e1klade toho vytvor\u00ed pr\u00edbeh pou\u017e\u00edvate\u013ea. TDD sa zvy\u010dajne za\u010d\u00edna jednotkov\u00fdm testom, po ktorom nasleduje nap\u00edsanie cel\u00e9ho pr\u00edbehu.<\/p>\n<p><iframe loading=\"lazy\" title=\"Test Driven Development - What? Why? And How?\" width=\"1080\" height=\"608\" src=\"https:\/\/www.youtube.com\/embed\/llaUBH5oayw?feature=oembed\"  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen><\/iframe><\/p>\n<p>&nbsp;<\/p>\n<p>Tento test bude pokra\u010dova\u0165 dovtedy, k\u00fdm testeri nenap\u00ed\u0161u spr\u00e1vny k\u00f3d, ktor\u00fd umo\u017en\u00ed \u00faspe\u0161n\u00e9 vykonanie testu jednotky. T\u00e1to met\u00f3da je u\u017eito\u010dn\u00e1 aj pre testy komponentov, ktor\u00e9 dobre funguj\u00fa s automatizovan\u00fdmi testovac\u00edmi n\u00e1strojmi. Tieto testy zabezpe\u010duj\u00fa, \u017ee v\u0161etky komponenty v\u00fdrobku funguj\u00fa jednotlivo.<\/p>\n<p>Agiln\u00ed testeri pou\u017e\u00edvaj\u00fa TDD na vyhodnotenie toho, ako produkt funguje v \u010dase implement\u00e1cie, a nie a\u017e po nej, ako by to bolo pri tradi\u010dnej met\u00f3de testovania.<\/p>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Vyvoj_riadeny_akceptacnymi_testami_ATDD\"><\/span><strong>V\u00fdvoj riaden\u00fd akcepta\u010dn\u00fdmi testami (ATDD)<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Z\u00e1kazn\u00edk, tester a v\u00fdvoj\u00e1r sa stretn\u00fa, aby z\u00edskali inform\u00e1cie v r\u00e1mci v\u00fdvoja riaden\u00e9ho akcepta\u010dn\u00fdmi testami<a href=\"https:\/\/books.google.com\/books?hl=en&amp;lr=&amp;id=RzOUlMjtfcEC&amp;oi=fnd&amp;pg=PR7&amp;dq=acceptance+test+driven+development&amp;ots=g95DiQvOvU&amp;sig=DXMHs2S5h9pvxWOnKT7ufuXKTTY#v=onepage&amp;q=acceptance%20test%20driven%20development&amp;f=false\">(ATDD)<\/a>. Prediskutuj\u00fa v\u0161etky tri \u00falohy a navrhn\u00fa defin\u00edciu akcepta\u010dn\u00e9ho testu.<\/p>\n<p><iframe loading=\"lazy\" title=\"ISTQB Agile Tester #40 - What is Acceptance Test Driven Development- ATDD\" width=\"1080\" height=\"608\" src=\"https:\/\/www.youtube.com\/embed\/KA4Egr1PG7I?feature=oembed\"  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen><\/iframe><\/p>\n<p>&nbsp;<\/p>\n<p>Pri ATDD z\u00e1kazn\u00edk diskutuje o probl\u00e9me, v\u00fdvoj\u00e1r sa sna\u017e\u00ed zisti\u0165, ako probl\u00e9m vyrie\u0161i\u0165, a tester h\u013ead\u00e1, \u010do by sa mohlo pokazi\u0165. ATDD je o poh\u013eade pou\u017e\u00edvate\u013ea na produkt a jeho fungovanie.<\/p>\n<p>Tieto agiln\u00e9 testy s\u00fa \u010dasto automatizovan\u00e9 a nap\u00edsan\u00e9 ako prv\u00e9. Na za\u010diatku sa im \u010dasto nedar\u00ed a potom sa na z\u00e1klade t\u00fdchto po\u010diato\u010dn\u00fdch v\u00fdsledkov robia zlep\u0161enia, ktor\u00e9 postupne zlep\u0161uj\u00fa produkt.<\/p>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Testovanie_na_zaklade_relacie\"><\/span><strong>Testovanie na z\u00e1klade rel\u00e1cie<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Cie\u013eom agiln\u00e9ho testovania zalo\u017een\u00e9ho na rel\u00e1ci\u00e1ch je zabezpe\u010di\u0165, aby softv\u00e9r pre\u0161iel komplexn\u00fdm testovan\u00edm. Obsahuje karty testov, aby agiln\u00ed testeri vedeli, \u010do sa testuje, a r\u00f4zne spr\u00e1vy, aby sa zistenia mohli zdokumentova\u0165.<\/p>\n<p><iframe loading=\"lazy\" title=\"Djuka Selendic - Session-Based Test Management and How We Made it Work\" width=\"1080\" height=\"608\" src=\"https:\/\/www.youtube.com\/embed\/tAoqScOGD-M?feature=oembed\"  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen><\/iframe><\/p>\n<p>&nbsp;<\/p>\n<p>V\u0161etky testovania v r\u00e1mci rel\u00e1cie sa vykon\u00e1vaj\u00fa v \u010dasovo rozdelen\u00fdch rel\u00e1ci\u00e1ch. Tieto stretnutia sa ukon\u010dia br\u00edfingom agiln\u00fdch testerov, scrum mana\u017e\u00e9rov a v\u00fdvoj\u00e1rov, na ktorom sa bude hovori\u0165 o piatich d\u00f4kazov\u00fdch bodoch. Scrum testovanie je mo\u017en\u00e9 upravi\u0165 pod\u013ea potreby.<\/p>\n<p>D\u00f4kazn\u00e9 body s\u00fa:<\/p>\n<ul>\n<li>\u010co bolo vykonan\u00e9 po\u010das testu<\/li>\n<li>\u010co test ur\u010duje<\/li>\n<li>Ak\u00e9ko\u013evek probl\u00e9my<\/li>\n<li>Zost\u00e1vaj\u00face testy, ktor\u00e9 treba vykona\u0165<\/li>\n<li>Ako sa tester c\u00edti pri testovan\u00ed<\/li>\n<\/ul>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Prieskumne_testovanie\"><\/span><strong>Prieskumn\u00e9 testovanie<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Nakoniec je to prieskumn\u00e9 testovanie. T\u00e1to agiln\u00e1 testovacia met\u00f3da sa zameriava na pr\u00e1cu testerov so softv\u00e9rom namiesto individu\u00e1lneho vytv\u00e1rania, pl\u00e1novania a vykon\u00e1vania r\u00f4znych testov. T\u00e1to met\u00f3da kombinuje vykon\u00e1vanie testov a f\u00e1zu n\u00e1vrhu.<\/p>\n<p><iframe loading=\"lazy\" title=\"Live Web Exploratory Technical Testing Session Example\" width=\"1080\" height=\"608\" src=\"https:\/\/www.youtube.com\/embed\/xvUKVpOCqAY?feature=oembed\"  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen><\/iframe><\/p>\n<p>Agiln\u00ed testeri sa v podstate hraj\u00fa so softv\u00e9rom, aby na\u0161li r\u00f4zne probl\u00e9my a siln\u00e9 str\u00e1nky softv\u00e9ru. Na rozdiel od in\u00fdch agiln\u00fdch testovac\u00edch met\u00f3d prieskumn\u00e9 testovanie nem\u00e1 skript. Testeri vystupuj\u00fa v \u00falohe pou\u017e\u00edvate\u013eov a m\u00f4\u017eu by\u0165 kreat\u00edvni pri r\u00f4znych scen\u00e1roch, ktor\u00e9 prehr\u00e1vaj\u00fa.<\/p>\n<p>Nebud\u00fa dokumentova\u0165 proces testovania softv\u00e9ru, ale ak testeri n\u00e1jdu probl\u00e9mov\u00fa oblas\u0165, nahl\u00e1sia ju, \u010do umo\u017en\u00ed aplikova\u0165 opravu.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Strategie_agilneho_testovania\"><\/span><strong>Strat\u00e9gie agiln\u00e9ho testovania<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Teraz, ke\u010f ste pochopili \u0161tyri kvadranty a \u017eivotn\u00fd cyklus agiln\u00e9ho testovania softv\u00e9ru, pozrime sa, \u010do zah\u0155\u0148aj\u00fa r\u00f4zne agiln\u00e9 strat\u00e9gie testovania.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"Iteracia_0\"><\/span><strong>Iter\u00e1cia 0<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Iter\u00e1cia 0, zn\u00e1ma aj ako prv\u00e1 f\u00e1za, je f\u00e1zou, v ktorej agiln\u00ed testeri vykon\u00e1vaj\u00fa nastavovacie \u00falohy. T\u00e1to agiln\u00e1 strat\u00e9gia testovania zah\u0155\u0148a nieko\u013eko zlo\u017eiek, ako je h\u013eadanie \u013eud\u00ed na testovanie, in\u0161tal\u00e1cia n\u00e1strojov, pl\u00e1novanie \u010dasu testovania a \u010fal\u0161ie.<\/p>\n<p>Kroky a osved\u010den\u00e9 postupy agiln\u00e9ho testovania softv\u00e9ru, ktor\u00e9 je potrebn\u00e9 dokon\u010di\u0165 v <a href=\"https:\/\/www.sciencedirect.com\/science\/article\/pii\/S0167642312001657\">0. iter\u00e1cii<\/a> agiln\u00e9ho testovania, s\u00fa:<\/p>\n<ul>\n<li>Zavedenie obchodnej starostlivosti o produkt<\/li>\n<li>Vypracovanie okrajov\u00fdch podmienok pre rozsah projektu<\/li>\n<li>na\u010drtn\u00fa\u0165 v\u0161etky kritick\u00e9 po\u017eiadavky, ktor\u00e9 bud\u00fa ur\u010dova\u0165 dizajn produktu<\/li>\n<li>Na\u010drtnite architekt\u00faru aspo\u0148 jedn\u00e9ho kandid\u00e1ta<\/li>\n<li>Zv\u00e1\u017ete rizik\u00e1<\/li>\n<li>Pr\u00edprava predbe\u017en\u00e9ho projektu<\/li>\n<\/ul>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Iteracie_konstrukcie\"><\/span><strong>Iter\u00e1cie kon\u0161trukcie<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Iter\u00e1cie kon\u0161trukcie s\u00fa druhou f\u00e1zou agiln\u00e9ho testovania. Hoci agiln\u00e9 testovanie prebieha po\u010das cel\u00e9ho procesu, v\u00e4\u010d\u0161ina testov sa uskuto\u010d\u0148uje v tejto f\u00e1ze. T\u00e1to f\u00e1za zah\u0155\u0148a nieko\u013eko iter\u00e1ci\u00ed, tak\u017ee testeri m\u00f4\u017eu v r\u00e1mci ka\u017edej iter\u00e1cie vytvori\u0165 rie\u0161enie pre v\u0161etko.<\/p>\n<p>Agiln\u00fd testovac\u00ed t\u00edm bude pou\u017e\u00edva\u0165 viacero postupov, ako napr\u00edklad Scrum, agiln\u00e9 modelovanie, XP a agiln\u00e9 d\u00e1ta. Pri ka\u017edej iter\u00e1cii si t\u00edm z testovania vyberie len najd\u00f4le\u017eitej\u0161ie po\u017eiadavky a implementuje ich.<\/p>\n<p>T\u00e1to f\u00e1za je definovan\u00e1 vy\u0161etrovac\u00edm testovan\u00edm a potvrdzuj\u00facim testovan\u00edm. Potvrdzovacie testovanie sl\u00fa\u017ei na overenie, \u010di produkt sp\u013a\u0148a v\u0161etky o\u010dak\u00e1vania zainteresovan\u00fdch str\u00e1n. Zah\u0155\u0148a v\u00fdvoj\u00e1rske a agiln\u00e9 akcepta\u010dn\u00e9 testovanie, ktor\u00e9 umo\u017e\u0148uje priebe\u017en\u00e9 testovanie po\u010das cel\u00e9ho \u017eivotn\u00e9ho cyklu.<\/p>\n<p>Vy\u0161etrovacie testy zis\u0165uj\u00fa v\u0161etky probl\u00e9my, ktor\u00e9 potvrdzuj\u00face testy nedok\u00e1zali identifikova\u0165, a zvy\u010dajne sa vykon\u00e1vaj\u00fa ako druh\u00e9. Tento typ agiln\u00e9ho testovania sa zaober\u00e1 v\u0161etk\u00fdmi probl\u00e9mami od z\u00e1\u0165a\u017eov\u00fdch testov a\u017e po bezpe\u010dnostn\u00e9 testy.<\/p>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Ukoncenie_vydania_alebo_prechodna_faza\"><\/span><strong>Ukon\u010denie vydania alebo prechodn\u00e1 f\u00e1za<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Tretia f\u00e1za agilnej testovacej strat\u00e9gie m\u00e1 dva n\u00e1zvy. Niektor\u00ed ju naz\u00fdvaj\u00fa prechodnou f\u00e1zou, ale v\u00e4\u010d\u0161ina \u013eud\u00ed ju naz\u00fdva koncovou f\u00e1zou uvo\u013enenia. V tejto f\u00e1ze agiln\u00ed testeri uvo\u013enia produkt do v\u00fdroby.<\/p>\n<p>Po\u010das koncovej f\u00e1zy bud\u00fa testeri \u0161koli\u0165 podporn\u00fd a prev\u00e1dzkov\u00fd person\u00e1l o produkte. Zah\u0155\u0148a tie\u017e:<\/p>\n<ul>\n<li>Marketing v\u00fdrobku na vydanie<\/li>\n<li>Re\u0161taurovanie<\/li>\n<li>Z\u00e1lohovanie<\/li>\n<li>Dokon\u010denie syst\u00e9mu<\/li>\n<li>V\u0161etka dokument\u00e1cia<\/li>\n<\/ul>\n<p>V poslednej f\u00e1ze pred produk\u010dnou f\u00e1zou m\u00f4\u017eu agiln\u00ed testeri vykona\u0165 \u00fapln\u00fd test syst\u00e9mu, aby sa uistili, \u017ee je v\u0161etko v poriadku.<\/p>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Vyroba\"><\/span><strong>V\u00fdroba<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Poslednou f\u00e1zou je v\u00fdrobn\u00e1 f\u00e1za. Ke\u010f produkt prejde v\u0161etk\u00fdmi potrebn\u00fdmi agiln\u00fdmi testami, ide do v\u00fdroby.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"3_priklady_spolocnosti_ktore_implementovali_agilne_testovacie_metodiky\"><\/span><strong>3 pr\u00edklady spolo\u010dnost\u00ed, ktor\u00e9 implementovali agiln\u00e9 testovacie metodiky<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>\u010coraz viac spolo\u010dnost\u00ed vyu\u017e\u00edva agiln\u00e9 metodiky testovania a <a href=\"https:\/\/www.zaptest.com\/hyperautomation\">hyperautomatiz\u00e1ciu<\/a>, aby zlep\u0161ili kvalitu a r\u00fdchlos\u0165 uvedenia svojich produktov na trh. Pou\u017e\u00edvaj\u00fa ich mnoh\u00e9 ve\u013ek\u00e9 technologick\u00e9 spolo\u010dnosti a toto s\u00fa tri skvel\u00e9 pr\u00edklady.<\/p>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Apple\"><\/span><strong>Apple<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Mo\u017eno si to neuvedomujete, ale <a href=\"https:\/\/internetdevels.com\/blog\/agile-lets-learn-from-the-best-ones\">Apple<\/a> je v\u00fdznamn\u00e1 spolo\u010dnos\u0165, ktor\u00e1 neust\u00e1le pou\u017e\u00edva agiln\u00e9 metodiky. Ke\u010f sa vyd\u00e1 nov\u00fd softv\u00e9r iOS a pou\u017e\u00edvatelia ho za\u010dn\u00fa pou\u017e\u00edva\u0165, spolo\u010dnos\u0165 Apple vyu\u017e\u00edva sp\u00e4tn\u00fa v\u00e4zbu od pou\u017e\u00edvate\u013eov na zlep\u0161enie softv\u00e9ru pre \u010fal\u0161iu verziu iOS.<\/p>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"Microsoft\"><\/span><strong>Microsoft<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Mnoh\u00ed konkurenti spolo\u010dnosti <a href=\"https:\/\/docs.microsoft.com\/en-us\/previous-versions\/windows\/desktop\/ee790617(v=msdn.10)\">Microsoft <\/a>u\u017e pou\u017e\u00edvali agiln\u00e9 testovanie na zlep\u0161ovanie svojich produktov a vyd\u00e1vanie nov\u00fdch verzi\u00ed, tak\u017ee prechod spolo\u010dnosti Microsoft by nemal by\u0165 prekvapuj\u00faci. Umo\u017e\u0148uje im to priebe\u017ene z\u00edskava\u0165 sp\u00e4tn\u00fa v\u00e4zbu na aktualiz\u00e1cie a pochopi\u0165, ako pou\u017e\u00edvatelia vn\u00edmaj\u00fa nov\u00e9 funkcie.<\/p>\n<h4><\/h4>\n<h4><span class=\"ez-toc-section\" id=\"IBM\"><\/span><strong>IBM<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p><a href=\"https:\/\/www.ibm.com\/downloads\/cas\/GXWXV5LR#:~:text=To%20drive%20ongoing%20successful%20Agile,automation%20within%20each%20sprint%20itself.\">IBM<\/a> vyu\u017e\u00edva agiln\u00e9 testovanie a <a href=\"https:\/\/www.zaptest.com\/sk\/kompletny-sprievodca-robotickou-automatizaciou-procesov-rpa\">robotick\u00fa automatiz\u00e1ciu procesov (RPA<\/a> ) na zefekt\u00edvnenie pr\u00e1ce v spolo\u010dnosti s viac ako 100 000 zamestnancami.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Kontrolny_zoznam_planu_agilneho_testovania\"><\/span><strong>Kontroln\u00fd zoznam pl\u00e1nu agiln\u00e9ho testovania<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-29236\" src=\"https:\/\/www.zaptest.com\/wp-content\/uploads\/2022\/07\/Software-testing-checklist-1024x681.jpeg\" alt=\"Kontroln\u00fd zoznam testovania softv\u00e9ru\" width=\"545\" height=\"363\"><\/p>\n<p>Nieko\u013eko kontroln\u00fdch zoznamov v\u00e1m pom\u00f4\u017ee zabezpe\u010di\u0165, aby ste pri vykon\u00e1van\u00ed testovania v agilnom prostred\u00ed z\u00edskali v\u0161etky potrebn\u00e9 inform\u00e1cie.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"1_Kontroly_ciselnych_poli\"><\/span><strong>1. Kontroly \u010d\u00edseln\u00fdch pol\u00ed<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Kontrola \u010d\u00edseln\u00fdch pol\u00ed je potrebn\u00e1 na zabezpe\u010denie platnosti v\u0161etk\u00fdch hodn\u00f4t na zabezpe\u010denie overenia.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"2_Kontroly_datovych_poli\"><\/span><strong>2. Kontroly d\u00e1tov\u00fdch pol\u00ed<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Skontrolujete \u0161pecifik\u00e1cie pol\u00ed, ako je de\u0148, mesiac alebo rok.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"3_Kontroly_chyb\"><\/span><strong>3. Kontroly ch\u00fdb<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Vytvorenie zoznamu s chybami umo\u017e\u0148uje \u0161pecifikova\u0165, ako sa chyba vyskytla, a analyzova\u0165 ju na \u00fa\u010dely rie\u0161enia.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"4_Kontroly_poli_Alpha\"><\/span><strong>4. Kontroly pol\u00ed Alpha<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Budete musie\u0165 skontrolova\u0165, \u010di s\u00fa \u010dierne a nepr\u00e1zdne, \u010di s\u00fa platn\u00e9 a neplatn\u00e9 znaky a \u010fal\u0161ie.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"5_Kontrolny_zoznam_pripravenosti_na_planovanie\"><\/span><strong>5. Kontroln\u00fd zoznam pripravenosti na pl\u00e1novanie<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Pred testovan\u00edm je potrebn\u00e9 napl\u00e1nova\u0165, kto bude v agilnom t\u00edme, a prideli\u0165 mu pr\u00edslu\u0161n\u00e9 \u00falohy a zodpovednosti. Budete tie\u017e musie\u0165 napl\u00e1nova\u0165 postupy testovania v agilnom prostred\u00ed.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"6_Kontrolny_zoznam_pripravenosti\"><\/span><strong>6. Kontroln\u00fd zoznam pripravenosti<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Pred odoslan\u00edm produktu na dodanie mus\u00ed agiln\u00fd t\u00edm dokon\u010di\u0165 v\u0161etky predch\u00e1dzaj\u00face \u00falohy.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"7_Kontrolny_zoznam_seminara\"><\/span><strong>7. Kontroln\u00fd zoznam semin\u00e1ra<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Tento kontroln\u00fd zoznam zah\u0155\u0148a plnenie r\u00f4znych \u00faloh a pl\u00e1novanie harmonogramu ich plnenia<\/p>\n<h4><span class=\"ez-toc-section\" id=\"8_Kontrolny_zoznam_epickeho_rozpadu\"><\/span><strong>8. Kontroln\u00fd zoznam epick\u00e9ho rozpadu<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Kontroln\u00fd zoznam pre epick\u00e9 rozdelenie je podrobnej\u0161\u00ed ako predch\u00e1dzaj\u00face zoznamy. Kontroln\u00fd zoznam epick\u00e9ho \u010dlenenia obsahuje r\u00f4zne funkcie, ktor\u00e9 treba zv\u00e1\u017ei\u0165, vr\u00e1tane:<\/p>\n<ul>\n<li>Varianty obchodn\u00fdch pravidiel<\/li>\n<li>Povaha \u017eiadosti<\/li>\n<li>Kroky pracovn\u00e9ho postupu<\/li>\n<li>Zmeny \u00fadajov<\/li>\n<li>Hlavn\u00fd \u00fa\u010dinok<\/li>\n<li>Odlo\u017eenie v\u00fdkonu<\/li>\n<li>Met\u00f3dy zad\u00e1vania \u00fadajov<\/li>\n<li>Oper\u00e1cie CRUD<\/li>\n<\/ul>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Agilny_testovaci_tim\"><\/span><strong>Agiln\u00fd testovac\u00ed t\u00edm<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Vytvorenie agiln\u00e9ho testovacieho softv\u00e9rov\u00e9ho t\u00edmu pred za\u010dat\u00edm projektu je pre hladk\u00fd priebeh testovania ve\u013emi d\u00f4le\u017eit\u00e9.<\/p>\n<p><iframe loading=\"lazy\" title=\"Who is the Agile Tester? What are the Benefits of Team Testing?\" width=\"1080\" height=\"608\" src=\"https:\/\/www.youtube.com\/embed\/uIsPk6LpIcY?feature=oembed\"  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen><\/iframe><\/p>\n<h4><span class=\"ez-toc-section\" id=\"Kto_by_mal_byt_sucastou_agilneho_testovacieho_timu\"><\/span><strong>Kto by mal by\u0165 s\u00fa\u010das\u0165ou agiln\u00e9ho testovacieho t\u00edmu<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Ka\u017ed\u00fd, kto sa podie\u013ea na \u017eivotnom cykle produktu, by mal by\u0165 \u010dlenom agiln\u00e9ho testovacieho t\u00edmu. Agiln\u00fd testovac\u00ed t\u00edm zah\u0155\u0148a testerov, v\u00fdvoj\u00e1rov a vlastn\u00edkov produktov. Ka\u017ed\u00e1 \u00faloha spolupracuje na prospech produktu a zabezpe\u010duje <a href=\"https:\/\/ieeexplore.ieee.org\/abstract\/document\/4293611\">kvalitu<\/a>.<\/p>\n<h5><span class=\"ez-toc-section\" id=\"1_Tester\"><\/span><strong>1. Tester<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h5>\n<p>Testeri s\u00fa zodpovedn\u00ed za vykon\u00e1vanie r\u00f4znych testov s\u00favisiacich s agiln\u00fdm testovac\u00edm r\u00e1mcom. Vyprac\u00favaj\u00fa stru\u010dn\u00fa dokument\u00e1ciu a stret\u00e1vaj\u00fa sa s ostatn\u00fdmi \u010dlenmi t\u00edmu s cie\u013eom vyvin\u00fa\u0165 rie\u0161enia.<\/p>\n<h5><span class=\"ez-toc-section\" id=\"2_Vyvojar\"><\/span><strong>2. V\u00fdvoj\u00e1r<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h5>\n<p>V\u00fdvoj\u00e1ri navrhuj\u00fa produkt. Pom\u00f4\u017eu testerom pri h\u013eadan\u00ed rie\u0161en\u00ed ch\u00fdb, ke\u010f sa vyskytn\u00fa, a z\u00e1rove\u0148 zabezpe\u010dia, aby boli vlastn\u00edci produktu spokojn\u00ed s kone\u010dn\u00fdm produktom.<\/p>\n<h5><span class=\"ez-toc-section\" id=\"3_Vlastnik_produktu\"><\/span><strong>3. Vlastn\u00edk produktu<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h5>\n<p>D\u00f4le\u017eit\u00fa \u00falohu v agilnom testovacom t\u00edme zohr\u00e1vaj\u00fa aj vlastn\u00edci produktov, ktor\u00ed sa podie\u013eaj\u00fa na v\u0161etk\u00fdch kone\u010dn\u00fdch rozhodnutiach na z\u00e1klade vstupov od testerov a v\u00fdvoj\u00e1rov.<\/p>\n<h2><\/h2>\n<h2><span class=\"ez-toc-section\" id=\"Automatizacia_agilneho_testovania_softveru\"><\/span><strong>Automatiz\u00e1cia agiln\u00e9ho testovania softv\u00e9ru<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>V\u00fdvoj\u00e1ri m\u00f4\u017eu automatizova\u0165 mnoh\u00e9 aspekty agiln\u00e9ho testovania. Automatizovan\u00fd n\u00e1stroj na agiln\u00e9 testovanie z dlhodob\u00e9ho h\u013eadiska u\u0161etr\u00ed ve\u013ea \u010dasu a pe\u0148az\u00ed.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Vyhody_automatizacie_agilneho_testovania_softveru\"><\/span><strong>V\u00fdhody automatiz\u00e1cie agiln\u00e9ho testovania softv\u00e9ru<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Automatiz\u00e1cia agiln\u00e9ho testovania softv\u00e9ru m\u00e1 mnoho <a href=\"https:\/\/www.researchgate.net\/profile\/S-Mantha\/publication\/261017281_Agile_Methodology_Adoption_Benefits_and_Constraints\/links\/582e930d08ae102f072dbb05\/Agile-Methodology-Adoption-Benefits-and-Constraints.pdf\">v\u00fdhod pre<\/a> zlep\u0161enie procesu testovania aj celkovej kvality produktu.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"1_Rychlejsie_vykonavanie\"><\/span><strong>1. R\u00fdchlej\u0161ie vykon\u00e1vanie<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Automatizovan\u00e9 agiln\u00e9 testovacie n\u00e1stroje m\u00f4\u017eu ur\u00fdchli\u0165 realiz\u00e1ciu. R\u00fdchlej\u0161ie z\u00edskate v\u00fdsledky a sp\u00e4tn\u00fa v\u00e4zbu, v\u010faka \u010domu r\u00fdchlej\u0161ie vypracujete rie\u0161enia probl\u00e9mov.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"2_Opakovane_pouzitelne\"><\/span><strong>2. Opakovane pou\u017eite\u013en\u00e9<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Testovanie v\u00fdvoja softv\u00e9ru m\u00f4\u017ee by\u0165 v\u0161edn\u00e9. Opakovan\u00e9 vykon\u00e1vanie t\u00fdch ist\u00fdch testov m\u00f4\u017ee by\u0165 \u00fanavn\u00e9, preto pou\u017eitie n\u00e1stroja na automatizovan\u00e9 agiln\u00e9 testovanie m\u00f4\u017ee t\u00fato \u00falohu u\u013eah\u010di\u0165 t\u00fdm, \u017ee sa ten ist\u00fd test pou\u017eije opakovane.<\/p>\n<p>Podobne ako <a href=\"https:\/\/www.zaptest.com\/rpa\">n\u00e1stroje RPA<\/a>, aj t\u00e1to metodika eliminuje mno\u017estvo opakuj\u00facich sa \u00faloh.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Rizika_automatizacie_agilnych_metodik_testovania_softveru\"><\/span><strong>Rizik\u00e1 automatiz\u00e1cie agiln\u00fdch metod\u00edk testovania softv\u00e9ru<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Tak ako pri v\u0161etkom, aj pri automatiz\u00e1cii testov agiln\u00e9ho softv\u00e9ru existuj\u00fa rizik\u00e1.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"1_Nemoze_uplne_nahradit_manualne_testovanie\"><\/span><strong>1. Nem\u00f4\u017ee \u00faplne nahradi\u0165 manu\u00e1lne testovanie<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Hoci v\u00fdhody automatiz\u00e1cie agiln\u00fdch testovac\u00edch procesov v\u00fdrazne preva\u017euj\u00fa nad ich obmedzeniami, automatizovan\u00e9 testy nie s\u00fa \u00fapln\u00fdm rie\u0161en\u00edm. Automatiz\u00e1cia dok\u00e1\u017ee len ve\u013emi m\u00e1lo, tak\u017ee sa st\u00e1le budete musie\u0165 spolieha\u0165 na manu\u00e1lne testovanie, ktor\u00e9 dopln\u00ed proces automatiz\u00e1cie testovania.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"2_Testy_mozu_byt_nespolahlive\"><\/span><strong>2. Testy m\u00f4\u017eu by\u0165 nespo\u013eahliv\u00e9<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Pokia\u013e ide o automatizovan\u00e9 testy, nespo\u013eahlivos\u0165 predstavuje zna\u010dn\u00fd probl\u00e9m. Testovac\u00ed t\u00edm bude musie\u0165 venova\u0165 zv\u00fd\u0161en\u00fa pozornos\u0165 falo\u0161ne pozit\u00edvnym v\u00fdsledkom a chyb\u00e1m pri testovan\u00ed.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"3_Moze_byt_nedostatok_ucinnych_rieseni\"><\/span><strong>3. M\u00f4\u017ee by\u0165 nedostatok \u00fa\u010dinn\u00fdch rie\u0161en\u00ed<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>\u010eal\u0161\u00edm probl\u00e9mom automatizovan\u00fdch testov je, \u017ee nie v\u017edy poskytuj\u00fa adekv\u00e1tne odpovede na v\u00fdzvy. Automatizovan\u00fdm testom \u010dasto ch\u00fdbaj\u00fa odborn\u00e9 znalosti na vytvorenie rie\u0161en\u00ed.<\/p>\n<h2><\/h2>\n<h2><span class=\"ez-toc-section\" id=\"Nastroje_na_agilne_testovanie\"><\/span><strong>N\u00e1stroje na agiln\u00e9 testovanie<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Hoci je k dispoz\u00edcii nieko\u013eko agiln\u00fdch testovac\u00edch n\u00e1strojov, niektor\u00e9 s\u00fa lep\u0161ie ako in\u00e9.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-28646\" src=\"https:\/\/www.zaptest.com\/wp-content\/uploads\/2022\/06\/Screenshot-2022-06-18-at-11.42.58-1024x641.png\" alt=\"\u010casto kladen\u00e9 ot\u00e1zky o automatiz\u00e1cii funk\u010dn\u00e9ho testovania\" width=\"1024\" height=\"641\" srcset=\"https:\/\/www.zaptest.com\/wp-content\/uploads\/2022\/06\/Screenshot-2022-06-18-at-11.42.58-980x614.png 980w, https:\/\/www.zaptest.com\/wp-content\/uploads\/2022\/06\/Screenshot-2022-06-18-at-11.42.58-480x301.png 480w\" sizes=\"(min-width: 0px) and (max-width: 480px) 480px, (min-width: 481px) and (max-width: 980px) 980px, (min-width: 981px) 1024px, 100vw\" \/><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Co_robi_dobry_nastroj_na_automatizaciu_agilneho_testovania_dobrym\"><\/span><strong>\u010co rob\u00ed dobr\u00fd n\u00e1stroj na automatiz\u00e1ciu agiln\u00e9ho testovania dobr\u00fdm?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Ako rozozn\u00e1te vynikaj\u00faci n\u00e1stroj na automatiz\u00e1ciu agiln\u00e9ho testovania od neefekt\u00edvneho? Tu je nieko\u013eko tipov.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"1_Adekvatne_zaznamenavanie\"><\/span><strong>1. Adekv\u00e1tne zaznamen\u00e1vanie<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>V r\u00e1mci agiln\u00e9ho procesu testovania softv\u00e9ru v\u00e1m kvalitn\u00fd n\u00e1stroj na automatizovan\u00e9 testovanie poskytne primeran\u00fa dokument\u00e1ciu v\u0161etk\u00fdch procesov a v\u00fdsledkov testov. Takto m\u00f4\u017eete jasne pochopi\u0165, kde sa vyskytuj\u00fa chyby a pre\u010do.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"2_Uprava_testu_bez_jeho_opakovania\"><\/span><strong>2. \u00daprava testu bez jeho opakovania<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Po vykonan\u00ed testu umo\u017en\u00ed dobr\u00fd automatiza\u010dn\u00fd n\u00e1stroj \u00fapravy bez toho, aby bolo potrebn\u00e9 \u00faplne prep\u00edsa\u0165 k\u00f3d alebo predch\u00e1dzaj\u00face testy.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"3_Jednoduchost_pouzivania\"><\/span><strong>3. Jednoduchos\u0165 pou\u017e\u00edvania<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Vzh\u013eadom na zapojenie \u010dlenov t\u00edmu s r\u00f4znymi \u00farov\u0148ami technick\u00fdch zru\u010dnost\u00ed do procesu testovania by sa mal agiln\u00fd testovac\u00ed n\u00e1stroj \u013eahko nau\u010di\u0165, nemal by vy\u017eadova\u0165 \u017eiadne osobitn\u00e9 sk\u00fasenosti s k\u00f3dovan\u00edm, mal by poskytova\u0165 bohat\u00e9 funkcie vo ve\u013emi intuit\u00edvnom rozhran\u00ed a umo\u017e\u0148ova\u0165 jednoduch\u00fa spolupr\u00e1cu a zdie\u013eanie inform\u00e1ci\u00ed.<\/p>\n<p>Hoci technick\u00e1 str\u00e1nka a funk\u010dnos\u0165 n\u00e1stroja s\u00fa samozrejme nevyhnutn\u00e9, tri vy\u0161\u0161ie uveden\u00e9 z\u00e1sady predstavuj\u00fa pilier ka\u017ed\u00e9ho agiln\u00e9ho testovacieho procesu, a preto mus\u00ed ka\u017ed\u00fd agiln\u00fd testovac\u00ed n\u00e1stroj sp\u013a\u0148a\u0165 tieto podmienky.<\/p>\n<h2><\/h2>\n<h2><span class=\"ez-toc-section\" id=\"Dalsie_veci_ktore_treba_mat_na_pamati_pri_prechode_na_agilnu_metodiku_testovania\"><\/span><strong>\u010eal\u0161ie veci, ktor\u00e9 treba ma\u0165 na pam\u00e4ti pri prechode na agiln\u00fa metodiku testovania<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Predt\u00fdm, ako \u00faplne prejdete na pou\u017e\u00edvanie agiln\u00e9ho testovacieho r\u00e1mca, mali by ste ma\u0165 na pam\u00e4ti nieko\u013eko vec\u00ed.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Spolupraca_je_klucova\"><\/span>Spolupr\u00e1ca je k\u013e\u00fa\u010dov\u00e1<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Jednou z hlavn\u00fdch zlo\u017eiek agilnej strat\u00e9gie testovania je spolupr\u00e1ca. Zatia\u013e \u010do pri tradi\u010dnom testovan\u00ed pracuj\u00fa testeri a v\u00fdvoj\u00e1ri oddelene, agiln\u00e1 metodika predpoklad\u00e1, \u017ee teraz bud\u00fa \u00fazko spolupracova\u0165 po\u010das cel\u00e9ho projektu testovania.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Vytvorenie_agilneho_testovacieho_prostredia\"><\/span>Vytvorenie agiln\u00e9ho testovacieho prostredia<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Efekt\u00edvna spolupr\u00e1ca nie je mo\u017en\u00e1 bez agiln\u00e9ho testovacieho prostredia, ktor\u00e9 ju podporuje. \u010ci u\u017e ide o vytvorenie vyhraden\u00e9ho pracovn\u00e9ho priestoru pre agiln\u00fd testovac\u00ed t\u00edm, zabezpe\u010denie lep\u0161\u00edch komunika\u010dn\u00fdch kan\u00e1lov alebo ak\u00e9ko\u013evek in\u00e9 relevantn\u00e9 opatrenia, prostredie pre spolo\u010dn\u00e9 testovanie je potrebn\u00e9 a nevyhnutn\u00e9.<\/p>\n<h2><\/h2>\n<h2><span class=\"ez-toc-section\" id=\"Casto_kladene_otazky\"><\/span><strong>\u010casto kladen\u00e9 ot\u00e1zky<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Pre \u010fal\u0161ie ot\u00e1zky o agilnom testovan\u00ed uv\u00e1dzame nieko\u013eko odpoved\u00ed na naj\u010dastej\u0161ie kladen\u00e9 ot\u00e1zky.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Ako_funguje_kontrola_kvality_v_agilnom_prostredi\"><\/span>Ako funguje kontrola kvality v agilnom prostred\u00ed?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>V ide\u00e1lnom pr\u00edpade agiln\u00fd proces testovania zah\u0155\u0148a zabezpe\u010denie kvality v celom procese. Agiln\u00ed testeri a v\u00fdvoj\u00e1ri sa bud\u00fa presne riadi\u0165 pokynmi klienta a na z\u00e1klade testovania vykonaj\u00fa zmeny s cie\u013eom zabezpe\u010di\u0165 a zv\u00fd\u0161i\u0165 kvalitu.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Ake_zrucnosti_potrebuju_agilni_testeri\"><\/span>Ak\u00e9 zru\u010dnosti potrebuj\u00fa agiln\u00ed testeri?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>V\u0161etci agiln\u00ed testeri by mali ma\u0165 zru\u010dnosti v oblasti automatiz\u00e1cie testovania, akcept\u00e1cie v\u00fdvoja riaden\u00e9ho testovan\u00edm, v\u00fdvoja riaden\u00e9ho testovan\u00edm, testovania \u010diernej skrinky, bielej skrinky a testovania zalo\u017een\u00e9ho na sk\u00fasenostiach. Je pre nich prospe\u0161n\u00e9, ak maj\u00fa snahu r\u00e1s\u0165, preto\u017ee proces testovania, postupy a technol\u00f3gie sa vyv\u00edjaj\u00fa r\u00fdchlos\u0165ou blesku.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Ake_su_zasady_agilneho_testovania\"><\/span>Ak\u00e9 s\u00fa z\u00e1sady agiln\u00e9ho testovania?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Osem agiln\u00fdch princ\u00edpov testovania je kontinu\u00e1lne testovanie, kontinu\u00e1lna sp\u00e4tn\u00e1 v\u00e4zba, zapojenie cel\u00e9ho t\u00edmu, r\u00fdchla sp\u00e4tn\u00e1 v\u00e4zba, vysok\u00e1 \u00farove\u0148 kvality softv\u00e9ru, menej dokument\u00e1cie, testovanie riaden\u00e9 testami a spokojnos\u0165 z\u00e1kazn\u00edka.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Ake_testovanie_sa_vykonava_pocas_agile\"><\/span>Ak\u00e9 testovanie sa vykon\u00e1va po\u010das agile?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Testovanie, ktor\u00e9 prebieha v r\u00e1mci agiln\u00e9ho pr\u00edstupu, zah\u0155\u0148a z\u00e1\u0165a\u017eov\u00e9 testy, testy komponentov, jednotkov\u00e9 testy a \u010fal\u0161ie.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Ako_funguje_agilne_testovanie\"><\/span>Ako funguje agiln\u00e9 testovanie?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>V procese agiln\u00e9ho testovania softv\u00e9ru testeri a v\u00fdvoj\u00e1ri spolupracuj\u00fa na priebe\u017enom testovan\u00ed r\u00f4znych \u010dast\u00ed produktu. Agiln\u00fd t\u00edm m\u00f4\u017ee identifikova\u0165 a opravi\u0165 chyby pri sk\u00faman\u00ed sp\u00e4tnej v\u00e4zby od z\u00e1kazn\u00edkov.<\/p>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"ZAPTEST_pre_agilne_testovanie\"><\/span><strong>ZAPTEST pre agiln\u00e9 testovanie<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Jednou z v\u00fdhod pou\u017e\u00edvania <a href=\"https:\/\/youtu.be\/zJnaNVSnF3Q\">ZAPTEST-u v agilnom testovan\u00ed<\/a> je mo\u017enos\u0165 vytv\u00e1ra\u0165 automatizovan\u00e9 skripty u\u017e vo f\u00e1ze n\u00e1vrhu produktu s pou\u017eit\u00edm akejko\u013evek formy grafick\u00fdch artefaktov, ako s\u00fa n\u00e1\u010drty na tabuli, wireframy, obr\u00e1zky v PowerPointe at\u010f. ZAPTEST umo\u017e\u0148uje konvertova\u0165 tieto obr\u00e1zky na automatiza\u010dn\u00e9 objekty, ktor\u00e9 sa pou\u017e\u00edvaj\u00fa v programe Autoamtors na zostavenie skriptov pred v\u00fdvojom skuto\u010dn\u00fdch softv\u00e9rov\u00fdch aplik\u00e1ci\u00ed. ZAPTEST pon\u00faka aj automatick\u00e9 vytv\u00e1ranie dokument\u00e1cie a paraleln\u00e9 vykon\u00e1vanie testov na v\u0161etk\u00fdch po\u017eadovan\u00fdch platform\u00e1ch. Tento pr\u00edstup d\u00e1va testovac\u00edm t\u00edmom n\u00e1skok pred pl\u00e1nom a umo\u017e\u0148uje testovanie a vyd\u00e1vanie aplik\u00e1ci\u00ed Just-In-Time.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Pri agilnom v\u00fdvoji softv\u00e9ru je testovanie rozhoduj\u00face pre zabezpe\u010denie pripravenosti softv\u00e9ru na produkciu. \u010co je v\u0161ak agiln\u00e1 metodika v testovan\u00ed? Agiln\u00e1 metodika testovania v porovnan\u00ed s vodop\u00e1dovou metodikou m\u00e1 podstatn\u00e9 koncep\u010dn\u00e9 rozdiely. Nau\u010di\u0165 sa, ako funguje \u017eivotn\u00fd cyklus agiln\u00e9ho testovania, met\u00f3dy, n\u00e1stroje agiln\u00e9ho testovania softv\u00e9ru a ako ich implementova\u0165, to v\u0161etko s\u00fa z\u00e1kladn\u00e9 faktory na [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":15681,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_robots_primary_cat":"none","_seopress_titles_title":"\u010co je agiln\u00e9 testovanie? Proces, \u017eivotn\u00fd cyklus, met\u00f3dy a bud\u00facnos\u0165","_seopress_titles_desc":"Od v\u00fdhod, v\u00fdziev a prechodu z tradi\u010dn\u00e9ho na agiln\u00e9 testovanie a\u017e po n\u00e1stroje agiln\u00e9ho testovania po\u010das cel\u00e9ho \u017eivotn\u00e9ho cyklu sa dozviete v\u0161etko, \u010do potrebujete vedie\u0165 o agilnom testovan\u00ed softv\u00e9ru!","_seopress_robots_index":"","_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","footnotes":"","beyondwords_generate_audio":"","beyondwords_integration_method":"","beyondwords_project_id":"","beyondwords_content_id":"","beyondwords_preview_token":"","beyondwords_player_content":"","beyondwords_player_style":"","beyondwords_language_code":"","beyondwords_language_id":"","beyondwords_title_voice_id":"","beyondwords_body_voice_id":"","beyondwords_summary_voice_id":"","beyondwords_error_message":"","beyondwords_disabled":"","beyondwords_delete_content":"","beyondwords_podcast_id":"","beyondwords_hash":"","publish_post_to_speechkit":"","speechkit_hash":"","speechkit_generate_audio":"","speechkit_project_id":"","speechkit_podcast_id":"","speechkit_error_message":"","speechkit_disabled":"","speechkit_access_key":"","speechkit_error":"","speechkit_info":"","speechkit_response":"","speechkit_retries":"","speechkit_status":"","speechkit_updated_at":"","_speechkit_link":"","_speechkit_text":""},"categories":[444],"tags":[],"class_list":{"0":"post-29843","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-typy-testovania-softveru-sk"},"acf":{"short_name":""},"_links":{"self":[{"href":"https:\/\/www.zaptest.com\/sk\/wp-json\/wp\/v2\/posts\/29843","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.zaptest.com\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.zaptest.com\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.zaptest.com\/sk\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.zaptest.com\/sk\/wp-json\/wp\/v2\/comments?post=29843"}],"version-history":[{"count":0,"href":"https:\/\/www.zaptest.com\/sk\/wp-json\/wp\/v2\/posts\/29843\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.zaptest.com\/sk\/wp-json\/wp\/v2\/media\/15681"}],"wp:attachment":[{"href":"https:\/\/www.zaptest.com\/sk\/wp-json\/wp\/v2\/media?parent=29843"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.zaptest.com\/sk\/wp-json\/wp\/v2\/categories?post=29843"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.zaptest.com\/sk\/wp-json\/wp\/v2\/tags?post=29843"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}