Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

Examples.feature changes overwritten whenever BLT is updated #1322

Closed
geerlingguy opened this issue Apr 5, 2017 · 3 comments
Closed

Examples.feature changes overwritten whenever BLT is updated #1322

geerlingguy opened this issue Apr 5, 2017 · 3 comments
Assignees

Comments

@geerlingguy
Copy link
Contributor

My system information:

  • Operating system type: macOS
  • Operating system version: 10.12.4
  • BLT version: 8.7.0

When I update BLT, the tests/behat/features/Examples.feature file is reverted to BLT's default example feature file:

diff --git a/tests/behat/features/Examples.feature b/tests/behat/features/Examples.feature
index d81895d..c3a0795 100644
--- a/tests/behat/features/Examples.feature
+++ b/tests/behat/features/Examples.feature
@@ -8,8 +8,8 @@ Feature: Web drivers
   @javascript
   Scenario: Load a page with Javascript
     Given I am on "/"
-    Then I should see the text "Something on my site"
+    Then I should see the text "Log in"
 
   Scenario: Load a page without Javascript
     Given I am on "/"
-    Then I should see the text "Something on my site"
+    Then I should see the text "Log in"

I would rather that file be left alone. Our site doesn't have the text "Log in" on the home page, so every time I update BLT, I am reminded by our CI environment that I have to go back in and revert the changes to that file so tests pass.

@geerlingguy
Copy link
Contributor Author

I can, of course, run git checkout -- tests/behat/features/Examples.feature after every update, but after doing this about 8 times I figured I'd finally open an issue.

@grasmash
Copy link
Contributor

grasmash commented Apr 5, 2017

Well, we can prevent this file from being overwritten, but do you really need to modify the example file?

@geerlingguy
Copy link
Contributor Author

@grasmash - If I don't change it, it causes tests to fail; we put all our feature files in that directory and tell behat to run all those tests. We disabled the 'Log in' link block on our site since it shouldn't display any login links anywhere.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants