{"id":54188,"date":"2019-12-20T00:00:00","date_gmt":"2019-12-19T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/chem-testmace-luchshe-postman"},"modified":"2020-02-18T14:02:10","modified_gmt":"2020-02-18T11:02:10","slug":"chem-testmace-luchshe-postman","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/chem-testmace-luchshe-postman","title":{"rendered":"\u00c7far\u00eb e b\u00ebn TestMace m\u00eb t\u00eb mir\u00eb se Postman","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"\u00c7far\u00eb<\/p>\n

<\/p>\n

P\u00ebrsh\u00ebndetje t\u00eb gjith\u00ebve, k\u00ebtu TestMace<\/a><\/noindex>! Ndoshta, shum\u00eb prej jush na njihni nga tonat<\/a><\/noindex> lajmeve t\u00eb m\u00ebparshme<\/a><\/noindex> artikujsh<\/a><\/noindex>. P\u00ebr ata q\u00eb sapo jan\u00eb lidhur: ne zhvillojm\u00eb IDE p\u00ebr pun\u00ebn me API TestMace. Pyetja m\u00eb e shpesht\u00eb kur krahasohet TestMace me produktet konkurrente \u00ebsht\u00eb: '\u00c7far\u00eb ju ndryshon nga Postman?'. Vendos\u00ebm q\u00eb \u00ebsht\u00eb koha t\u00eb japim nj\u00eb p\u00ebrgjigje t\u00eb detajuar p\u00ebr k\u00ebt\u00eb pyetje. M\u00eb posht\u00eb, kemi renditur p\u00ebrfitimet tona ndaj Postman<\/a><\/noindex>.<\/p>\n

<\/a><\/noindex><\/p>\n

Ndarja n\u00eb nyje<\/h2>\n

<\/p>\n

N\u00ebse punoni me Postman, e dini se nd\u00ebrfaqja e k\u00ebrkes\u00ebs p\u00ebrmban t\u00eb gjith\u00eb funksionalitetin e nevojsh\u00ebm. Aty ka skripte, teste dhe, n\u00eb thelb, k\u00ebrkesat vet\u00eb. Kjo e thjeshton pun\u00ebn p\u00ebr fillestar\u00ebt, megjithat\u00eb, n\u00eb skenar\u00eb t\u00eb m\u00ebdhenj, ky qasje nuk \u00ebsht\u00eb fleksib\u00ebl. \u00c7far\u00eb n\u00ebse d\u00ebshiron t\u00eb krijosh disa k\u00ebrkesa dhe t\u00eb b\u00ebsh agregimin mbi to? \u00c7far\u00eb n\u00ebse do t\u00eb ekzekutosh nj\u00eb skript pa k\u00ebrkes\u00eb ose disa skripte t\u00eb ndara logjikisht radhazi? N\u00eb fund t\u00eb fundit, nuk do t\u00eb ishte keq t\u00eb ndaheshin testet nga skriptet e zakonshme utilitare. P\u00ebrve\u00e7 k\u00ebsaj, qasja 'shtojm\u00eb t\u00eb gjith\u00eb funksionalitetin n\u00eb nj\u00eb nyje' \u00ebsht\u00eb e pa shkall\u00ebzuar \u2014 nd\u00ebrfaqja shpejt b\u00ebhet e ngarkuar.<\/p>\n

<\/p>\n

TestMace fillimisht ndan t\u00eb gjith\u00eb funksionalitetin n\u00eb lloje t\u00eb ndryshme nyjesh. D\u00ebshiron t\u00eb b\u00ebsh nj\u00eb k\u00ebrkes\u00eb? Ja ku je hapi i k\u00ebrkes\u00ebs<\/a><\/noindex> nyje. D\u00ebshiron t\u00eb shkruash nj\u00eb skript? Ja ku je script<\/a><\/noindex> nyje. T\u00eb nevojiten teste? Po \u2014 Assertion<\/a><\/noindex> nyje. Oh, po, ti gjithashtu mund ta mb\u00ebshtjell\u00ebsh k\u00ebt\u00eb n\u00eb nj\u00eb folder<\/a><\/noindex> nyje. Dhe e gjith\u00eb kjo leht\u00eb kombinon me nj\u00ebra-tjetr\u00ebn. Kjo qasje jo vet\u00ebm q\u00eb \u00ebsht\u00eb shum\u00eb fleksib\u00ebl, por edhe, n\u00eb p\u00ebrputhje me parimin e p\u00ebrgjegj\u00ebsis\u00eb unike, lejon t\u00eb p\u00ebrdoret vet\u00ebm ajo q\u00eb t\u00eb nevojitet v\u00ebrtet n\u00eb at\u00eb moment. Pse t\u00eb m\u00eb duhen skripte dhe teste, n\u00ebse thjesht dua t\u00eb b\u00ebj nj\u00eb k\u00ebrkes\u00eb?<\/p>\n

<\/p>\n

Formati i lexuesh\u00ebm p\u00ebr njeriun i projektit<\/h2>\n

<\/p>\n

Mes TestMace dhe Postman ka nj\u00eb dallim konceptual n\u00eb m\u00ebnyr\u00ebn e ruajtjes. N\u00eb Postman t\u00eb gjitha k\u00ebrkesat ruhen diku n\u00eb ruajtjen lokale. N\u00ebse ka nevoj\u00eb p\u00ebr t\u00eb ndar\u00eb k\u00ebrkesat midis disa p\u00ebrdoruesve, duhet t\u00eb p\u00ebrdoren sinkronizimi i nd\u00ebrtuar. N\u00eb t\u00eb v\u00ebrtet\u00eb, kjo \u00ebsht\u00eb nj\u00eb qasje e zakonshme, por jo pa disavantazhe. Si p\u00ebr sigurin\u00eb e t\u00eb dh\u00ebnave? Politika e disa kompanive mund t\u00eb mos lejoj\u00eb ruajtjen e t\u00eb dh\u00ebnave te pal\u00ebt e treta. Megjithat\u00eb, ne mendojm\u00eb se TestMace mund t\u00eb ofroj\u00eb di\u00e7ka m\u00eb t\u00eb mir\u00eb! Dhe emri i k\u00ebtij p\u00ebrmir\u00ebsimi \u00ebsht\u00eb 'formati i lexuesh\u00ebm p\u00ebr njeriun i projektit'.<\/p>\n

<\/p>\n

Le t\u00eb fillojm\u00eb me faktin se n\u00eb TestMace ka n\u00eb thelb entitetin \u201cprojekt\u201d. Dhe aplikacioni \u00ebsht\u00eb zhvilluar n\u00eb parim p\u00ebr ruajtjen e projekteve n\u00eb sistemet e kontrollit t\u00eb versioneve: struktura e projektit pothuajse projektohet nj\u00eb n\u00eb nj\u00eb me struktur\u00ebn e skedar\u00ebve, formati i ruajtjes p\u00ebrdor yaml (pa shenj\u00eb t\u00eb panevojshme dhe presje), dhe paraqitja e skedar\u00ebve t\u00eb \u00e7do nyje p\u00ebrshkruhet n\u00eb detaje n\u00eb dokumentacion me komentet. Por n\u00eb shumic\u00ebn e rasteve nuk do t\u00eb keni nevoj\u00eb t\u00eb shikoni atje \u2014 t\u00eb gjitha emrat e fushave kan\u00eb emra t\u00eb arsyesh\u00ebm. <\/p>\n

<\/p>\n

\u00c7far\u00eb i sjell p\u00ebrdoruesit? Kjo lejon t\u00eb ndryshoni shum\u00eb fleksib\u00ebl rrjedh\u00ebn e pun\u00ebs s\u00eb ekipit duke p\u00ebrdorur qasje t\u00eb njohura. P\u00ebr shembull, zhvilluesit mund t\u00eb ruajn\u00eb projektin n\u00eb t\u00eb nj\u00ebjtin depo si backend. N\u00eb deg\u00eb, p\u00ebrve\u00e7 ndryshimit t\u00eb baz\u00ebs s\u00eb kodit, zhvilluesi mund t\u00eb rregulloj\u00eb skenar\u00ebt ekzistues t\u00eb k\u00ebrkesave dhe testet. Pas regjistrimit t\u00eb ndryshimeve n\u00eb depo (git, svn, mercurial \u2014 \u00e7far\u00ebdo q\u00eb ju p\u00eblqen) CI (e preferuara juaj, e cila s'iu \u00ebsht\u00eb imponuar) aktivizon mjetin ton\u00eb konsol\u00eb testmace-cli<\/a><\/noindex>, dhe raporti i marr\u00eb pas ekzekutimit (p\u00ebr shembull, n\u00eb formatin junit, i cili gjithashtu mb\u00ebshtetet n\u00eb testmace-cli) d\u00ebrgohet n\u00eb sistemin p\u00ebrkat\u00ebs. Dhe, pyetja e p\u00ebrmendur m\u00eb lart p\u00ebr sigurin\u00eb tashm\u00eb s'\u00ebsht\u00eb problem.<\/p>\n

<\/p>\n

Si\u00e7 shihni, TestMace nuk imponon ekosistemin dhe paradigm\u00ebn e saj. N\u00eb vend t\u00eb k\u00ebsaj, ajo leht\u00eb integrohet n\u00eb proceset e themeluara.<\/p>\n

<\/p>\n

Variablat dinamike<\/h2>\n

<\/p>\n

TestMace ndjek konceptin no-code: n\u00ebse problemi mund t\u00eb zgjidhet pa p\u00ebrdorimin e kodit, ne p\u00ebrpiqemi t\u00eb ofrojm\u00eb k\u00ebt\u00eb mund\u00ebsi. Puna me variablat \u00ebsht\u00eb pik\u00ebrisht funksionaliteti ku n\u00eb shumic\u00ebn e rasteve mund t\u00eb kaloni pa programim.<\/p>\n

<\/p>\n

Shembuj: mor\u00ebm nj\u00eb p\u00ebrgjigje nga serveri dhe duam t\u00eb ruajm\u00eb nj\u00eb pjes\u00eb t\u00eb p\u00ebrgjigjes n\u00eb nj\u00eb variab\u00ebl. N\u00eb Postman do t\u00eb shkruanim n\u00eb skenarin e testit (\u00e7ka vet\u00eb \u00ebsht\u00eb e \u00e7uditshme) di\u00e7ka si:<\/p>\n

<\/p>\n

var jsonData = JSON.parse(responseBody);\npostman.setEnvironmentVariable(\"data\", jsonData.data);<\/code><\/pre>\n
<\/p>\n
Por sipas mendimit ton\u00eb, shkruarja e nj\u00eb skripti p\u00ebr nj\u00eb skenar kaq t\u00eb thjesht\u00eb dhe t\u00eb p\u00ebrdorur shpesh duket e tepruar. Prandaj n\u00eb TestMace ka mund\u00ebsin\u00eb p\u00ebr t\u00eb caktuar nj\u00eb pjes\u00eb t\u00eb p\u00ebrgjigjes nj\u00eb variabli duke p\u00ebrdorur nd\u00ebrfaqen grafike. Shihni sa e thjesht\u00eb \u00ebsht\u00eb:<\/p>\n
<\/p>\n
\"\u00c7far\u00eb<\/p>\n
<\/p>\n
Dhe tani, me \u00e7do k\u00ebrkes\u00eb, ky variab\u00ebl dinamik do t\u00eb p\u00ebrdit\u00ebsohet. Por ju mund t\u00eb kund\u00ebrshtoni, duke argumentuar se qasja e Postman \u00ebsht\u00eb m\u00eb fleksibile dhe lejon t\u00eb b\u00ebni jo vet\u00ebm caktimin, por gjithashtu t\u00eb kryeni nj\u00eb p\u00ebrpunim paraprak. Ja si mund t\u00eb modifikoni shembullin e m\u00ebparsh\u00ebm:<\/p>\n
<\/p>\n
var jsonData = JSON.parse(responseBody);\npostman.setEnvironmentVariable(\"data\", CryptoJS.MD5(jsonData.data));<\/code><\/pre>\n
<\/p>\n
Epo, p\u00ebr k\u00ebt\u00eb n\u00eb TestMace ka script<\/a><\/noindex> nj\u00eb nod, i cili mbulon k\u00ebt\u00eb skenar. P\u00ebr t\u00eb riprodhuar rastin e m\u00ebparsh\u00ebm, por tashm\u00eb n\u00eb implementimin e TestMace, \u00ebsht\u00eb e nevojshme pas k\u00ebrkes\u00ebs t\u00eb krijoni nj\u00eb nod script dhe si skript t\u00eb p\u00ebrdorni kodin e m\u00ebposht\u00ebm:<\/p>\n
<\/p>\n
const data = tm.currentNode.prev.response.body.data;\ntm.currentNode.parent.setDynamicVar('data', crypto.MD5(data));<\/code><\/pre>\n
<\/p>\n
Si\u00e7 e shihni, kompozita e node-ve k\u00ebtu ka sh\u00ebrbyer mir\u00eb. Dhe p\u00ebr nj\u00eb rast kaq t\u00eb thjesht\u00eb, si\u00e7 \u00ebsht\u00eb p\u00ebrshkruar m\u00eb sip\u00ebr, ju madje mund t\u00eb p\u00ebrcaktoni thjesht shprehjen ${crypto.MD5($response.data)}<\/code> p\u00ebr nj\u00eb variab\u00ebl, e cila krijohet p\u00ebrmes nd\u00ebrfaqes grafike!<\/p>\n
<\/p>\n
Krijimi i testeve p\u00ebrmes GUI<\/h2>\n
<\/p>\n
Postman lejon krijimin e testeve p\u00ebrmes shkruarjes s\u00eb skripteve (n\u00eb rastin e Postman \u00ebsht\u00eb JavaScript). Ky qasje ka vet\u00ebm avantazhe \u2014 fleksibilitet t\u00eb pakufizuar, zgjidhje t\u00eb gatshme, etj.<\/p>\n
<\/p>\n
Megjithat\u00eb, realitetet shpesh jan\u00eb t\u00eb tilla (nuk jemi ne k\u00ebshtu, \u00ebsht\u00eb k\u00ebshtu jeta), q\u00eb testuesi nuk ka aft\u00ebsi programimi, nd\u00ebrsa do t\u00eb donte t\u00eb kontribuonte n\u00eb ekip q\u00eb tani. P\u00ebr k\u00ebto raste, duke ndjekur konceptin no-code, TestMace lejon krijimin e testeve t\u00eb thjeshta p\u00ebrmes nj\u00eb nd\u00ebrfaqe grafike, pa u nevojitur t\u00eb shkruani skripte. Ja si duket procesi i krijimit t\u00eb nj\u00eb testi q\u00eb krahason vlerat p\u00ebr barazim:<\/p>\n
<\/p>\n
\"\u00c7far\u00eb<\/p>\n
<\/p>\n
Megjithat\u00eb, krijimi i testeve n\u00eb redaktorin grafik nuk anullon mund\u00ebsin\u00eb e shkruarjes s\u00eb testeve n\u00eb kod<\/a><\/noindex>. K\u00ebtu jan\u00eb t\u00eb nj\u00ebjtat biblioteka si n\u00eb nyj\u00ebn script, dhe chai<\/a><\/noindex> p\u00ebr shkruarjen e testeve.<\/p>\n
<\/p>\n
Dallime t\u00eb tjera<\/h2>\n
<\/p>\n