Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tooling: Speed up test runs #2877

Open
jcfranco opened this issue Aug 20, 2021 · 1 comment
Open

Tooling: Speed up test runs #2877

jcfranco opened this issue Aug 20, 2021 · 1 comment
Labels
0 - new New issues that need assignment. estimate - 21 Requires planning, input from team members and possibly others. help wanted Issues that the core team needs help with in a sprint. p - medium Issue is non core or affecting less that 60% of people using the library testing Issues related to automated or manual testing. tooling Issues relating to build system fixes or improvements.
Milestone
2025-03-25 - 3.1....

Comments

@jcfranco
Copy link
Member

jcfranco commented Aug 20, 2021 •
edited by Elijbet
Loading

Summary

Current test runs on the CI are taking about ~20 mins. We should look into speeding these up.

Ideas:

  • clean up tests/assertions
  • revisit common tests/helpers to see if some are still relevant or if they can be merged
  • move non-interactive E2E tests to be spec tests. newSpecPage() is much faster since it does not require a full Puppeteer instance to be running. Stencil Docs on newSpecPage()
  • explore testing class logic directly. This approach allows you to test the component's class logic without the need for a full rendering setup. Stencil Docs on Testing Component Class Logic

Measure of Success

Any decrease in test run time would be a win.

Proposed Advantages

These approaches can help improve test execution time and overall efficiency.

Which Component

General refactor of the commonTest utils.
@jcfranco jcfranco added help wanted Issues that the core team needs help with in a sprint. testing Issues related to automated or manual testing. tooling Issues relating to build system fixes or improvements. 0 - new New issues that need assignment. labels Aug 20, 2021
@jcfranco jcfranco added this to the Freezer milestone Aug 20, 2021
@Elijbet Elijbet mentioned this issue Sep 8, 2023
Closed
2 tasks
@jcfranco jcfranco added 1 - assigned Issues that are assigned to a sprint and a team member. estimate - 21 Requires planning, input from team members and possibly others. p - medium Issue is non core or affecting less that 60% of people using the library and removed 0 - new New issues that need assignment. labels Feb 14, 2024
@brandentheintern brandentheintern added 2 - in development Issues that are actively being worked on. and removed 1 - assigned Issues that are assigned to a sprint and a team member. labels Apr 4, 2024
@jcfranco jcfranco added 0 - new New issues that need assignment. and removed 2 - in development Issues that are actively being worked on. labels Apr 21, 2024
@jcfranco jcfranco removed their assignment Apr 21, 2024
@jcfranco jcfranco added the spike complete Issues that have a research spike completed and dev work can proceed label Apr 21, 2024
@github-actions github-actions bot added the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Apr 21, 2024
@github-actions github-actions bot removed this from the 2024-04-30 - Apr Release milestone Apr 21, 2024
@github-actions GitHub Actions
Copy link
Contributor

cc @geospatialem, @brittneytewks

@jcfranco jcfranco removed the spike complete Issues that have a research spike completed and dev work can proceed label Apr 21, 2024
@geospatialem geospatialem added this to the 2025-03-25 - Mar Release milestone Sep 6, 2024
@geospatialem geospatialem removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - new New issues that need assignment. estimate - 21 Requires planning, input from team members and possibly others. help wanted Issues that the core team needs help with in a sprint. p - medium Issue is non core or affecting less that 60% of people using the library testing Issues related to automated or manual testing. tooling Issues relating to build system fixes or improvements.
Projects
None yet
Milestone
2025-03-25 - 3.1.0 Mar Release
Development

No branches or pull requests
4 participants
@jcfranco @alisonailea @geospatialem @brandentheintern