Unit test coverage for @carbon/ibm-products components

[elycheea]

This is a parallel issue to the work that @guidari has been doing in @carbon/react.

REF carbon-design-system/carbon#16319

The goal of this workstream is to increase confidence in each component, not just to increase coverage. It’s better to have 80% coverage with high-quality tests than 100% coverage with low-quality tests.

Important

Read the Carbon core kickoff notes below for implementation instructions and tips

Add code coverage CI check

Preview Give feedback

1. Research current code coverage approach from core team #6107
   1 of 2
   role: dev type: infrastructure 🤖 +2
   
2. Implement code coverage tooling #6108
   role: dev type: infrastructure 🤖 +2
   

Evaluate current test coverage

Preview Give feedback

1. Document list of components with under 80% test coverage #6109
   2 of 35
   role: dev type: infrastructure 🤖 type: process 🎞️ +3
   

Tests under 80% coverage

Preview Give feedback

1. Increase AddSelect code coverage #6653
   Debt component: AddSelect role: dev status: needs tests +4
2. Increase BigNumbers code coverage #6654
   Debt role: dev status: needs tests +3
3. Increase Carousel code coverage #6261
   component: Carousel status: needs tests type: enhancement 💡 +3
   
4. Increase Coachmark code coverage #6262
   component: Coachmark status: needs tests type: enhancement 💡 +3
   
5. Increase FeatureFlags code coverage #6655
   Debt role: dev status: needs tests +3
6. Increase GuideBanner code coverage #6263
   component: GuideBanner status: needs tests type: enhancement 💡 +3
   
7. Increase InterstitialScreen code coverage #6264
   component: Interstitial screen status: needs tests type: enhancement 💡 +3
   
8. Increase SidePanel code coverage #6265
   component: SidePanel status: needs tests type: enhancement 💡 +3
   
9. Increase StatusIcon code coverage #6651
   Debt component: StatusIcon role: dev status: needs tests +4
10. Increase TooltipTrigger code coverage #6652
    Debt role: dev status: needs tests +3

[ljcarot]

@elycheea Can you please check the list of components and patterns above and remove any that have been flagged for deprecation? Doesn't make sense to put the effort in to any that will be deprecated this year.

[elycheea]

I’ve removed the following from the list as components that are or should be deprecated in the near term.

• ActionSet (internal; potential to replace with ButtonSet)
• ComboButton (deprecated)
• DataSpreadsheet (to deprecate)
• Datagrid (to deprecate)
• EditUpdateCards (to deprecate)
• FilterPanel (to deprecate)
• Nav (to deprecate)
• StatusIndicator (to deprecate)
• UserProfileImage (to deprecate after UserAvatar release)

We can probably also deprioritize (and remove) the following that are being recategorized as utilities. If they are rewritten, we’ll see the coverage report in the PRs for them.

• ScrollGradient
• StringFormatter
• TagOverflow
• TruncatedList

Lastly, CreateModal, StatusIcon and EmptyState I’ve left in place for now since the latter two may have new versions but unclear when those will be delivered. And CreateModal we haven’t discussed more directly although I would recommend deprioritizing otherwise since we could rewrite this as pattern code.

[elycheea]

@ljcarot Compared the original list to Codecov and removed components/utilities that already reached 80% coverage. Converted any remaining tasks to issues.

Also removed TagOverflow which is still under 80% because @davidmenendez and @makafsal will look into coverage as part of #6601