Spring start afresh for each test run
up vote
1
down vote
favorite
Each time I run tests using rails test
, Spring starts up in a new instance. See below:
$ spring status
Spring is running:
56604 spring server | sample_app | started 9 mins ago
56804 spring app | sample_app | started 7 mins ago | test mode
$ rails test
Running via Spring preloader in process 57248
Started with run options --seed 27813
5/5: [=====================================================================================================================] 100% Time: 00:00:00, Time: 00:00:00
Finished in 0.58059s
5 tests, 9 assertions, 0 failures, 0 errors, 0 skips
Any way to prevent this to improve test suite performance?
ruby-on-rails spring testing
add a comment |
up vote
1
down vote
favorite
Each time I run tests using rails test
, Spring starts up in a new instance. See below:
$ spring status
Spring is running:
56604 spring server | sample_app | started 9 mins ago
56804 spring app | sample_app | started 7 mins ago | test mode
$ rails test
Running via Spring preloader in process 57248
Started with run options --seed 27813
5/5: [=====================================================================================================================] 100% Time: 00:00:00, Time: 00:00:00
Finished in 0.58059s
5 tests, 9 assertions, 0 failures, 0 errors, 0 skips
Any way to prevent this to improve test suite performance?
ruby-on-rails spring testing
I've got the same problem when I run tests inside of a docker container. I enter docker bash and there runrake test
and got the same results like @will-taylor
– mario199
Nov 20 at 16:28
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Each time I run tests using rails test
, Spring starts up in a new instance. See below:
$ spring status
Spring is running:
56604 spring server | sample_app | started 9 mins ago
56804 spring app | sample_app | started 7 mins ago | test mode
$ rails test
Running via Spring preloader in process 57248
Started with run options --seed 27813
5/5: [=====================================================================================================================] 100% Time: 00:00:00, Time: 00:00:00
Finished in 0.58059s
5 tests, 9 assertions, 0 failures, 0 errors, 0 skips
Any way to prevent this to improve test suite performance?
ruby-on-rails spring testing
Each time I run tests using rails test
, Spring starts up in a new instance. See below:
$ spring status
Spring is running:
56604 spring server | sample_app | started 9 mins ago
56804 spring app | sample_app | started 7 mins ago | test mode
$ rails test
Running via Spring preloader in process 57248
Started with run options --seed 27813
5/5: [=====================================================================================================================] 100% Time: 00:00:00, Time: 00:00:00
Finished in 0.58059s
5 tests, 9 assertions, 0 failures, 0 errors, 0 skips
Any way to prevent this to improve test suite performance?
ruby-on-rails spring testing
ruby-on-rails spring testing
asked Nov 19 at 21:55
Will Taylor
75611023
75611023
I've got the same problem when I run tests inside of a docker container. I enter docker bash and there runrake test
and got the same results like @will-taylor
– mario199
Nov 20 at 16:28
add a comment |
I've got the same problem when I run tests inside of a docker container. I enter docker bash and there runrake test
and got the same results like @will-taylor
– mario199
Nov 20 at 16:28
I've got the same problem when I run tests inside of a docker container. I enter docker bash and there run
rake test
and got the same results like @will-taylor– mario199
Nov 20 at 16:28
I've got the same problem when I run tests inside of a docker container. I enter docker bash and there run
rake test
and got the same results like @will-taylor– mario199
Nov 20 at 16:28
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383193%2fspring-start-afresh-for-each-test-run%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I've got the same problem when I run tests inside of a docker container. I enter docker bash and there run
rake test
and got the same results like @will-taylor– mario199
Nov 20 at 16:28