Feature: Ruby Automated Testing Introduction Lesson #22449
Merged
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
ZachBaird
reviewed
Jul 16, 2021
leosoaivan
reviewed
Jul 16, 2021
KevinMulhern
force-pushed
the
feature/ruby-automated-testing-introduction
branch
from
48bee16 to
d25cc4f
Compare
|
Thanks for all the feedback @ZachBaird, @wise-king-sullyman and @leosoaivan. It's very much appreciated 😄 |
|
|
||
| Depending on the size of the project, it could take anywhere from a few minutes to a few weeks in order to exhaustively test everything manually. This amount of time only increases as the project grows in size and complexity. | ||
|
|
||
| On the flip side, automated tests take a fraction of the time to run, often only seconds. And you only need to write an automated test once, after which it will test that behavior every time the test suite is run as opposed to having to repeatedly testing the same thing manually every time a change is made. |
There was a problem hiding this comment.
Suggested change
| On the flip side, automated tests take a fraction of the time to run, often only seconds. And you only need to write an automated test once, after which it will test that behavior every time the test suite is run as opposed to having to repeatedly testing the same thing manually every time a change is made. | |
| On the flip side, automated tests take a fraction of the time to run, often only seconds. And you only need to write an automated test once, after which it will test that behavior every time the test suite is run as opposed to repeatedly testing the same thing manually every time a change is made. |
There was a problem hiding this comment.
Nice catch 🎯 thanks dude.
Because: * We are writing a new section about automated testing in the Ruby course and this lesson will serve as the introduction to that section. It's purpose is to provide the big picture about automated tests and why they are important.
KevinMulhern
force-pushed
the
feature/ruby-automated-testing-introduction
branch
from
d25cc4f to
ed96f32
Compare
wise-king-sullyman
approved these changes
Jul 17, 2021
|
@wise-king-sullyman it wasn't a problem mate, all this feedback has been great. The lesson reads sooo much better now. Thanks for taking the time to review this everyone, I appreciate you all 😄 |
This was referenced Jul 29, 2021
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.
Because: