Uploaded image for project: 'stripes-data-transfer-components'
  1. stripes-data-transfer-components
  2. STDTC-18

jest/react-testing-library setup in stripes-data-transfer-components



    • Story
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • 4.0.0
    • None
    • Concorde - Sprint 101
    • 3
    • Concorde


      Setup jest/rtl in the ui-data-export and write the first tests to verify that they are running correctly as a part of the CI. However, as a result of this story jest/rtl tests won't be part of CI as for now the CI is configured to show the coverage for one test framework tool at the moment (Bigtest now). Once there is a setup (which should be introduced by the devops team according to Emelianov) to see both Bigtest and jest/rtl then jest/rtl should be enabled on CI as well.

      The suggested tests are on the screenshot below:

      Acceptance criteria:
      1. Jest/rtl is setup;
      2. Tests using the setup is written and the coverage above 80% is reached (according to the note below in order to prove it the screenshot should be attached in JIRA comment);

      Note: that Bigtest tests should not be removed for a while. The reason for this is that there is no way right now to see metrics for Bigtest tests run and jest/rtl tests run separately on CI. Once it is done we can start removing Bigtest tests when there are replacement tests written with jest/rtl and.

      TestRail: Results


          1. Screen Shot 2020-09-30 at 12.40.59 PM.png
            148 kB
            Viktor Soroka
          2. Screen Shot 2020-11-06 at 3.02.03 PM.png
            23 kB
            Viktor Soroka
          3. Screen Shot 2020-11-06 at 3.02.13 PM.png
            23 kB
            Viktor Soroka
          4. Screen Shot 2020-11-07 at 3.18.05 PM.png
            194 kB
            Viktor Soroka

          Issue Links



                Viktor Soroka Viktor Soroka
                Viktor Soroka Viktor Soroka
                0 Vote for this issue
                2 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases