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.

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

Use Sidekiq.fake instead of Sidekiq.inline by default #2195

Merged
merged 8 commits into from
Feb 5, 2025

Conversation

jayjay-w
Copy link
Contributor

Description

Use Sidekiq.fake instead of Sidekiq.inline by default for faster tests

References: CV2-4453

How has this been tested?

Confirmed that all tests pass

Checklist

  • I have performed a self-review of my own code
  • I have added unit and feature tests, if the PR implements a new feature or otherwise would benefit from additional testing
  • I have added regression tests, if the PR fixes a bug
  • I have added logging, exception reporting, and custom tracing with any additional information required for debugging
  • I considered secure coding practices when writing this code. Any security concerns are noted above.
  • I have commented my code in hard-to-understand areas, if any
  • I have made needed changes to the README
  • My changes generate no new warnings
  • If I added a third party module, I included a rationale for doing so and followed our current guidelines

 Use `Sidekiq.fake` instead of `Sidekiq.inline` by default for faster tests
@jayjay-w jayjay-w force-pushed the CV2-4453-use-sidekiq.fake branch from d171bc7 to 8cd805a Compare January 29, 2025 14:23
@jayjay-w jayjay-w marked this pull request as ready for review January 29, 2025 19:39
Copy link
Contributor

@caiosba caiosba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Jay, looks like the current PR addresses the first two bullet points we had in the ticket: Add Sidekiq.fake to the Test Helper setup method and add it to test suites that don't use the setup method. As expected, some tests have failed... much less than I expected tbh, so that's good! I assume more changes will be needed to fix the tests that broke. Please ask for a re-review once the tests are fixed. Also, please document in the ticket how long the build takes before and after this change.

@jayjay-w jayjay-w force-pushed the CV2-4453-use-sidekiq.fake branch from 73b2b13 to d3ed68e Compare February 4, 2025 11:48
@jayjay-w jayjay-w force-pushed the CV2-4453-use-sidekiq.fake branch from d3ed68e to 83e6f65 Compare February 4, 2025 19:03
@jayjay-w jayjay-w requested a review from caiosba February 4, 2025 21:08
@jayjay-w jayjay-w requested a review from caiosba February 5, 2025 10:38
Copy link

codeclimate bot commented Feb 5, 2025

Code Climate has analyzed commit 959e1e2 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (100% is the threshold).

This pull request will bring the total coverage in the repository to 100.0% (0.0% change).

View more on Code Climate.

@jayjay-w jayjay-w merged commit b3a26f0 into develop Feb 5, 2025
15 of 16 checks passed
@jayjay-w jayjay-w deleted the CV2-4453-use-sidekiq.fake branch February 5, 2025 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants