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

Fix1544 - Change search path for specflow.json and update configuration tests #1629

Merged
merged 14 commits into from Jun 27, 2019

Conversation

hgbchoi
Copy link
Contributor

@hgbchoi hgbchoi commented Jun 26, 2019

The GetSpecflowJsonFilePath method was looking for the specflow.json file in Environment.CurrentDirectory which may not be set to the same paths for all test frameworks. This was changed to AppDomain.CurrentDomain.BaseDirectory (the same directory as the project file).

I have also changed the assertions for the configuration tests to look for strings such as "Using specflow.json" in the compile results output instead of the test results output.

Types of changes

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist:

  • I've added tests for my code.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added an entry to the changelog

@SabotageAndi
Copy link
Contributor

Thanks for the PR!
Could you add an entry to the changelog? After that I will merge this PR and release a new version to nuget.org.

@hgbchoi
Copy link
Contributor Author

hgbchoi commented Jun 27, 2019

Thank you, I have added an entry to the changelog

@SabotageAndi SabotageAndi merged commit c195785 into SpecFlowOSS:master Jun 27, 2019
@SabotageAndi
Copy link
Contributor

Thanks for your contribution to SpecFlow. If you would like us to send you some SpecFlow stickers as a thank you, please fill out the form here.

idg10 pushed a commit to idg10/SpecFlow that referenced this pull request Jan 8, 2020
…on tests (SpecFlowOSS#1629)

* enable configuration scenarios

* Change search path for specflow.json

* Change test condition to look for configuration usage strings in complie result instead of output result

* Fix configuration tests

* Update submodule version

* Fix assertion

* enable configuration scenarios

* Change search path for specflow.json

* Change test condition to look for configuration usage strings in complie result instead of output result

* Fix configuration tests

* Update submodule version

* Fix assertion

* Update changelog.txt
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

2 participants