Cypress: Best practise for conditional testing of presence of UI elements











up vote
0
down vote

favorite












I'm trying to start automated testing with Cypress. But apparently learning a new concept AND a new language is challenging... So I'm not sure if I found the best solution for simply testing the presence of UI elements depending on conditions.

All elements are rendered server-side.



So basically there is a DIV element which can contain either




  • a DIV element of class 'card'


OR




  • a P element of class 'no-ops'


In order to test this conditionally I figured out this code:



cy.get('div#section_paused_op').then(($div) => {
if($div.find('div.card').length > 0) {
cy.get('div#section_paused_op div.card').should('exist')
} else {
cy.get('div#section_paused_op p.no-ops').should('exist')
}
})


So to test the existence of the DIV element of class 'card' in one case, first I have to find it with find(). Is this good practice or can this be done in a better way?










share|improve this question




























    up vote
    0
    down vote

    favorite












    I'm trying to start automated testing with Cypress. But apparently learning a new concept AND a new language is challenging... So I'm not sure if I found the best solution for simply testing the presence of UI elements depending on conditions.

    All elements are rendered server-side.



    So basically there is a DIV element which can contain either




    • a DIV element of class 'card'


    OR




    • a P element of class 'no-ops'


    In order to test this conditionally I figured out this code:



    cy.get('div#section_paused_op').then(($div) => {
    if($div.find('div.card').length > 0) {
    cy.get('div#section_paused_op div.card').should('exist')
    } else {
    cy.get('div#section_paused_op p.no-ops').should('exist')
    }
    })


    So to test the existence of the DIV element of class 'card' in one case, first I have to find it with find(). Is this good practice or can this be done in a better way?










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm trying to start automated testing with Cypress. But apparently learning a new concept AND a new language is challenging... So I'm not sure if I found the best solution for simply testing the presence of UI elements depending on conditions.

      All elements are rendered server-side.



      So basically there is a DIV element which can contain either




      • a DIV element of class 'card'


      OR




      • a P element of class 'no-ops'


      In order to test this conditionally I figured out this code:



      cy.get('div#section_paused_op').then(($div) => {
      if($div.find('div.card').length > 0) {
      cy.get('div#section_paused_op div.card').should('exist')
      } else {
      cy.get('div#section_paused_op p.no-ops').should('exist')
      }
      })


      So to test the existence of the DIV element of class 'card' in one case, first I have to find it with find(). Is this good practice or can this be done in a better way?










      share|improve this question















      I'm trying to start automated testing with Cypress. But apparently learning a new concept AND a new language is challenging... So I'm not sure if I found the best solution for simply testing the presence of UI elements depending on conditions.

      All elements are rendered server-side.



      So basically there is a DIV element which can contain either




      • a DIV element of class 'card'


      OR




      • a P element of class 'no-ops'


      In order to test this conditionally I figured out this code:



      cy.get('div#section_paused_op').then(($div) => {
      if($div.find('div.card').length > 0) {
      cy.get('div#section_paused_op div.card').should('exist')
      } else {
      cy.get('div#section_paused_op p.no-ops').should('exist')
      }
      })


      So to test the existence of the DIV element of class 'card' in one case, first I have to find it with find(). Is this good practice or can this be done in a better way?







      user-interface testing automated-tests conditional cypress






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited yesterday

























      asked yesterday









      R0byn

      377




      377
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          As you mentioned best practices, I'm going to answer with that, and not a code suggestion:



          I would say your testing should be based on triggering those conditions, and knowing for sure what state something is meant to be in during that test.



          What makes the DIV with class "card" show up? Have a test that triggers that condition, then asserts that the element is there.



          What makes the P with class "no-ops" show up? Have a test that triggers that condition, then asserts that the element is there.



          Just because something is there on the page doesn't mean it should be.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53204316%2fcypress-best-practise-for-conditional-testing-of-presence-of-ui-elements%23new-answer', 'question_page');
            }
            );

            Post as a guest
































            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote













            As you mentioned best practices, I'm going to answer with that, and not a code suggestion:



            I would say your testing should be based on triggering those conditions, and knowing for sure what state something is meant to be in during that test.



            What makes the DIV with class "card" show up? Have a test that triggers that condition, then asserts that the element is there.



            What makes the P with class "no-ops" show up? Have a test that triggers that condition, then asserts that the element is there.



            Just because something is there on the page doesn't mean it should be.






            share|improve this answer

























              up vote
              1
              down vote













              As you mentioned best practices, I'm going to answer with that, and not a code suggestion:



              I would say your testing should be based on triggering those conditions, and knowing for sure what state something is meant to be in during that test.



              What makes the DIV with class "card" show up? Have a test that triggers that condition, then asserts that the element is there.



              What makes the P with class "no-ops" show up? Have a test that triggers that condition, then asserts that the element is there.



              Just because something is there on the page doesn't mean it should be.






              share|improve this answer























                up vote
                1
                down vote










                up vote
                1
                down vote









                As you mentioned best practices, I'm going to answer with that, and not a code suggestion:



                I would say your testing should be based on triggering those conditions, and knowing for sure what state something is meant to be in during that test.



                What makes the DIV with class "card" show up? Have a test that triggers that condition, then asserts that the element is there.



                What makes the P with class "no-ops" show up? Have a test that triggers that condition, then asserts that the element is there.



                Just because something is there on the page doesn't mean it should be.






                share|improve this answer












                As you mentioned best practices, I'm going to answer with that, and not a code suggestion:



                I would say your testing should be based on triggering those conditions, and knowing for sure what state something is meant to be in during that test.



                What makes the DIV with class "card" show up? Have a test that triggers that condition, then asserts that the element is there.



                What makes the P with class "no-ops" show up? Have a test that triggers that condition, then asserts that the element is there.



                Just because something is there on the page doesn't mean it should be.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 5 hours ago









                anonygoose

                52429




                52429






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53204316%2fcypress-best-practise-for-conditional-testing-of-presence-of-ui-elements%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest




















































































                    Popular posts from this blog

                    鏡平學校

                    ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

                    Why https connections are so slow when debugging (stepping over) in Java?