[FOLIO-2810] Create additional step for UI modules pipeline Created: 30/Sep/20  Updated: 19/Oct/20  Resolved: 19/Oct/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Anton Emelianov (Inactive) Assignee: John Malconian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps: Sprint 97, DevOps: Sprint 99
Development Team: FOLIO DevOps

 Description   

Integration and unit tests for UI modules will be converted to RTL/Jest with deadline Q3 2021. We need to provide teams with:
1) Additional build step for every UI module that will execute RTL/Jest tests
2) Istanbul coverage report for these tests. This report should be separate from existing Big Test report.

We have to try our best to run both tests until RTL/Jest coverage reaches 80% and we can drop old Big Tests.



 Comments   
Comment by John Malconian [ 14/Oct/20 ]

Using the model provided in ui-orders, we can execute both test suites (Jest and Big Test) sequentially during the Run Tests stage of the build pipeline. This is preferable to running them in parallel due to resource constraints. Both Big Test and Jest Junit test results are published in Jenkins. Separate coverage reports for each are also published in Jenkins. The link that displays the Jest coverage report is called 'Jest LCov Coverage Report'. It is NOT analyzed by the Sonarqube scanner at this time.

https://jenkins-aws.indexdata.com/job/folio-org/job/ui-orders/job/FOLIO-2810-jest/Jest_20LCov_20Coverage_20Report/

Generated at Thu Feb 08 23:23:24 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.