Skip to content

Upgrade to capybara 3#3361

Merged
mrcasals merged 5 commits intomasterfrom
upgrade_to_capybara_3
May 9, 2018
Merged

Upgrade to capybara 3#3361
mrcasals merged 5 commits intomasterfrom
upgrade_to_capybara_3

Conversation

@deivid-rodriguez
Copy link
Copy Markdown
Contributor

🎩 What? Why?

This is the alternative I mentioned in #3225 (comment), so that we can upgrade capybara without having to attempt a full rails upgrade.

📌 Related Issues

📋 Subtasks

None.

📷 Screenshots (optional)

None.

@ghost ghost assigned deivid-rodriguez May 8, 2018
@ghost ghost added the status: WIP label May 8, 2018
@mrcasals mrcasals merged commit 74dc358 into master May 9, 2018
@ghost ghost removed the status: WIP label May 9, 2018
@mrcasals mrcasals deleted the upgrade_to_capybara_3 branch May 9, 2018 07:04
@mrcasals mrcasals mentioned this pull request May 9, 2018
2 tasks
isaacmg410 pushed a commit to CodiTramuntana/decidim that referenced this pull request May 25, 2018
* Bump capybara version to 3.0.3

* Use capybara's default server

Because:

* We can configure quietness.
* It's Ctrl-C friendly.

Since we're configuring puma directly, add a explicit dev dependency on
it.

* Add a rake task to bundle all gemfiles at once

* Store logs as artifacts on circle CI failures

* Add "HTML screenshots" to test failures
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.

3 participants