{"id":31264,"date":"2019-10-31T21:40:21","date_gmt":"2019-10-31T18:40:21","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kto-otvetit-za-kachestvo\/"},"modified":"2019-10-31T21:40:21","modified_gmt":"2019-10-31T18:40:21","slug":"kto-otvetit-za-kachestvo","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kto-otvetit-za-kachestvo","title":{"rendered":"Kush do t\u00eb p\u00ebrgjigjet p\u00ebr cil\u00ebsin\u00eb?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u00ebrsh\u00ebndetje, Habr!<\/p>\n

Kemi nj\u00eb tem\u00eb t\u00eb re t\u00eb r\u00ebnd\u00ebsishme - zhvillimi cil\u00ebsor i produkteve IT. Shpesh flasim n\u00eb HighLoad++ se si t\u00eb b\u00ebjm\u00eb sh\u00ebrbimet e ngarkuara t\u00eb shpejta, nd\u00ebrsa n\u00eb Frontend Conf - nj\u00eb nd\u00ebrfaqe p\u00ebrdoruesi fantastike q\u00eb nuk ngadal\u00ebson. Rregullisht kemi tema p\u00ebr testimin, dhe n\u00eb DevOpsConf flasim p\u00ebr integrimin e proceseve t\u00eb ndryshme, p\u00ebrfshir\u00eb testimin. Por p\u00ebr at\u00eb q\u00eb mund t\u00eb quhet cil\u00ebsi n\u00eb p\u00ebrgjith\u00ebsi dhe si t\u00eb punojm\u00eb kompleks mbi t\u00eb - nuk kemi.<\/p>\n

Do ta rregullojm\u00eb k\u00ebt\u00eb n\u00eb QualityConf<\/a><\/noindex>\u00a0\u2014 do t\u00eb zhvillojm\u00eb kultur\u00ebn e mendimit p\u00ebr cil\u00ebsin\u00eb e produktit p\u00ebrfundimtar p\u00ebr p\u00ebrdoruesin n\u00eb \u00e7do faz\u00eb t\u00eb zhvillimit. Nj\u00eb zakon p\u00ebr t\u00eb mos u p\u00ebrqendruar vet\u00ebm n\u00eb zon\u00ebn ton\u00eb t\u00eb p\u00ebrgjegj\u00ebsis\u00eb dhe p\u00ebr ta lidhur cil\u00ebsin\u00eb jo vet\u00ebm me testuesit.<\/p>\n

Posht\u00eb do t\u00eb flasim me kryetarin e komitetit programor, drejtorin e testimit n\u00eb Tinkoff.Biznes, krijuesin e komunitetit QA n\u00eb gjuh\u00ebn ruse Anastasija Aseeva-Nguen<\/b> p\u00ebr gjendjen e industris\u00eb QA dhe misionin e konferenc\u00ebs s\u00eb re.<\/p>\n

\"Kush
\n<\/a><\/noindex>
\n\u2014 Nastya, p\u00ebrsh\u00ebndetje. T\u00eb lutem, trego pak p\u00ebr veten.<\/em><\/strong><\/p>\n

\"KushAnastasia<\/strong>: Un\u00eb drejtoj testimin n\u00eb bank\u00eb, p\u00ebrgjigjem p\u00ebr nj\u00eb ekip shum\u00eb t\u00eb madh - kemi m\u00eb shum\u00eb se 90 njer\u00ebz. Ne kemi nj\u00eb linj\u00eb t\u00eb r\u00ebnd\u00ebsishme biznesi, ne p\u00ebrgjigjemi p\u00ebr ekosistemin p\u00ebr personat juridik\u00eb.<\/p>\n

Kam studiuar n\u00eb mekanik\u00eb dhe matematik\u00eb dhe fillimisht doja t\u00eb b\u00ebhesha programues. Por kur m\u00eb erdhi nj\u00eb ofert\u00eb interesante, vendosa t\u00eb provoja veten si testuese. Si\u00e7 \u00ebsht\u00eb e \u00e7uditshme, kjo u b\u00eb thirrja ime. Tani e shoh t\u00eb gjith\u00eb pun\u00ebn time n\u00eb k\u00ebt\u00eb industri.<\/p>\n

Un\u00eb jam nj\u00eb adhurues i zellsh\u00ebm i disiplin\u00ebs s\u00eb Quality Assurance. M\u00eb intereson se \u00e7far\u00eb produkte krijohen, si i kushtohet r\u00ebnd\u00ebsi cil\u00ebsis\u00eb n\u00eb kompani, n\u00eb ekip dhe n\u00eb p\u00ebrgjith\u00ebsi n\u00eb procesin e zhvillimit.<\/p><\/blockquote>\n

\nP\u00ebr mua \u00ebsht\u00eb e qart\u00eb se komuniteti n\u00eb k\u00ebt\u00eb drejtim nuk \u00ebsht\u00eb mjaft i pjekur<\/strong>, s\u00eb paku n\u00eb Rusi. Nuk e kuptojm\u00eb gjithmon\u00eb se sigurimi i cil\u00ebsis\u00eb nuk \u00ebsht\u00eb vet\u00ebm fakti i testimit t\u00eb aplikacionit sipas k\u00ebrkesave. Do t\u00eb doja t\u00eb ndryshoja k\u00ebt\u00eb situat\u00eb.<\/p>\n

\u2014 Ti p\u00ebrdor fjal\u00ebt Quality Assurance dhe testim. N\u00eb syt\u00eb e nj\u00eb lajthit\u00ebsi, k\u00ebto dy terma shpesh i p\u00ebrfshijn\u00eb nj\u00ebri-tjetrin. \u00c7far\u00eb i ndan ato, n\u00ebse e shqyrton thell\u00eb?<\/em><\/strong><\/p>\n

Anastasija:<\/strong> N\u00eb shum\u00eb raste nuk dallohen. Testimi \u00ebsht\u00eb nj\u00eb pjes\u00eb e disiplin\u00ebs s\u00eb Sigurimit t\u00eb Cil\u00ebsis\u00eb, kjo \u00ebsht\u00eb nj\u00eb aktivitet i drejtp\u00ebrdrejt\u00eb \u2013 vet\u00eb fakti q\u00eb un\u00eb po testoj di\u00e7ka. Ka shum\u00eb lloje testimi n\u00eb t\u00eb v\u00ebrtet\u00eb, dhe p\u00ebr lloje t\u00eb ndryshme testimi jan\u00eb p\u00ebrgjegj\u00ebs njer\u00ebz t\u00eb ndrysh\u00ebm. Por, n\u00eb Rusi, kur erdhi vala e outsourcing-ut q\u00eb ofronte testues p\u00ebr kompani, testimi u kufizua n\u00eb nj\u00eb lloj t\u00eb vet\u00ebm.<\/p>\n

N\u00eb shumic\u00ebn e rasteve kufizohen vet\u00ebm n\u00eb testimin funksional: kontrollojn\u00eb n\u00ebse ajo q\u00eb kan\u00eb koduar zhvilluesit p\u00ebrputhet me specifikimin dhe gjith\u00e7ka.<\/p>\n

\u2014 Trego, t\u00eb lutem, cilat jan\u00eb disiplinat e tjera t\u00eb sigurimit t\u00eb cil\u00ebsis\u00eb? \u00c7far\u00eb tjet\u00ebr p\u00ebrve\u00e7 testimit p\u00ebrfshihet k\u00ebtu?<\/em><\/strong><\/p>\n

Anastasia<\/strong>: Sigurimi i Cil\u00ebsis\u00eb \u00ebsht\u00eb, para s\u00eb gjithash, p\u00ebr krijimin e nj\u00eb produkti cil\u00ebsor. Pra, ne pyesim se me cil\u00ebt atribute cil\u00ebsie duhet t\u00eb disponoj\u00eb produkti yn\u00eb. P\u00ebrkat\u00ebsisht, n\u00ebse e kuptojm\u00eb k\u00ebt\u00eb, mund t\u00eb krahasojm\u00eb se kush ndikon n\u00eb k\u00ebto atribute cil\u00ebsie. Nuk ka r\u00ebnd\u00ebsi, zhvilluesi, menaxheri i projektit ose produktologu<\/strong>\u00a0\u2014 \u00ebsht\u00eb nj\u00eb person q\u00eb ndikon n\u00eb zhvillimin e produktit, n\u00eb backlog-un e tij, n\u00eb strategjin\u00eb e tij.<\/p>\n

Testuesi fillon t\u00eb kuptoj\u00eb m\u00eb mir\u00eb rolin e tij. Ai kupton se detyra e tij nuk \u00ebsht\u00eb vet\u00ebm t\u00eb testoj\u00eb p\u00ebr p\u00ebrputhshm\u00ebri me k\u00ebrkesat, por edhe t\u00eb testoj\u00eb k\u00ebrkesat, t\u00eb v\u00ebr\u00eb n\u00eb dyshim formulimet q\u00eb vijn\u00eb nga produktologu, t\u00eb zbuloj\u00eb t\u00eb gjitha k\u00ebrkesat dhe pritjet e papara t\u00eb klientit. Kur ne i ofrojm\u00eb nj\u00eb funksionalitet t\u00eb ri klientit ton\u00eb, ne duhet t\u00eb plot\u00ebsojm\u00eb v\u00ebrtet pritjet e tij dhe t\u00eb zgjidhim shqet\u00ebsimin e tij. N\u00ebse do t\u00eb mendojm\u00eb p\u00ebr t\u00eb gjitha atributet e cil\u00ebsis\u00eb, klienti do t\u00eb jet\u00eb i k\u00ebnaqur dhe do t\u00eb kuptoj\u00eb se kompania, produktin e t\u00eb cilit po e p\u00ebrdor, v\u00ebrtet\u00eb kujdeset p\u00ebr interesat e tij, dhe nuk punon me parimin \"t\u00eb shp\u00ebrb\u00ebj nj\u00eb karakteristik\u00eb\".<\/p>\n

\u2014 M\u00eb duket se ajo q\u00eb po e p\u00ebrshkruan tani \u00ebsht\u00eb detyra e produktologut. N\u00eb parim, kjo nuk ka t\u00eb b\u00ebj\u00eb me testimin dhe cil\u00ebsin\u00eb \u2013 kjo \u00ebsht\u00eb krejt\u00ebsisht p\u00ebr menaxhimin e produktit, apo jo?<\/em><\/strong><\/p>\n

Anastasia<\/strong>: Po, deri diku. Sigurimi i Cil\u00ebsis\u00eb nuk \u00ebsht\u00eb nj\u00eb disiplin\u00eb p\u00ebr t\u00eb cil\u00ebn p\u00ebrgjigjet nj\u00eb person konkret. Tani ka nj\u00eb qasje t\u00eb njohur n\u00eb testim, e cila quhet Testimi Agile<\/strong>N\u00eb p\u00ebrkufizimin e tij thuhet qart\u00eb se \u00ebsht\u00eb nj\u00eb qasje ekipore ndaj testimit, e cila p\u00ebrfshin nj\u00eb grup t\u00eb caktuar praktikash. P\u00ebr realizimin e k\u00ebsaj qasjeje \u00ebsht\u00eb p\u00ebrgjegj\u00ebse t\u00eb gjith\u00eb ekipi, nuk \u00ebsht\u00eb e nevojshme q\u00eb n\u00eb ekip t\u00eb ket\u00eb patjet\u00ebr nj\u00eb testues. I gjith\u00eb ekipi \u00ebsht\u00eb orientuar p\u00ebr t\u00eb ofruar vler\u00eb p\u00ebr klientin dhe q\u00eb kjo vler\u00eb t\u00eb p\u00ebrputhet me pritshm\u00ebrit\u00eb e tij.<\/p>\n

Pra, duket se cil\u00ebsia nd\u00ebrthuret pothuajse me t\u00eb gjitha disiplinat p\u00ebrreth, duke vendosur kufij p\u00ebr gjith\u00e7ka rreth?<\/em><\/strong><\/p>\n

Anastasia<\/strong>: E sakt\u00eb. Kur mendojm\u00eb p\u00ebr t\u00eb krijuar nj\u00eb produkt cil\u00ebsor, fillojm\u00eb t\u00eb mendojm\u00eb p\u00ebr atributet e ndryshme t\u00eb cil\u00ebsis\u00eb. P\u00ebr shembull, si t\u00eb verifikojm\u00eb q\u00eb kemi realizuar me t\u00eb v\u00ebrtet\u00eb nj\u00eb funksion q\u00eb i nevojitet klientit ton\u00eb.<\/p>\n

K\u00ebtu del nj\u00eb lloj testimi, si UAT<\/strong> (testimi i pranimit nga p\u00ebrdoruesi). Fatkeq\u00ebsisht, n\u00eb Rusi ai praktikohet rrall\u00eb, por ndonj\u00ebher\u00eb \u00ebsht\u00eb i pranish\u00ebm n\u00eb ekipet SCRUM, si nj\u00eb demonstrim p\u00ebr klientin p\u00ebrfundimtar. N\u00eb kompanit\u00eb jasht\u00eb vendit, kjo \u00ebsht\u00eb nj\u00eb form\u00eb testimi mjaft e zakonshme. Para se t\u00eb hapim funksionalitetin p\u00ebr t\u00eb gjith\u00eb klient\u00ebt, ne fillimisht b\u00ebjm\u00eb UAT, dmth. ftojm\u00eb p\u00ebrdoruesin p\u00ebrfundimtar, i cili kryen testimin dhe menj\u00ebher\u00eb jep feedback - n\u00ebse produkti n\u00eb t\u00eb v\u00ebrtet\u00eb p\u00ebrputhet me pritshm\u00ebrit\u00eb dhe zgjidh dhimbjen. Vet\u00ebm pas k\u00ebsaj ndodh zgjerimi p\u00ebr t\u00eb gjith\u00eb klient\u00ebt e tjer\u00eb.<\/p>\n

K\u00ebshtu q\u00eb ne orientoheni n\u00eb biznes, n\u00eb klientin p\u00ebrfundimtar, por n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb nuk harrojm\u00eb p\u00ebr teknologjin\u00eb<\/strong>. Cil\u00ebsia e produktit varet gjithashtu shum\u00eb nga teknologjit\u00eb. N\u00ebse kemi nj\u00eb arkitektur\u00eb t\u00eb dob\u00ebt, nuk do ta kemi t\u00eb leht\u00eb t\u00eb publikojm\u00eb shpejt funksionet dhe t\u00eb p\u00ebrputhemi me pritshm\u00ebrit\u00eb e klientit. Mund t\u00eb ket\u00eb shum\u00eb defekte kur p\u00ebrpiqemi t\u00eb zgjerim, apo kur p\u00ebrpiqemi t\u00eb b\u00ebjm\u00eb refaktorizimin ne mund t\u00eb thyejm\u00eb di\u00e7ka. E gjith\u00eb kjo do t\u00eb ndikoj\u00eb n\u00eb k\u00ebnaq\u00ebsin\u00eb e klientit.<\/p>\n

Nga kjo pik\u00ebpamje, arkitektura duhet t\u00eb jet\u00eb e till\u00eb q\u00eb ne t\u00eb mund t\u00eb shkruajm\u00eb kod t\u00eb past\u00ebr, i cili do t\u00eb lejoj\u00eb q\u00eb t\u00eb b\u00ebjm\u00eb shpejt ndryshime dhe t\u00eb mos kemi frik\u00eb se do t\u00eb thyejm\u00eb gjith\u00e7ka. Q\u00eb iteracionet e p\u00ebrmir\u00ebsimit mos t\u00eb zgjaten p\u00ebr muaj t\u00eb t\u00ebr\u00eb thjesht sepse kemi aq shum\u00eb legjaci, dhe duhet t\u00eb kryejm\u00eb faza testimi t\u00eb gjata.<\/p>\n

Pra, tashm\u00eb jan\u00eb t\u00eb p\u00ebrfshir\u00eb zhvilluesit, arkitekt\u00ebt, produktolog\u00ebt, menaxher\u00ebt e produkteve, vet\u00eb testuesit. Kush tjet\u00ebr \u00ebsht\u00eb i p\u00ebrfshir\u00eb n\u00eb procesin e sigurimit t\u00eb cil\u00ebsis\u00eb?<\/em><\/strong><\/p>\n

Anastasia<\/strong>: Tani, le t\u00eb imagjinojm\u00eb se ne tashm\u00eb ia kemi dor\u00ebzuar klientit k\u00ebt\u00eb tipar. \u00cbsht\u00eb e qart\u00eb se menaxhimi i cil\u00ebsis\u00eb s\u00eb produktit \u00ebsht\u00eb i r\u00ebnd\u00ebsish\u00ebm, edhe kur ai \u00ebsht\u00eb n\u00eb prodhim. N\u00eb k\u00ebt\u00eb faz\u00eb, situatat me skenar\u00eb jo t\u00eb duksh\u00ebm, t\u00eb njohura si t\u00eb mbeturina, mund t\u00eb dalin n\u00eb pah.<\/p>\n

Pyetja e par\u00eb \u00ebsht\u00eb se si punojm\u00eb me k\u00ebto t\u00eb mbeturina pasi e kemi l\u00ebshuar produktin? Si reagojm\u00eb, p\u00ebr shembull, ndaj ngarkes\u00ebs? Klienti nuk do t\u00eb jet\u00eb shum\u00eb i k\u00ebnaqur n\u00ebse faqja ngarkohet p\u00ebr m\u00eb shum\u00eb se 30 sekonda.<\/p>\n

K\u00ebtu hyn n\u00eb loj\u00eb operimi ose, si\u00e7 e quajn\u00eb tani, DevOps<\/strong>. N\u00eb fakt, k\u00ebta jan\u00eb njer\u00ebzit q\u00eb jan\u00eb p\u00ebrgjegj\u00ebs p\u00ebr operimin e produktit kur ai \u00ebsht\u00eb tashm\u00eb n\u00eb prodhim. K\u00ebtu p\u00ebrfshihen lloje t\u00eb ndryshme monitorimi. Ka edhe nj\u00eb n\u00ebnkategori t\u00eb testimit - testimi n\u00eb prodhim, kur ne i lejojm\u00eb vetes t\u00eb mos testojm\u00eb di\u00e7ka para l\u00ebshimit dhe ta testojm\u00eb menj\u00ebher\u00eb n\u00eb prodhim. Ky \u00ebsht\u00eb nj\u00eb seri masash, p\u00ebrballet nga pik\u00ebpamja e organizimit t\u00eb infrastruktur\u00ebs, q\u00eb lejojn\u00eb reagimin e shpejt\u00eb ndaj incidenteve, ndikuar n\u00eb to, dhe korrigjimin e tyre.<\/p>\n

Infrastruktura \u00ebsht\u00eb gjithashtu e r\u00ebnd\u00ebsishme. Shpesh ndodhin situata ku n\u00eb koh\u00ebn e testit, e pamund\u00ebsueshme t\u00eb sigurohemi se ne fakt kemi gjith\u00e7ka q\u00eb d\u00ebshirojm\u00eb t'i japim klientit. L\u00ebshojm\u00eb n\u00eb prodhim \u2013 dhe fillojm\u00eb t\u00eb kapim situata t\u00eb jo t\u00eb dukshme. Dhe e gjitha kjo ndodh sepse infrastruktura n\u00eb test nuk p\u00ebrputhet me infrastrukturen n\u00eb prodhim. K\u00ebtu del nj\u00eb lloj i ri testimi \u2014 testimi i infrastruktur\u00ebs<\/strong>. K\u00ebtu p\u00ebrfshihen konfiguracione t\u00eb ndryshme, rregullime, migrimi i bazave t\u00eb t\u00eb dh\u00ebnave, etj.<\/p>\n

K\u00ebtu lind pyetja \u2014 ndoshta ekipi duhet t\u00eb p\u00ebrdor\u00eb infrastruktura si kod.<\/p>\n

Un\u00eb besoj se infrastruktura ndikon drejtp\u00ebrdrejt n\u00eb cil\u00ebsin\u00eb e produktit.<\/p><\/blockquote>\n

\nShpresoj se n\u00eb konferenc\u00eb do t\u00eb ket\u00eb nj\u00eb prezantim me nj\u00eb rast real. Na shkruani n\u00ebse jeni t\u00eb gatsh\u00ebm t\u00eb flisni nga p\u00ebrvoja juaj se si infrastruktura si kod ndikon n\u00eb cil\u00ebsi. Infrastruktura si kod lejon t\u00eb kontrollohet m\u00eb leht\u00eb t\u00eb gjitha rregullimet dhe t\u00eb testojn\u00eb at\u00eb q\u00eb p\u00ebrndryshe do t\u00eb ishte e pamundur. Prandaj n\u00eb procesin e zhvillimit t\u00eb nj\u00eb produkti cil\u00ebsor p\u00ebrfshihet edhe operimi.<\/p>\n

\u2014 Dhe si q\u00ebndron \u00e7\u00ebshtja e analitik\u00ebs dhe dokumentacionit?<\/em><\/strong><\/p>\n

Anastasia<\/strong>: Kjo i referohet m\u00eb shum\u00eb sistemeve enterprise. Kur flasim p\u00ebr enterprise, menj\u00ebher\u00eb n\u00eb mendje vijn\u00eb njer\u00ebz si analist\u00ebt dhe analist\u00ebt sistemor\u00eb. Ndonj\u00ebher\u00eb ato quhen shkrimtar\u00eb teknik\u00eb. Ata marrin nj\u00eb detyr\u00eb p\u00ebr t\u00eb shkruar specifikimin dhe e realizojn\u00eb at\u00eb, p\u00ebr shembull, brenda nj\u00eb muaji.<\/p>\n

Ka provuar disa her\u00eb se shkruarja e dokumentacionit t\u00eb till\u00eb \u00e7on n\u00eb iteracione shum\u00eb t\u00eb gjata zhvillimi dhe iteracione t\u00eb gjata p\u00ebr p\u00ebrmir\u00ebsime, sepse gjat\u00eb procesit t\u00eb testimit dalin defekte dhe fillojn\u00eb kthimet. N\u00eb rezultat, shfaqen shum\u00eb qarqe q\u00eb rrisin koston e zhvillimit. P\u00ebr m\u00eb tep\u00ebr, kjo mund t\u00eb sjell\u00eb vulnerabilitete. Ne sikur e kemi shkruar kodin referenc\u00eb, por m\u00eb pas b\u00ebm\u00eb ndryshime q\u00eb shkat\u00ebrrojn\u00eb arkitektur\u00ebn e menduar n\u00eb m\u00ebnyr\u00eb ideale.<\/p>\n

Si rezultat, kemi nj\u00eb produkt jo t\u00eb mir\u00eb, sepse n\u00eb arkitektur\u00eb tashm\u00eb jan\u00eb shfaqur patch, kodi n\u00eb disa vende nuk \u00ebsht\u00eb mbuluar mjaftuesh\u00ebm me teste, sepse afatet po ngushtohen dhe duhet t\u00eb mbyllen sa m\u00eb shpejt t\u00eb jet\u00eb e mundur t\u00eb gjith\u00eb defektet. Dhe kjo ndodh sepse n\u00eb specifikimin fillestar nuk u mor\u00ebn parasysh t\u00eb gjitha aspektet q\u00eb duhej t\u00eb realizoheshin.<\/p>\n

Zhvilluesit nuk jan\u00eb shkaktar\u00eb dhe nuk shkruajn\u00eb kod me q\u00ebllim gabimesh.<\/p><\/blockquote>\n

\nN\u00ebse do t\u00eb kishim menduar fillimisht nj\u00eb specifikim, n\u00eb t\u00eb cilin do t\u00eb ishin p\u00ebrfshir\u00eb t\u00eb gjitha aspektet e nevojshme, gjith\u00e7ka do t\u00eb realizohej pik\u00ebrisht ashtu si\u00e7 duhet. Por kjo \u00ebsht\u00eb nj\u00eb utopi.<\/p>\n

Ndoshta, t\u00eb shkruash nj\u00eb specifikim t\u00eb p\u00ebrsosur n\u00eb 100 faqe \u00ebsht\u00eb e pamundur. Prandaj duhet t\u00eb mendojm\u00eb p\u00ebr m\u00ebnyra alternative t\u00eb shkruarjes s\u00eb dokumentacionit<\/strong>, specifikimit, vendosjes s\u00eb detyrave, q\u00eb do t\u00eb na afronin m\u00eb af\u00ebr realizimit t\u00eb asaj q\u00eb zhvilluesi t\u00eb b\u00ebnte pik\u00ebrisht at\u00eb q\u00eb duhet.<\/p>\n

K\u00ebtu m\u00eb vjen n\u00eb mendje qasja nga Agile - historit\u00eb e p\u00ebrdoruesve me kriteret e pranimit. Kjo \u00ebsht\u00eb m\u00eb shum\u00eb e aplikueshme p\u00ebr ekipet q\u00eb evolucionojn\u00eb n\u00eb iteracione t\u00eb vogla.<\/p>\n

\u2014 \u00c7far\u00eb \u00ebsht\u00eb p\u00ebr testimin e p\u00ebrdorshm\u00ebris\u00eb, leht\u00ebsin\u00eb e p\u00ebrdorimit t\u00eb produktit, dizajnin?<\/em><\/strong><\/p>\n

Anastasia<\/strong>: Ky \u00ebsht\u00eb nj\u00eb moment shum\u00eb i r\u00ebnd\u00ebsish\u00ebm, sepse n\u00eb ekip ka dizajner\u00eb. Zakonisht p\u00ebrdoren dizajner\u00ebt si nj\u00eb sh\u00ebrbim \u2014 ose nj\u00eb departament dizajni, ose nj\u00eb dizajner i jasht\u00ebm. Fatkeq\u00ebsisht, ndodhin situata kur duket se dizajneri e d\u00ebgjoi produktologun dhe kreu at\u00eb q\u00eb kuptoi. Por kur fillojm\u00eb iteracionin, zbulojm\u00eb se n\u00eb t\u00eb v\u00ebrtet\u00eb nuk \u00ebsht\u00eb b\u00ebr\u00eb ashtu si\u00e7 pritej: dizajneri harroi di\u00e7ka, nuk e mendoi deri n\u00eb fund funksionimin, sepse ai nuk \u00ebsht\u00eb n\u00eb ekip dhe nuk ndodhet n\u00eb kontekst, ose zhvilluesi i frontend-it nuk e kuptoi plot\u00ebsisht skic\u00ebn e tij. Mund t\u00eb nevojiten disa iteracione vet\u00ebm p\u00ebr shkak se ka nj\u00eb problem me kuptimin e dizajnit nga ana e zhvilluesit t\u00eb frontend-it.<\/p>\n

P\u00ebrve\u00e7 k\u00ebsaj, ka nj\u00eb problem tjet\u00ebr. Tani jan\u00eb n\u00eb rritje popullaritetin e sistemet e dizajnit. Ato jan\u00eb n\u00eb trend, por p\u00ebrfitimi nga to nuk \u00ebsht\u00eb krejt\u00ebsisht i qart\u00eb.<\/p>\n

Kam hasur n\u00eb mendimin se sistemet e dizajnit, nga nj\u00ebra an\u00eb, e thjeshtojn\u00eb zhvillimin, por nga ana tjet\u00ebr, imponojn\u00eb shum\u00eb kufizime n\u00eb nd\u00ebrfaqe.<\/p><\/blockquote>\n

\nN\u00eb p\u00ebrfundim, ne nuk po b\u00ebjm\u00eb nj\u00eb ve\u00e7ori t\u00eb till\u00eb q\u00eb klienti d\u00ebshiron t\u00eb marr\u00eb, por nj\u00eb t\u00eb till\u00eb q\u00eb na p\u00ebrshtatet ne, sepse ne tashm\u00eb kemi disa kubik\u00eb nga t\u00eb cil\u00ebt mund ta nd\u00ebrtojm\u00eb.<\/p>\n

M\u00eb duket se duhet t\u00eb kushtohet v\u00ebmendje k\u00ebsaj teme dhe t\u00eb mendohet, a e zgjidhim me t\u00eb v\u00ebrtet\u00eb dhimbjen e klient\u00ebve n\u00eb p\u00ebrpjekjen p\u00ebr t\u00eb thjeshtuar pun\u00ebn n\u00eb dizajn.<\/p>\n

\u2014 K\u00ebshtu q\u00eb duket se ka shum\u00eb tema q\u00eb lidhen me Sigurin\u00eb e Cil\u00ebsis\u00eb. N\u00eb Rusi ka nj\u00eb konferenc\u00eb ku mund t\u00eb diskutohet p\u00ebr to?<\/em><\/strong><\/p>\n

Anastasia<\/strong>: Ka konferenc\u00ebn m\u00eb t\u00eb vjet\u00ebr p\u00ebr testimin, e cila k\u00ebt\u00eb vit do t\u00eb mbahet p\u00ebr her\u00eb t\u00eb 25-t\u00eb dhe quhet \u2014 Konferenca p\u00ebr sigurimin e cil\u00ebsis\u00eb SQA Days. Kryesisht n\u00eb t\u00eb diskutohen mjetet dhe qasje t\u00eb caktuara t\u00eb testimit p\u00ebr testuesit funksional\u00eb. Zakonisht, n\u00eb prezantimet n\u00eb SQA Days shqyrtohen thell\u00ebsisht fushat specifike n\u00eb zon\u00ebn e p\u00ebrgjegj\u00ebsis\u00eb s\u00eb vet\u00eb testuesve, por jo aktivitetet kumulative.<\/p>\n

Kjo ndihmon shum\u00eb p\u00ebr t\u00eb kuptuar mjetet dhe qasjet e ndryshme se si t\u00eb testohen bazat e t\u00eb dh\u00ebnave, API etj. Por nga nj\u00ebra an\u00eb, nuk motivon p\u00ebrfshirjen n\u00eb krijimin e nj\u00eb produkti m\u00eb cil\u00ebsor jo vet\u00ebm nga testimi. Nd\u00ebrsa nga ana tjet\u00ebr, testuesit nuk b\u00ebhen m\u00eb t\u00eb angazhuar n\u00eb proces, p\u00ebr t\u00eb menduar p\u00ebr q\u00ebllimin global t\u00eb produktit dhe komponentin e tij biznesor.<\/p>\n

Un\u00eb drejtoj nj\u00eb departament t\u00eb madh, realizoj shum\u00eb intervista q\u00eb n\u00eb t\u00eb v\u00ebrtet\u00eb pasqyrojn\u00eb gjendjen e industris\u00eb n\u00eb p\u00ebrgjith\u00ebsi. Zakonisht, djemt\u00eb tan\u00eb punojn\u00eb n\u00eb enterprise, dhe ata kan\u00eb nj\u00eb zon\u00eb t\u00eb qart\u00eb p\u00ebrgjegj\u00ebsie. Koleg\u00ebt q\u00eb punojn\u00eb n\u00eb projekte nd\u00ebrkomb\u00ebtare p\u00ebrdorin lloje t\u00eb ndryshme testimi: ata mund t\u00eb realizojn\u00eb teste ngarkese, teste performanc\u00ebs, dhe madje ndonj\u00ebher\u00eb teste sigurie, sepse ata v\u00ebrtet ndihmojn\u00eb ekipin t\u00eb siguroj\u00eb cil\u00ebsin\u00eb e produktit.<\/p>\n

M\u00eb p\u00eblqen t\u00eb mendoj q\u00eb edhe n\u00eb Rusia djemt\u00eb duhet t\u00eb fillojn\u00eb t\u00eb mendojn\u00eb se industria nuk p\u00ebrfundon me testimin funksional.<\/p>\n

\u2014 P\u00ebr k\u00ebt\u00eb po organizojm\u00eb nj\u00eb konferenc\u00eb t\u00eb re QualityConf, e cila \u00ebsht\u00eb e dedikuar cil\u00ebsis\u00eb si nj\u00eb disiplin\u00eb t\u00ebr\u00ebsore. Mund t\u00eb na tregosh m\u00eb shum\u00eb p\u00ebr konceptin, cili \u00ebsht\u00eb q\u00ebllimi kryesor i konferenc\u00ebs?<\/em><\/strong><\/p>\n

Anastasia<\/strong>: Ne duam t\u00eb krijojm\u00eb nj\u00eb komunitet njer\u00ebzish t\u00eb interesuar n\u00eb t\u00eb b\u00ebrit e produkteve me cil\u00ebsi t\u00eb lart\u00eb. T\u00eb ofrojm\u00eb nj\u00eb platform\u00eb ku ata mund t\u00eb vijn\u00eb, t\u00eb d\u00ebgjojn\u00eb ligj\u00ebrata dhe t\u00eb dalin pas konferenc\u00ebs me nj\u00eb kuptim t\u00eb qart\u00eb se \u00e7far\u00eb duhet t\u00eb ndryshojn\u00eb p\u00ebr t\u00eb p\u00ebrmir\u00ebsuar cil\u00ebsin\u00eb.<\/p>\n

S\u00eb shumti tani po d\u00ebgjoj k\u00ebrkesat nga konsulenca p\u00ebr at\u00eb se \u00e7far\u00eb t\u00eb b\u00ebjm\u00eb kur ka probleme me testimin dhe cil\u00ebsin\u00eb. Kur fillon t\u00eb bisedosh me ekipet, shikon se problemi nuk \u00ebsht\u00eb te vet\u00eb testuesit, por te m\u00ebnyra se si \u00ebsht\u00eb nd\u00ebrtuar procesi. P\u00ebr shembull, kur zhvilluesit mendojn\u00eb se jan\u00eb p\u00ebrgjegj\u00ebs vet\u00ebm p\u00ebr shkrimin e kodit, p\u00ebrgjegj\u00ebsia e tyre p\u00ebrfundon pik\u00ebrisht n\u00eb momentin q\u00eb ata e kalojn\u00eb detyr\u00ebn n\u00eb testim.<\/p>\n

Nuk t\u00eb gjith\u00eb mendojn\u00eb q\u00eb kodi me cil\u00ebsi t\u00eb dob\u00ebt, me arkitektur\u00eb t\u00eb keqe, sjell probleme t\u00eb m\u00ebdha p\u00ebr projektin. Nuk mendohet rreth kostos s\u00eb gabimeve, se defektet q\u00eb kalojn\u00eb n\u00eb prodhim mund t\u00eb sjellin kosto t\u00eb m\u00ebdha p\u00ebr kompanin\u00eb dhe ekipin. Nuk ka nj\u00eb kultur\u00eb p\u00ebr t\u00eb menduar rreth k\u00ebsaj. Dua q\u00eb gjat\u00eb konferenc\u00ebs t\u00eb fillojm\u00eb ta p\u00ebrhapim k\u00ebt\u00eb kultur\u00eb.<\/p>\n

E kuptoj q\u00eb kjo nuk \u00ebsht\u00eb nj\u00eb inovat\u00eb. Edward Deming, autori i 14 postulateve t\u00eb cil\u00ebsis\u00eb, kishte shkruar p\u00ebr koston e gabimeve q\u00eb n\u00eb shekullin e kaluar. Kjo lib\u00ebr \u00ebsht\u00eb baza e Quality Assurance si nj\u00eb disiplin\u00eb, por fatkeq\u00ebsisht, zhvillimi modern e harron k\u00ebt\u00eb.<\/p>\n

\u2014 A do t\u00eb planifikoni t\u00eb diskutoni tema drejtp\u00ebrdrejt n\u00eb lidhje me testimin dhe mjetet?<\/em><\/strong><\/p>\n

Anastasia<\/strong>: Pranoj q\u00eb do t\u00eb ket\u00eb prezantime mbi mjetet. Ka mjaft mjete universale me an\u00eb t\u00eb t\u00eb cilave kompanit\u00eb dhe ekipet mund t\u00eb ndikojn\u00eb n\u00eb produkt.<\/p>\n

T\u00eb gjitha prezantimet do t\u00eb jen\u00eb globalisht t\u00eb bashkuara nga nj\u00eb mision t\u00eb p\u00ebrbashk\u00ebt: t\u00eb komunikojn\u00eb me audienc\u00ebn se me an\u00eb t\u00eb k\u00ebtij qasje, mjeti, metode, procesi, tipit t\u00eb testimit ne ndikojm\u00eb n\u00eb cil\u00ebsin\u00eb e produktit dhe p\u00ebrmir\u00ebsojm\u00eb jet\u00ebn e klientit.<\/p><\/blockquote>\n

\nSigurisht q\u00eb nuk do t\u00eb kem prezantime p\u00ebr mjetin p\u00ebr vet\u00eb mjetin. T\u00eb gjitha prezantimet q\u00eb do t\u00eb p\u00ebrfshihen n\u00eb program do t\u00eb ken\u00eb nj\u00eb q\u00ebllim t\u00eb p\u00ebrbashk\u00ebt.<\/p>\n

\u2014 Kush do t\u00eb ket\u00eb interes p\u00ebr at\u00eb q\u00eb po thua, k\u00eb keni parasysh si mysafir\u00eb t\u00eb konferenc\u00ebs?<\/em><\/strong><\/p>\n

Anastasia<\/strong>: Ne do t\u00eb kemi prezantime p\u00ebr zhvilluesit, t\u00eb cil\u00ebt nuk jan\u00eb indiferent\u00eb ndaj fatit t\u00eb projektit t\u00eb tyre, produktit, sistemit. Po ashtu, do t\u00eb jet\u00eb interesante p\u00ebr testuesit dhe, si\u00e7 mendoj, ve\u00e7an\u00ebrisht p\u00ebr menaxher\u00ebt. Me menaxher\u00ebt kam parasysh ata q\u00eb marrin vendime dhe mund t\u00eb ndikojn\u00eb n\u00eb fatin dhe zhvillimin e produktit, sistemit, ekipit gjithashtu.<\/p>\n

K\u00ebta jan\u00eb njer\u00ebz q\u00eb b\u00ebjn\u00eb pyetje se si t\u00eb rrisin cil\u00ebsin\u00eb e produktit, sistemit. N\u00eb konferenc\u00ebn ton\u00eb ata do t\u00eb m\u00ebsojn\u00eb p\u00ebr komplekset e ndryshme t\u00eb aktiviteteve dhe do t\u00eb mund t\u00eb kuptojn\u00eb se \u00e7far\u00eb nuk \u00ebsht\u00eb mir\u00eb tani, \u00e7far\u00eb duhet t\u00eb ndryshojn\u00eb.<\/p>\n

Mendoj se kriteri kryesor \u00ebsht\u00eb t\u00eb kuptohet se di\u00e7ka nuk \u00ebsht\u00eb mir\u00eb me cil\u00ebsin\u00eb dhe t\u00eb d\u00ebshirohet t\u00eb ndikosh n\u00eb k\u00ebt\u00eb. Ndoshta, nuk do t\u00eb arrijm\u00eb t\u00eb arrijm\u00eb te njer\u00ebzit q\u00eb mendojn\u00eb se gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull nga hera e par\u00eb.<\/p>\n

\u2014 Si e mendon, industria n\u00eb t\u00ebr\u00ebsi ka arritur n\u00eb nj\u00eb pik\u00eb ku mund t\u00eb flitet jo thjesht p\u00ebr testimin, por p\u00ebr kultur\u00ebn e cil\u00ebsis\u00eb?<\/em><\/strong><\/p>\n

Anastasia<\/strong>: Un\u00eb mendoj se ka arritur. Tani shum\u00eb kompani po largohen nga qasja tradicionale Waterfall drejt Agile. Po ndodh orientimi ndaj klientit, njer\u00ebzit n\u00eb ekipe v\u00ebrtet po fillojn\u00eb t\u00eb mendojn\u00eb p\u00ebr m\u00ebnyrat se si t\u00eb krijojn\u00eb nj\u00eb produkt cil\u00ebsor. Edhe n\u00eb kompanit\u00eb enterprise ndodhin riorientime p\u00ebr rritjen e cil\u00ebsis\u00eb.<\/p>\n

Duke par\u00eb numrin e k\u00ebrkesave q\u00eb ndodhin n\u00eb komunitet, mendoj se tashm\u00eb \u00ebsht\u00eb koha. Nuk jam e sigurt, sigurisht, q\u00eb do t\u00eb jet\u00eb nj\u00eb revolucion i madh, por do t\u00eb doja q\u00eb ky ndryshim n\u00eb mendje t\u00eb ndodhte.<\/p>\n

\u2014 Marr\u00ebveshje! Do t\u00eb punojm\u00eb p\u00ebr t\u00eb kultivuar kultur\u00ebn dhe ndryshuar mendimin.<\/em><\/strong><\/p>\n

Konferenca p\u00ebr zhvillimin cil\u00ebsor t\u00eb produkteve IT QualityConf<\/a><\/noindex> do t\u00eb ndodh\u00eb n\u00eb Mosk\u00eb m\u00eb 7 qershor<\/strong>Dini, se nga \u00e7far\u00eb fazash p\u00ebrb\u00ebhet nj\u00eb produkt i mir\u00eb, kemi raste t\u00eb suksesshme t\u00eb luftimit t\u00eb defekteve n\u00eb prodhim, dhe kemi verifikuar metodologjit\u00eb populare n\u00eb praktik\u00ebn ton\u00eb \u2014 na nevojitet eksperienca juaj. D\u00ebrgoni<\/a><\/noindex> t\u00eb tuat k\u00ebrkesat deri m\u00eb 1 maj<\/strong>, dhe Komiteti Programor do t\u00eb ndihmoj\u00eb n\u00eb fokusimin e tem\u00ebs p\u00ebr nj\u00eb koherenc\u00eb t\u00eb p\u00ebrgjithshme t\u00eb konferenc\u00ebs.<\/p>\n

Bashkohuni me bised\u00ebn<\/a><\/noindex>, ku diskutojm\u00eb \u00e7\u00ebshtjet e cil\u00ebsis\u00eb dhe konferenc\u00ebn, abonohuni n\u00eb kanalin Telegram<\/a><\/noindex>, p\u00ebr t'u mbajtur t\u00eb informuar mbi lajmet e programit.<\/p><\/blockquote>\n

Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041f\u0440\u0438\u0432\u0435\u0442, \u0425\u0430\u0431\u0440! \u0423\u00a0\u043d\u0430\u0441 \u043d\u043e\u0432\u0430\u044f \u0432\u0430\u0436\u043d\u0430\u044f \u0442\u0435\u043c\u0430\u00a0\u2014 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u0430\u044f \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0430 IT-\u043f\u0440\u043e\u0434\u0443\u043a\u0442\u043e\u0432. \u041c\u044b\u00a0\u0447\u0430\u0441\u0442\u043e \u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043d\u0430\u00a0HighLoad++, \u043a\u0430\u043a \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u043d\u0430\u0433\u0440\u0443\u0436\u0435\u043d\u043d\u044b\u0435 \u0441\u0435\u0440\u0432\u0438\u0441\u044b \u0431\u044b\u0441\u0442\u0440\u044b\u043c\u0438, \u0430\u00a0\u043d\u0430\u00a0Frontend Conf\u00a0\u2014 \u043a\u043b\u0430\u0441\u0441\u043d\u044b\u0439 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u0441\u043a\u0438\u0439 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043d\u0435\u00a0\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442. \u0423\u00a0\u043d\u0430\u0441 \u0440\u0435\u0433\u0443\u043b\u044f\u0440\u043d\u043e \u0435\u0441\u0442\u044c \u0442\u0435\u043c\u044b \u043f\u0440\u043e \u0442\u0435\u0441\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435, \u0438\u00a0DevOpsConf \u043f\u0440\u043e \u043e\u0431\u044a\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0435 \u0440\u0430\u0437\u043d\u044b\u0445 \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u043e\u0432, \u0432\u043a\u043b\u044e\u0447\u0430\u044f \u0442\u0435\u0441\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435. \u0410\u00a0\u043f\u0440\u043e\u00a0\u0442\u043e, \u0447\u0442\u043e \u043c\u043e\u0436\u043d\u043e \u043d\u0430\u0437\u0432\u0430\u0442\u044c \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u043e \u0432\u00a0\u0446\u0435\u043b\u043e\u043c, \u0438\u00a0\u043a\u0430\u043a \u043d\u0430\u0434 \u043d\u0438\u043c \u043a\u043e\u043c\u043f\u043b\u0435\u043a\u0441\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0442\u044c\u00a0\u2014 \u043d\u0435\u0442. \u0418\u0441\u043f\u0440\u0430\u0432\u0438\u043c \u044d\u0442\u043e \u043d\u0430 QualityConf\u00a0\u2014 \u0431\u0443\u0434\u0435\u043c \u0440\u0430\u0437\u0432\u0438\u0432\u0430\u0442\u044c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":23230,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31264","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Kush do t\u00eb p\u00ebrgjigjet p\u00ebr cil\u00ebsin\u00eb? | ProHoster","description":"P\u00ebrsh\u00ebndetje, Habr! Ne kemi nj\u00eb tem\u00eb t\u00eb re t\u00eb r\u00ebnd\u00ebsishme \u2014 zhvillimi i cil\u00ebsis\u00eb s\u00eb produkteve IT.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kto-otvetit-za-kachestvo","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041a\u0442\u043e \u043e\u0442\u0432\u0435\u0442\u0438\u0442 \u0437\u0430 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u043e? | ProHoster","og:description":"\u041f\u0440\u0438\u0432\u0435\u0442, \u0425\u0430\u0431\u0440! \u0423 \u043d\u0430\u0441 \u043d\u043e\u0432\u0430\u044f \u0432\u0430\u0436\u043d\u0430\u044f \u0442\u0435\u043c\u0430 \u2014 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u0430\u044f \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0430 IT-\u043f\u0440\u043e\u0434\u0443\u043a\u0442\u043e\u0432.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kto-otvetit-za-kachestvo","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:40:21+00:00","article:modified_time":"2019-10-31T18:40:21+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31264","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 05:19:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:19:50","updated":"2026-01-21 05:19:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/31264","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=31264"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/31264\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/23230"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=31264"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=31264"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=31264"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}