test: Isolate integration, external tests

[DaveSkender]

Description

Tests that use live data feeds or represent other forms of integration, such as end use of the package, should be separated from our normal unit test runs to avoid the slippery slope of cross-domain e2e forms. This isolation ensures we do not run these during normal local development unit test runs where speed and true unit test coverage are important.

Separating tests that reflect:

• use of external data feeds
• use of library as external package (pure UX tests)

To do

• add conditional and/or manual run triggers for local development
• add conditional and/or manual run triggers in CI/CD pipelines
• move External test portions from unit tests

Checklist

• My code follows the existing style, code structure, and naming taxonomy
• I have put comments in my code, particularly for hard-to-understand areas
• I have performed a self-review of my code and included any verifying manual calculations
• I have added or updated unit tests that prove my fix is effective or that my feature works and achieves sufficient code coverage. New and existing unit tests pass locally and in the build (below) with my changes
• My changes generate no new warnings or other code analysis issues
• I have added or run the performance tests that depict optimal execution times
• I have made corresponding changes to the documentation

[github-actions]

✔️ Tests 728 / 728 - passed in 7.3s
📝 Coverage 94.88%
📏 5471 / 5571 lines covered 🌿 2366 / 2689 branches covered
🔍 click here for more details

✏️ updated for commit 4730fd4