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

Investigate ways to speed up rspec run #1549

Open
Br3nda opened this issue Jan 21, 2018 · 5 comments
Open

Investigate ways to speed up rspec run #1549

Br3nda opened this issue Jan 21, 2018 · 5 comments

Comments

@Br3nda
Copy link
Member

Br3nda commented Jan 21, 2018

A fast test suite is run more often

@pozorvlak
Copy link
Member

+1. Some thoughts:

  • Smart test-runners: I looked into various gems for preloading tests or only running relevant tests soon after the project started, but the number of stale-cache problems I ran into made me give up; however, the tooling's probably improved since then.
  • Profile our tests: obviously. I think we'll find that the tests in spec/features are much slower than others - at least, they always seem to hold the top 3 spots reported by rspec. Then I guess we'd want to rewrite slow tests to be lower-level. Or maybe we could have a rake spec_fast target to only run the fast tests?
  • DB-less tests: is this feasible in Rails? It's common advice for speeding up tests in other ecosystems.

@CloCkWeRX
Copy link
Collaborator

For travis, we can turn of 'build branches' and rely on only pull requests building maybe.

@Br3nda
Copy link
Member Author

Br3nda commented Jan 22, 2018

Sounds like a plan. I think we can configure Travis to only run on pushes to the dev and master branch.

@Br3nda
Copy link
Member Author

Br3nda commented Jan 22, 2018

I've seen DB-less tests -- they use a lot of

expect(Garden).to receive(:where).with(args).and_return [garden1, garden2]

@stale
Copy link

stale bot commented Jul 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants