simplecov: Cucumber tests failing in main branch
For some reason cucumber tests are failing for me when I run them locally in main branch. For example, I currently have a clean local copy on commit 9cd3a46169943f2c79d688d96e93871cd7febe2d and here is what I get:
$ be cucumber features/old_version_json.feature:12
Using the default profile...
....F
(::) failed steps (::)
Ambiguous match, found 3 elements matching visible css " .t-line-summary" (Capybara::Ambiguous)
./features/step_definitions/html_steps.rb:55:in `/^I should see a (.+) coverage summary of (\d+)\/(\d+)( for the file)?$/'
features/old_version_json.feature:18:in `I should see a line coverage summary of 8/9'
Failing Scenarios:
cucumber features/old_version_json.feature:12 # Scenario: Running the tests succeeds
1 scenario (1 failed)
5 steps (1 failed, 4 passed)
0m6.321s
It looks like I have wrong version of simplecov-html, but it’s locked to 0.12.2 in the Gemfile. Build fails on Github as well: https://github.com/umbrellio/simplecov/runs/1063083286 (I just pushed the main branch to the forked repo).
Any ideas how to fix that?
About this issue
- Original URL
- State: open
- Created 4 years ago
- Comments: 24
Commits related to this issue
- Switch to cuprite to avoid failures with new Chrome Fixes #925 Ref: https://github.com/twalpole/apparition/issues/64 — committed to simplecov-ruby/simplecov by PragTob 4 years ago
ah right the thing in expect is the actual not the expected… yeah that makes more sense. I hope I can give it another look this evening. It looks a bit scary as that might be further visibility shenanigans like I was facing with other browsers. Hopefully it’s just a timing issue which I should be able to fix