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

Update README.md summary about testing #2442

Merged
merged 1 commit into from
Dec 13, 2017

Conversation

benjaminwil
Copy link
Contributor

In #2433, I rewrote and expanding the getting started guide to discuss developing Solidus. In a review, @tvdeyen requested some changes regarding testing. These changes are also required in Solidus's README:

  • Solidus no longer uses PhantomJS for running backend and frontend tests. Now it uses ChromeDriver.
  • @tvdeyen also mentioned:

    We should not promote a custom ENV var [FAIL_FAST=true] but the rspec --fail-fast feature instead. But this is common rspec knowledge, I don't think we need to mention it in our guides at all.

I also took the liberty of making the markdown more readable in this section.

In solidusio#2433, I rewrote and expanded the getting started guide to discuss
developing Solidus. In a review, tvdeyen requested some changes
regarding testing. These changes are also required in Solidus's README:

- Solidus no longer uses PhantomJS for running backend and frontend
  tests. Now it uses ChromeDriver.
- tvdeyen also mentioned "We should not promote a custom ENV var
  [`FAIL_FAST=true`] but the rspec `--fail-fast` feature instead. But
  this is common rspec knowledge, I don't think we need to mention it in
  our guides at all."

I also took the liberty of making the markdown more readable in this
section.
@jhawthorn jhawthorn merged commit baf6e6f into solidusio:master Dec 13, 2017
@benjaminwil benjaminwil deleted the readme_testing branch April 30, 2018 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants