Spring is meant to make running locally (as in development and test) nearly as
quick as running in production (where everything is cached). development isn't
cached because it would mean you would have to stop the server and re-start
every time you made any change at all. test is meant to be the
Thanks, Rob! Entering "DISABLE_SPRING=1 rails test" gives me the 93.16%
test coverage.
Exactly what is the significance of the Spring server? Why isn't Rails set
up to automatically take care of this?
On Saturday, October 20, 2018 at 9:39:11 AM UTC-5, Rob Zolkos wrote:
>
> In development run
In development run your tests with the DISABLE_SPRING=1 flag before the
test command and see if you see a difference in coverage.
On Sun, Oct 21, 2018 at 12:17 AM Jason Hsu, Ruby on High Speed Rails <
jhsu802...@gmail.com> wrote:
> How can I get test coverage results to show more consistent resul
How can I get test coverage results to show more consistent results that
make sense?
I earlier decided against having SimpleCov and test coverage badges in my
Rails apps. It seemed that no matter how I configured SimpleCov, there
were some glaring flaws in its results. However, I have since c
4 matches
Mail list logo