Details

    • Type: Testing
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: JS APIs and Utilities
    • Labels:
      None

      Description

      Review FI owned macros:

      1. Use macros to document purpose in conditionals and avoid having conditionals at the test layer
      2. Your test design on the testcase layer should strike a balance of readability and maintainability. Making use of macros allows you to maintain more readability but it makes it more difficult to know what is specifically wrong with the test or system under test. Think about what you would like to see when your test fails and try to automate your analysis to get you to the next step in analysis and not add an additional step

      ie: no extra assertions in the test where it's not necessary. If purpose of test is to verify that user can add a blog, then there shouldn't be any assertions checking that navigation page has loaded, or asserting all the success messages while getting there. Those should be verifyElementPresent steps instead of assert steps.

        Attachments

          Activity

            People

            Assignee:
            summer.zhang Summer Zhang
            Reporter:
            john.co John Co
            Recent user:
            Summer Zhang
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package