Fast and Efficient Testing #94
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
+1 I would like to hear about it |
|
👍 |
7 similar comments
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
👍 |
|
+1 |
|
👍 |
|
Judging from today's tweets, it looks like discussing how fewer but better tests helps improve the speed of your suite is an important topic and something I would definitely include in this talk :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want to share how we deal with large and complex test suites on our client projects at Hashrocket. The tools and techniques we use to keep a fast development pace without compromising our testing can benefit all attendees, regardless of skill level with Ruby. I think people will really enjoy the talk and be able to directly apply the content to their day-to-day development.