{"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\/da\/blog\/administrirovanie\/testrail-individualnye-nastrojki-pod-proekt","title":{"rendered":"TestRail \u2014 Individuelle indstillinger til projektet","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Introduktion<\/h2>\n

I mange projekter, jeg har arbejdet med, har folk ikke tilpasset TestRail til deres behov og har klaret sig med de standardindstillinger, der findes. Derfor vil jeg i denne artikel fors\u00f8ge at beskrive et eksempel p\u00e5 individuelle indstillinger, der kan hj\u00e6lpe dig med at \u00f8ge din arbejdeffektivitet. Som eksempel vil vi tage et projekt til udvikling af en mobilapp.<\/p>\n

Lille disclaimer. Denne artikel indeholder ikke en beskrivelse af den grundl\u00e6ggende funktionalitet i TestRail (der findes mange vejledninger til dette) eller salgsfremmende udtryk, der farverigt beskriver, hvorfor du skal v\u00e6lge netop denne leverand\u00f8r til at oprette et repository til testene.<\/p>\n

Projektplan (hvad der vil blive implementeret)<\/h2>\n
    \n
  1. \n

    Generelle krav<\/p>\n

      \n
    1. \n

      Kassen skal kunne gennemf\u00f8res af enhver person<\/p>\n<\/li>\n

    2. \n

      Kasserne skal opretholde relevans s\u00e5 l\u00e6nge som muligt<\/p>\n<\/li>\n

    3. \n

      Kasserne skal d\u00e6kke funktionaliteten af mobilappen s\u00e5 grundigt som muligt, s\u00e5 l\u00e6nge det ikke strider mod de to f\u00f8rstn\u00e6vnte punkter<\/p>\n<\/li>\n<\/ol>\n<\/li>\n

    4. \n

      Opdeling i TestCase og TestScenario<\/p>\n<\/li>\n

    5. \n

      Hurtig oprettelse af TestRun af forskellige typer<\/p>\n

        \n
      1. \n

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

      2. \n

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

      3. \n

        Impact testning osv.<\/p>\n<\/li>\n<\/ol>\n<\/li>\n

      4. \n

        Optimering af st\u00f8tte til kasserne<\/p>\n

          \n
        1. \n

          Oph\u00f8r med \"d\u00f8de\" h\u00e5rdkodede screenshots og overgang til \"movable data\"<\/p>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

          Krav<\/h2>\n

          For at redigere felterne skal du have administratoradgang<\/p>\n

          Valg af projekttype<\/h2>\n

          Du kan v\u00e6lge tre projekttyper:<\/p>\n

          \"TestRail<\/p>\n

          Vi v\u00e6lger standardtypen. Her vil alle kasser v\u00e6re tilg\u00e6ngelige samtidig. Vi vil bruge smart filtrering og dynamisk styre alle kasser samtidigt.<\/p>\n

          Tilf\u00f8jelse af felter til visning af listen over testkasser<\/h2>\n

          Vi tilf\u00f8jer et felt til at vise prioriteten af testkasser:<\/p>\n

          \"TestRail<\/p>\n

          Du kan ogs\u00e5 tilf\u00f8je andre felter.<\/p>\n

          Konfiguration af felter og tags i testkassen<\/h2>\n

          \u00c5bn indstillingsmenuen:<\/p>\n

          \"TestRail<\/p>\n

          Vi f\u00e5r brug for f\u00f8lgende felter:<\/p>\n

          Feltet \u00abSummary\u00bb (overskriften for testcasen)<\/h4>\n

          \"TestRail<\/p>\n

          Dette felt eksisterer allerede, vi systematiserer blot dets anvendelse. Vi vil opdele kasserne i TestCase og TestScenario. For bedre l\u00e6sbarhed af en stor liste af kasser er det en god id\u00e9 at blive enige om reglerne for skrivning af overskrifter.<\/p>\n

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

          Eksempel: TestScenario \u2014 Hovedscenariet for brugen af den mobile applikation<\/p>\n

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

          Eksempel: MainScreen \u2014 Log ind sektionen \u2014 Indtastning af brugernavn<\/p>\n

          Samlet set ser vi i oversigten over kassen den klassiske forst\u00e5else: \u201chvad, hvor, hvorn\u00e5r\u201d. Vi adskiller ogs\u00e5 visuelt de overordnede testsituationer og de detaljerede testkasser i den mest hensigtsm\u00e6ssige form for automatisering.<\/p>\n

          Tag \u00abStartScreen\u00bb (sk\u00e6rmen hvorfra TestScenario begynder, mange testcases kan ogs\u00e5 involvere nabosk\u00e6rme)<\/h4>\n

          Purpose: we will remove standard steps from the text of the test cases that lead the user to the current test case screen. (standard steps for creating a particular test situation) All standard steps for all test cases will be documented in one file. I will write more about it separately.<\/p>\n

          Creating a new field:<\/p>\n

          \"TestRail<\/p>\n

          Filling in the components of the new field: <\/p>\n

          \"TestRail<\/p>\n

          In this case, we are creating a selection field from a list of values. We enter the values for this field:<\/p>\n

          \"TestRail<\/p>\n

          Note that the value IDs do not start from one and do not go consecutively. Why is that? The reason is that if we have test cases written with a specific ID,<\/p>\n

          \"TestRail<\/p>\n

          and then we need to create a third screen between two existing ones,<\/p>\n

          \"TestRail<\/p>\n

          we will have to rewrite the IDs, and since existing test case tags are already tied to these IDs, they will simply be deleted. This would be very unpleasant.<\/p>\n

          Tag \u00abScreen\u00bb (navnet p\u00e5 sk\u00e6rmen, som TestCase omhandler)<\/h4>\n

          Purpose: one of the anchors for impact testing. For example, developers have created a new cool feature. We need to test it, but for that, we need to understand what this feature could have affected. By default, we can rely on the paradigm that different screens (Activity) of the application have different classes and therefore form different components of the application. Of course, in this case, an individual approach is needed.<\/p>\n

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

          \"TestRail<\/p>\n

          Feltet \u00abMovableData\u00bb (link til proxy DB med \u00e6ndrede testdata)<\/h4>\n

          Next, we will try to solve the problem of maintaining the relevance of data in test cases:<\/p>\n

            \n
          1. \n

            Links to up-to-date layouts (this is much better than making dead screenshots)<\/p>\n<\/li>\n

          2. \n

            Standard steps to the screen with the test situation<\/p>\n<\/li>\n

          3. \n

            SQL queries<\/p>\n<\/li>\n

          4. \n

            Links to external data and other information<\/p>\n<\/li>\n<\/ol>\n

            I stedet for at skrive testdata direkte ind i hver test case, vil vi oprette \u00e9n ekstern fil, og alle test cases vil referere til denne. Ved opdatering af disse data beh\u00f8ver vi ikke at gennemg\u00e5 alle test cases og \u00e6ndre dem, men kan blot \u00e6ndre dataene \u00e9t sted. Hvis nogen uden forberedelse \u00e5bner testcasen, vil de se et link til filen i testen og en besked om, at de skal henvende sig til den for testdata.<\/p>\n

            Alle disse data vil vi pakke ind i \u00e9n ekstern fil, som vil v\u00e6re tilg\u00e6ngelig for alle interesserede i projektet. For eksempel kan vi bruge Google Sheet eller Excel og oprette en s\u00f8gefunktion i filen. Hvorfor lige disse leverand\u00f8rer? Det er fordi, vi baserer os p\u00e5 paradigmet om, at enhver i teamet skal kunne \u00e5bne og gennemf\u00f8re en test case uden at skulle installere forskellige v\u00e6rkt\u00f8jer p\u00e5 forh\u00e5nd.<\/p>\n

            For Google Sheet<\/strong> man kan bruge SQL-foresp\u00f8rgsler. Eksempel:<\/p>\n

            =query(DATA!A1:M1146;\"\nSELECT C,D\nWHERE\nC contains '\"&SEARCH!A2&\"'\")<\/code><\/pre>\n
            For Excel<\/strong> man kan oprette praktiske makroer til \u00f8jeblikkelig s\u00f8gning. (filtrering) Eksempel via linket<\/a><\/noindex>.<\/p>\n
            Selve ideen er ikke ny og er beskrevet i den f\u00f8rste bog af testeren \"Testning dot com\". (forfatter Savin Roman) Vi integrerer blot de metoder, som Roman Savin foresl\u00e5r, i TestRail. For dette form\u00e5l opretter vi et felt med et link til den oprettede fil:<\/p>\n
            \"TestRail<\/p>\n
            vi udfylder standardv\u00e6rdien for linket, s\u00e5 hver ny test case allerede har et link:<\/p>\n
            \"TestRail<\/p>\n
            Hvis placeringen af den eksterne fil \u00e6ndres (vi forudser enhver force majeure), kan man nemt \u00e6ndre et eller flere felter i alle test cases p\u00e5 \u00e9n gang:<\/p>\n
            \"TestRail\"TestRail<\/p>\n
            Feltet \"Descriptions\" (beskrivelse eller id\u00e9 til test case, typiske instruktioner)<\/h4>\n
            Hvad det kan v\u00e6re nyttigt til: I dette tekstfelt vil vi placere en kort beskrivelse af test casen og typiske instruktioner.<\/p>\n
            Eksempel: Alle testdata (aktuelle skabeloner, brug af v\u00e6rkt\u00f8jer og andre data) fra denne test case er angivet med links {\u2026} og findes i filen MovableData. Linket til MovableData er i det relevante felt ovenfor.<\/em><\/p>\n
            \"TestRail<\/p>\n
            Tag \u00abComponent\u00bb (komponent i den mobile applikation)<\/h4>\n
            Hvad det kan bruges til: til impact-testning. Hvis en mobilapplikation kan opdeles i komponenter (der p\u00e5virker hinanden s\u00e5 lidt som muligt), er det tilstr\u00e6kkeligt at teste \u00e6ndringer i en komponent (med nogle risici) inden for den samme komponent, og der vil v\u00e6re f\u00e6rre grunde til at udf\u00f8re omfattende regressionstest af alt. Hvis der er information om, at en komponent kan p\u00e5virke en anden, oprettes der en matrice for impact-testning.<\/p>\n
            Eksempler p\u00e5 komponenter: GooglePay, Ordre, Brugere, Kort, Autorisation osv.<\/p>\n
            \"TestRail<\/p>\n
            Tag \u00abTAG\u00bb (andre tags til filtrering)<\/h2>\n
            Tagging af test cases med etiketter for vilk\u00e5rlig filtrering. <\/p>\n
            S\u00e6rdeles nyttigt til: <\/p>\n
              \n
            1. \n
              hurtigt at oprette TestRun til forskellige standardopgaver: smoke, regression osv.<\/p>\n<\/li>\n
            2. \n
              vil testene blive automatiseret eller er allerede automatiseret<\/p>\n<\/li>\n
            3. \n
              enhver anden tag<\/p>\n<\/li>\n<\/ol>\n
              Eksempel: Smoke, Automated, WhiteLabel, ForDelete osv.<\/p>\n
              \"TestRail\"TestRail<\/p>\n
              Vi konfigurerer r\u00e6kkef\u00f8lgen for visning af felter i test casen<\/h2>\n
              Vi har oprettet mange nye felter, nu er det tid til at arrangere dem i en praktisk r\u00e6kkef\u00f8lge:<\/p>\n
              \"TestRail<\/p>\n
              Oprettelse af TestRun<\/h2>\n
              Vi vil nu oprette et nyt test run med de relevante cases til udf\u00f8relse af smoke testning p\u00e5 tre klik:<\/p>\n
              \"TestRail<\/p>\n
              Andre nyttige tips<\/h2>\n
                \n
              1. \n
                Hvis der er flere projekter i TestRail, skal du ikke glemme at oprette nye felter kun til dit projekt, ellers vil kolleger fra nabogrupper blive meget overraskede over forekomsten af nye, us\u00e6dvanlige felter. Lokale svimmelhedsproblemer kan opst\u00e5.<\/p>\n<\/li>\n<\/ol>\n
                \"TestRail<\/p>\n
                2. Cases med mange felter er lettere at kopiere fra en lignende gruppe end at oprette nye:<\/p>\n
                \"TestRail<\/p>\n
                3. Du kan bruge konti f\u00e6lles. For eksempel: en administrativ, flere brugerkonti.<\/p>\n
                Konklusion<\/h2>\n
                De f\u00f8rn\u00e6vnte eksempler er implementeret i flere projekter og har vist sig effektive. Jeg h\u00e5ber, de vil hj\u00e6lpe med at forbedre din forst\u00e5else af dette v\u00e6rkt\u00f8j og hj\u00e6lpe med at skabe effektive og bekvemme \"testlagre\". Jeg vil v\u00e6re meget taknemmelig, hvis du i kommentarerne beskriver din erfaring med at bruge TestRail og nyttige tips.<\/p>\n
                Links:<\/p>\n
                TestRail leverand\u00f8rens hjemmeside<\/a><\/noindex><\/p>\n
                Bog: \u00abTestning .COM\u00bb (forfatter Roman Savin)<\/a><\/noindex><\/p>\n
                Tusind tak for opm\u00e6rksomheden!<\/p>\n
                Kilde: 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\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 Individuelle indstillinger til projektet | ProHoster","description":"IntroduktionI mange projekter, jeg har arbejdet med, har folk ikke konfigureret TestRail til deres behov og har n\u00f8jet sig med standardindstillinger.","canonical_url":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/testrail-individualnye-nastrojki-pod-proekt","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"da_DK","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\/da\/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\/da\/wp-json\/wp\/v2\/posts\/97474","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/comments?post=97474"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts\/97474\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media\/97475"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media?parent=97474"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/categories?post=97474"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/tags?post=97474"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}