flaky issue - testing

[Satish-Pothabathula]

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes and the overall coverage did not decrease.
• All unit tests pass on CircleCi.
• I ran all tests locally and they pass.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.83%. Comparing base (1d8fdf5) to head (47abb7c).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##             master    #1034   +/-   ##
=========================================
  Coverage     88.83%   88.83%           
  Complexity     2391     2391           
=========================================
  Files           366      366           
  Lines         10640    10640           
  Branches       1538     1538           
=========================================
  Hits           9452     9452           
  Misses          835      835           
  Partials        353      353           

Flag	Coverage Δ
integration	48.87% <ø> (+0.29%)	⬆️
jest	86.68% <ø> (ø)
karma	95.59% <ø> (ø)
unittests	86.99% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.