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

SpecFlow3 [C#]: Default.srprofile and Specflow.Json combination is not working for multiple browser Targets #1761

Closed
AnushaEdara opened this issue Oct 24, 2019 · 5 comments
Labels
Milestone

Comments

@AnushaEdara
Copy link

@AnushaEdara AnushaEdara commented Oct 24, 2019

We have recently migrated from Specflow2 to Specflow3. All the key value pairs from App.config are moved to specflow.json file and App.config file is excluded from solution. We have multi browser target requirement, Targets and Filters are set in Default.srprofile file. After building solution tests are discovered in Test Explorer as per the Targets given in .srprofile file, but they are skipping while running and control is not even reaching the Feature File. No message is showing in output window and it is showing elapsed time .
Environment:
Tool: VSTS 2017 Enterprise
SpecFlow 3
Test Project Type: MSTest project
Unit Test Provider: SpecRun

@AnushaEdara AnushaEdara changed the title SpecFlow3 [C#]: Default.srProfile and Specflow.Json combination is not working for multiple browser Targets SpecFlow3 [C#]: Default.srprofile and Specflow.Json combination is not working for multiple browser Targets Oct 24, 2019
@SabotageAndi

This comment has been minimized.

Copy link
Collaborator

@SabotageAndi SabotageAndi commented Oct 25, 2019

Thanks for reporting this issue. We found it on Monday and are working on a fix.
As a workaround until the fix is released, you can change the testThreadIsolationMode to "SharedAppDomain".

For that you have to add following line to your Default.srProfile within the TestProfile tags:

<Environment testThreadIsolation="SharedAppDomain"/>
@SabotageAndi SabotageAndi added the bug label Oct 25, 2019
@AnushaEdara

This comment has been minimized.

Copy link
Author

@AnushaEdara AnushaEdara commented Oct 25, 2019

Thanks for reporting this issue. We found it on Monday and are working on a fix.
As a workaround until the fix is released, you can change the testThreadIsolationMode to "SharedAppDomain".

For that you have to add following line to your Default.srProfile within the TestProfile tags:

Hi Andreas,

many.. Thanks for quick response.
It would be great help if you can share the lines code that needs to be added to .srprofile file to overcome this issue.

@SabotageAndi

This comment has been minimized.

Copy link
Collaborator

@SabotageAndi SabotageAndi commented Oct 25, 2019

Sorry, Markdown hid the xml tab.

This is the line:

<Environment testThreadIsolation="SharedAppDomain"/>
@SabotageAndi

This comment has been minimized.

Copy link
Collaborator

@SabotageAndi SabotageAndi commented Nov 8, 2019

This issue is fixed with the latest 3.1 preview version.

@AnushaEdara

This comment has been minimized.

Copy link
Author

@AnushaEdara AnushaEdara commented Nov 10, 2019

Many.. Thanks Andreas for the update,

Multi Browser Targeting is working for me now with SpecFlow 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.