{"id":97474,"date":"2020-10-19T02:42:20","date_gmt":"2020-10-19T00:42:20","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/testrail-individualnye-nastrojki-pod-proekt"},"modified":"2020-10-19T02:42:20","modified_gmt":"2020-10-19T00:42:20","slug":"testrail-individualnye-nastrojki-pod-proekt","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/testrail-individualnye-nastrojki-pod-proekt","title":{"rendered":"TestRail \u2013 Set\u0103ri personalizate pentru proiect","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Introducere<\/h2>\n

\u00cen multe proiecte cu care am lucrat, oamenii nu \u0219i-au personalizat TestRail \u0219i s-au descurcat cu set\u0103rile standard. A\u0219adar, \u00een acest articol, voi \u00eencerca s\u0103 descriu un exemplu de set\u0103ri personalizate care ar putea s\u0103 v\u0103 ajute s\u0103 \u00eembun\u0103t\u0103\u021bi\u021bi eficien\u021ba muncii dvs. Pentru exemplu, s\u0103 lu\u0103m un proiect de dezvoltare a unei aplica\u021bii mobile.<\/p>\n

O mic\u0103 precizare. \u00cen acest articol nu este descris\u0103 func\u021bionalitatea de baz\u0103 a TestRail (exist\u0103 multe ghiduri pentru aceasta) \u0219i nu sunt folosite expresii comerciale care s\u0103 descrie pl\u0103cut de ce ar trebui s\u0103 alegi acest furnizor pentru a crea un depozit de teste.<\/p>\n

Plan de fundamentare (ce va fi implementat)<\/h2>\n
    \n
  1. \n

    Cerin\u021be generale<\/p>\n

      \n
    1. \n

      Cazul trebuie s\u0103 poat\u0103 fi parcurs de oricine<\/p>\n<\/li>\n

    2. \n

      Cazurile trebuie s\u0103 \u00ee\u0219i p\u0103streze relevan\u021ba c\u00e2t mai mult timp<\/p>\n<\/li>\n

    3. \n

      Cazurile trebuie s\u0103 acopere c\u00e2t mai bine func\u021bionalitatea aplica\u021biei mobile, \u00een m\u0103sura \u00een care acest lucru nu contravine primelor dou\u0103 puncte<\/p>\n<\/li>\n<\/ol>\n<\/li>\n

    4. \n

      Separarea \u00een TestCase \u0219i TestScenario<\/p>\n<\/li>\n

    5. \n

      Generarea rapid\u0103 a TestRun de tipuri diferite<\/p>\n

        \n
      1. \n

        Smoke<\/p>\n<\/li>\n

      2. \n

        Regress<\/p>\n<\/li>\n

      3. \n

        Testarea de Impact etc.<\/p>\n<\/li>\n<\/ol>\n<\/li>\n

      4. \n

        Optimizarea suportului pentru cazuri<\/p>\n

          \n
        1. \n

          Renun\u021barea la capturi de ecran \u201emoarte\u201d hardcodate \u0219i trecerea la \u201edate mutabile\u201d<\/p>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

          Cerin\u021be<\/h2>\n

          Pentru a edita c\u00e2mpurile, ave\u021bi nevoie de acces de administrator<\/p>\n

          Alegerea tipului de proiect<\/h2>\n

          Se pot alege trei tipuri de proiecte:<\/p>\n

          \"TestRail<\/p>\n

          Vom alege tipul implicit. \u00cen acesta vor fi disponibile simultan toate cazurile. Vom folosi filtrarea inteligent\u0103 \u0219i vom gestiona dinamic toate cazurile deodat\u0103.<\/p>\n

          Ad\u0103ugarea c\u00e2mpurilor pentru vizualizarea listei de teste<\/h2>\n

          Vom ad\u0103uga un c\u00e2mp pentru a afi\u0219a prioritatea testelor:<\/p>\n

          \"TestRail<\/p>\n

          De asemenea, se pot ad\u0103uga \u0219i alte c\u00e2mpuri.<\/p>\n

          Configurarea c\u00e2mpurilor \u0219i etichetelor testelor<\/h2>\n

          Deschidem meniul de configurare:<\/p>\n

          \"TestRail<\/p>\n

          Avem nevoie de urm\u0103toarele c\u00e2mpuri:<\/p>\n

          C\u00e2mpul «Summary» (antetul cazului de test)<\/h4>\n

          \"TestRail<\/p>\n

          Acest c\u00e2mp exist\u0103 deja, vom sistematiza doar utilizarea sa. Vom separa cazurile \u00een TestCase \u0219i TestScenario. Pentru o mai bun\u0103 citire a unei liste mari de cazuri, cel mai bine este s\u0103 convenim din timp asupra regulilor de redactare a rezumatului.<\/p>\n

          TestScenario:<\/strong><\/p>\n

          Exemplu: TestScenario — Scenariul principal de utilizare a aplica\u021biei mobile<\/p>\n

          TestCase:<\/strong><\/p>\n

          Exemplu: MainScreen — Sec\u021biunea de autentificare — Introducerea numelui de utilizator<\/p>\n

          Prin urmare, vedem \u00een rezumatul cazului o \u00een\u021belegere clasic\u0103: \u201ece, unde, c\u00e2nd\u201d. De asemenea, vizual separ\u0103m scenariile de testare de nivel superior \u0219i cazurile de testare de nivel inferior \u00eentr-o form\u0103 care este cel mai potrivit pentru automatizare.<\/p>\n

          Eticheta «StartScreen» (ecranul de pe care \u00eencepe TestScenario; de asemenea, multe cazuri de test pot atinge ecranele \u00eenvecinate)<\/h4>\n

          Pentru ce poate fi necesar: vom elimina din textul testelor pa\u0219ii standard care duc utilizatorul la ecranul testului curent. (pa\u0219ii standard pentru crearea unei situa\u021bii de testare specifice) To\u021bi pa\u0219ii standard pentru toate testele vor fi descri\u0219i \u00eentr-un singur fi\u0219ier. Despre acesta voi scrie mai \u00een detaliu separat.<\/p>\n

          Cre\u0103m un nou c\u00e2mp:<\/p>\n

          \"TestRail<\/p>\n

          Umplem componentele noului c\u00e2mp: <\/p>\n

          \"TestRail<\/p>\n

          \u00cen acest caz, cre\u0103m un c\u00e2mp de selec\u021bie dintr-o list\u0103 de valori. Introducem valorile acestui c\u00e2mp:<\/p>\n

          \"TestRail<\/p>\n

          Aten\u021bie, ID-urile valorilor nu \u00eencep de la unu \u0219i nu sunt consecutive. De ce a\u0219a? Motivul este c\u0103, dac\u0103 vom avea teste \u00eenregistrate cu ID-uri introduse,<\/p>\n

          \"TestRail<\/p>\n

          \u0219i dup\u0103 aceea va fi necesar s\u0103 cre\u0103m un al treilea ecran \u00eentre cele dou\u0103 existente,<\/p>\n

          \"TestRail<\/p>\n

          atunci va trebui s\u0103 rescriem ID-urile, iar deoarece acestea sunt deja legate de etichetele testelor existente, ele vor fi pur \u0219i simplu \u0219terse. Acest lucru va fi foarte nepl\u0103cut.<\/p>\n

          Eticheta «Screen» (denumirea ecranului la care se refer\u0103 TestCase)<\/h4>\n

          Pentru ce poate fi necesar: unul dintre punctele de ancorare pentru testarea impactului. De exemplu, dezvoltatorii au realizat o nou\u0103 caracteristic\u0103 grozav\u0103. Trebuie s\u0103 o test\u0103m, dar pentru aceasta trebuie s\u0103 \u00een\u021belegem ce anume ar putea fi afectat de aceast\u0103 caracteristic\u0103. \u00cen mod implicit, ne putem baza pe paradigma c\u0103 diferitele ecrane (Activity) ale aplica\u021biei au clase diferite \u0219i, prin urmare, formeaz\u0103 componente diferite ale aplica\u021biei. Desigur, \u00een acest caz este necesar\u0103 o abordare individual\u0103.<\/p>\n

          Exemplu: home_screen, MapScreen, PayScreen etc.<\/p>\n

          \"TestRail<\/p>\n

          C\u00e2mpul «MovableData» (link c\u0103tre proxy-ul bazei de date cu date de test modificabile)<\/h4>\n

          \u00cen continuare, vom \u00eencerca s\u0103 rezolv\u0103m problema men\u021binerii actualiz\u0103rii datelor \u00een teste:<\/p>\n

            \n
          1. \n

            Linkuri c\u0103tre machete actualizate (acesta este mult mai bine dec\u00e2t s\u0103 facem capturi de ecran moarte)<\/p>\n<\/li>\n

          2. \n

            Pa\u0219ii standard p\u00e2n\u0103 la ecranul cu situa\u021bia de testare<\/p>\n<\/li>\n

          3. \n

            Interog\u0103ri SQL<\/p>\n<\/li>\n

          4. \n

            Linkuri c\u0103tre date externe \u0219i alte date<\/p>\n<\/li>\n<\/ol>\n

            \u00cen loc s\u0103 introducem datele de testare \u00een fiecare caz de test, vom crea un fi\u0219ier extern \u0219i vom face referire la acesta \u00een toate cazurile de test. Atunci c\u00e2nd actualiz\u0103m aceste date, nu va trebui s\u0103 parcurgem toate cazurile de test pentru a le modifica, ci putem schimba aceste date \u00eentr-un singur loc. Dac\u0103 cineva neavizat deschide un caz de test, va vedea \u00een corpul cazului de test un link c\u0103tre fi\u0219ier \u0219i o sugestie c\u0103 trebuie s\u0103 mearg\u0103 acolo pentru datele de testare.<\/p>\n

            Toate aceste date le vom ambala \u00eentr-un singur fi\u0219ier extern, care va fi disponibil tuturor celor interesa\u021bi \u00een proiect. De exemplu, putem folosi Google Sheet sau Excel \u0219i s\u0103 configur\u0103m c\u0103utarea \u00een interiorul fi\u0219ierului. De ce anume ace\u0219ti furnizori? Pentru c\u0103 ne baz\u0103m pe paradigma c\u0103 oricine din echip\u0103 trebuie s\u0103 fie capabil s\u0103 deschid\u0103 \u0219i s\u0103 parcurg\u0103 un caz de test f\u0103r\u0103 a necesita instalarea preliminar\u0103 a diverselor unelte.<\/p>\n

            Pentru Google Sheet<\/strong> putem folosi interog\u0103ri SQL. Exemplu:<\/p>\n

            =query(DATA!A1:M1146;\"\nSELECT C,D\nWHERE\nC contains '\"&SEARCH!A2&\"'\" )<\/code><\/pre>\n
            Pentru Excel<\/strong> putem configura macrocomenzi convenabile pentru c\u0103utare rapid\u0103. (filtrare) Exemplu la link<\/a><\/noindex>.<\/p>\n
            Ideea, de fapt, nu este nou\u0103 \u0219i este descris\u0103 \u00een prima carte a testerului \u201eTestarea dot com\u201d. (autor Savin Roman) Noi integr\u0103m doar \u00een TestRail metodologiile propuse de Roman Savin. Pentru aceasta, vom crea un c\u00e2mp cu un link c\u0103tre fi\u0219ierul creat:<\/p>\n
            \"TestRail<\/p>\n
            complet\u0103m valoarea implicit\u0103 a linkului, astfel \u00eenc\u00e2t \u00een fiecare caz de test nou s\u0103 existe deja un link:<\/p>\n
            \"TestRail<\/p>\n
            Dac\u0103 loca\u021bia fi\u0219ierului extern se va schimba (preconiz\u0103m orice for\u021b\u0103 major\u0103), atunci putem modifica convenabil \u00een toate cazurile de test simultan unul sau mai multe c\u00e2mpuri:<\/p>\n
            \"TestRail\"TestRail<\/p>\n
            C\u00e2mpul \u201eDescriptions\u201d (descriere sau idee a cazului de test, instruc\u021biuni tipice)<\/h4>\n
            Pentru ce poate fi necesar: \u00cen acest c\u00e2mp text, vom introduce o descriere scurt\u0103 a cazului de test \u0219i instruc\u021biuni tipice.<\/p>\n
            Exemplu: Toate datele de test (modele actuale, utilizarea uneltelor \u0219i alte date) din acest caz de test sunt marcate cu linkuri {\u2026} \u0219i se afl\u0103 \u00een fi\u0219ierul MovableData. Linkul c\u0103tre MovableData se afl\u0103 \u00een c\u00e2mpul corespunz\u0103tor de sus.<\/em><\/p>\n
            \"TestRail<\/p>\n
            Eticheta «Component» (componenta aplica\u021biei mobile)<\/h4>\n
            Pentru ce poate fi necesar: pentru testarea de impact. Dac\u0103 o aplica\u021bie mobil\u0103 poate fi \u00eemp\u0103r\u021bit\u0103 \u00een componente (care afecteaz\u0103 c\u00e2t mai pu\u021bin una pe cealalt\u0103), atunci modific\u0103rile \u00eentr-o component\u0103 vor fi suficiente (cu anumite riscuri) pentru a fi verificate \u00een cadrul acelei componente, iar motivele pentru a efectua regresii generale vor fi reduse. Dac\u0103 exist\u0103 informa\u021bii c\u0103 o component\u0103 poate afecta o alt\u0103 component\u0103, se elaboreaz\u0103 o matrice de testare de impact.<\/p>\n
            Exemple de componente: GooglePay, Order, Users, Map, Authorization etc.<\/p>\n
            \"TestRail<\/p>\n
            Eticheta «TAG» (alte etichete pentru filtrare)<\/h2>\n
            Etichetarea cazului de testare cu etichete pentru filtrare arbitrar\u0103. <\/p>\n
            Foarte util pentru: <\/p>\n
              \n
            1. \n
              compunerea rapid\u0103 a TestRun pentru diverse sarcini standard: smoke, regresie etc.<\/p>\n<\/li>\n
            2. \n
              dac\u0103 testele vor fi automatizate sau sunt deja automatizate<\/p>\n<\/li>\n
            3. \n
              orice alte etichete<\/p>\n<\/li>\n<\/ol>\n
              Exemplu: Smoke, Automated, WhiteLabel, ForDelete etc.<\/p>\n
              \"TestRail\"TestRail<\/p>\n
              Configur\u0103m ordinea de afi\u0219are a c\u00e2mpurilor \u00een cazul de testare<\/h2>\n
              Am creat multe c\u00e2mpuri noi, acum este timpul s\u0103 le organiz\u0103m \u00eentr-o ordine convenabil\u0103:<\/p>\n
              \"TestRail<\/p>\n
              Crearea TestRun<\/h2>\n
              Acum vom crea un nou test run cu cazurile actuale pentru a efectua testarea smoke \u00een trei clicuri:<\/p>\n
              \"TestRail<\/p>\n
              Alte sfaturi utile<\/h2>\n
                \n
              1. \n
                Dac\u0103 \u00een TestRail sunt mai multe proiecte, nu uita\u021bi s\u0103 crea\u021bi c\u00e2mpuri noi doar pentru proiectul dvs., altfel colegii din echipele vecine vor fi foarte surprin\u0219i de apari\u021bia unor c\u00e2mpuri noi neobi\u0219nuite. Pot ap\u0103rea lesinuri locale.<\/p>\n<\/li>\n<\/ol>\n
                \"TestRail<\/p>\n
                2. Cazurile cu un num\u0103r mare de c\u00e2mpuri sunt mai u\u0219or de copiat dintr-un grup similar dec\u00e2t de a crea noi:<\/p>\n
                \"TestRail<\/p>\n
                3. Pute\u021bi folosi conturi \u00een comun. De exemplu: un cont de administrator, mai multe conturi de utilizator.<\/p>\n
                Concluzie<\/h2>\n
                Exemplele de mai sus au fost implementate \u00een mai multe proiecte \u0219i \u0219i-au demonstrat eficien\u021ba. Sper c\u0103 v\u0103 vor ajuta s\u0103 \u00een\u021belege\u021bi mai bine acest instrument \u0219i s\u0103 crea\u021bi \u201eb\u0103nci de teste\u201d eficiente \u0219i convenabile. A\u0219 fi foarte recunosc\u0103tor dac\u0103 a\u021bi descrie \u00een comentarii experien\u021ba dvs. de utilizare a TestRail \u0219i sfaturi utile.<\/p>\n
                Linkuri:<\/p>\n
                Site-ul vendorului TestRail<\/a><\/noindex><\/p>\n
                Cartea: «Testare .COM» (autor Roman Savin)<\/a><\/noindex><\/p>\n
                V\u0103 mul\u021bumesc mult pentru aten\u021bie!<\/p>\n
                Sursa: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
                \u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0412\u043e \u043c\u043d\u043e\u0433\u0438\u0445 \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u0445, \u0441 \u043a\u043e\u0442\u043e\u0440\u044b\u043c\u0438 \u044f \u0440\u0430\u0431\u043e\u0442\u0430\u043b, \u043b\u044e\u0434\u0438 \u043d\u0435 \u043d\u0430\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u043b\u0438 \u043f\u043e\u0434 \u0441\u0435\u0431\u044f TestRail \u0438 \u043e\u0431\u0445\u043e\u0434\u0438\u043b\u0438\u0441\u044c \u0441\u0442\u0430\u043d\u0434\u0430\u0440\u0442\u043d\u044b\u043c\u0438 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430\u043c\u0438. \u041f\u043e\u044d\u0442\u043e\u043c\u0443 \u0432 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u044f \u043f\u043e\u0441\u0442\u0430\u0440\u0430\u044e\u0441\u044c \u043e\u043f\u0438\u0441\u0430\u0442\u044c \u043f\u0440\u0438\u043c\u0435\u0440 \u0438\u043d\u0434\u0438\u0432\u0438\u0434\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043d\u0430\u0441\u0442\u0440\u043e\u0435\u043a, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u0443\u0442 \u043f\u043e\u043c\u043e\u0447\u044c \u0412\u0430\u043c \u043f\u043e\u0432\u044b\u0441\u0438\u0442\u044c \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0441\u0442\u044c \u0441\u0432\u043e\u0435\u0439 \u0440\u0430\u0431\u043e\u0442\u044b. \u0414\u043b\u044f \u043f\u0440\u0438\u043c\u0435\u0440\u0430 \u0432\u043e\u0437\u044c\u043c\u0435\u043c \u043f\u0440\u043e\u0435\u043a\u0442 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u043c\u043e\u0431\u0438\u043b\u044c\u043d\u043e\u0433\u043e \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f. \u041d\u0435\u0431\u043e\u043b\u044c\u0448\u043e\u0439 \u0434\u0438\u0441\u043a\u043b\u0435\u0439\u043c\u0435\u0440. \u0412 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043d\u0435\u0442 \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u044f \u0431\u0430\u0437\u043e\u0432\u043e\u0433\u043e \u0444\u0443\u043d\u043a\u0446\u0438\u043e\u043d\u0430\u043b\u0430 TestRail (\u043d\u0430 \u044d\u0442\u043e […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":97475,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-97474","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\udd47TestRail \u2014 Set\u0103ri personalizate pentru proiect | ProHoster","description":"Introducere\u00cen multe proiecte cu care am lucrat, oamenii nu \u0219i-au configurat TestRail pentru a se potrivi nevoilor lor \u0219i s-au descurcat cu set\u0103rile standard.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/testrail-individualnye-nastrojki-pod-proekt","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\udd47TestRail \u2014 \u0418\u043d\u0434\u0438\u0432\u0438\u0434\u0443\u0430\u043b\u044c\u043d\u044b\u0435 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 \u043f\u043e\u0434 \u043f\u0440\u043e\u0435\u043a\u0442 | ProHoster","og:description":"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435\u0412\u043e \u043c\u043d\u043e\u0433\u0438\u0445 \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u0445, \u0441 \u043a\u043e\u0442\u043e\u0440\u044b\u043c\u0438 \u044f \u0440\u0430\u0431\u043e\u0442\u0430\u043b, \u043b\u044e\u0434\u0438 \u043d\u0435 \u043d\u0430\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u043b\u0438 \u043f\u043e\u0434 \u0441\u0435\u0431\u044f TestRail \u0438 \u043e\u0431\u0445\u043e\u0434\u0438\u043b\u0438\u0441\u044c \u0441\u0442\u0430\u043d\u0434\u0430\u0440\u0442\u043d\u044b\u043c\u0438 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430\u043c\u0438.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/testrail-individualnye-nastrojki-pod-proekt","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":"2020-10-19T00:42:20+00:00","article:modified_time":"2020-10-19T00:42:20+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"97474","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 10:19:39","updated":"2022-09-30 01:20:29","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/97474","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=97474"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/97474\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/97475"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=97474"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=97474"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=97474"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}