Skip to content

Commit

Permalink
modifed steps
Browse files Browse the repository at this point in the history
  • Loading branch information
kodai-t committed May 30, 2024
1 parent ad34c97 commit f15a3a1
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion steps_en.md
Original file line number Diff line number Diff line change
Expand Up @@ -175,7 +175,7 @@ Create CRUD to manage the tasks. First of all, let's make it with a simple struc
**Note**: Remove the `webdrivers` gem from your Gemfile. If `webdrivers` is present, it will attempt to find Chrome in your application’s container.
As Chrome isn’t installed in the Dockerfile, the spec will fail.

- Before start testing we need to register a new driver with Capybara that is configured to use the Selenium container, add the below codes to
- If you are using Docker, before start testing we need to register a new driver with Capybara that is configured to use the Selenium container, add the below codes to
`spec/rails_helper.rb`
```
Capybara.register_driver :remote_chrome do |app|
Expand Down
2 changes: 1 addition & 1 deletion steps_jp.md
Original file line number Diff line number Diff line change
Expand Up @@ -302,7 +302,7 @@ chrome://extensions/ を開いて右上のDeveloper modeをオンにして、RKG
**Note**: Remove the `webdrivers` gem from your Gemfile. If `webdrivers` is present, it will attempt to find Chrome in your application’s container.
As Chrome isn’t installed in the Dockerfile, the spec will fail.
- Before start testing we need to register a new driver with Capybara that is configured to use the Selenium container, add the below codes to
- If you are using Docker, before start testing we need to register a new driver with Capybara that is configured to use the Selenium container, add the below codes to
`spec/rails_helper.rb`
```
Capybara.register_driver :remote_chrome do |app|
Expand Down

0 comments on commit f15a3a1

Please sign in to comment.