SpecFlow | SpecFlow automates | Functional Testing library

You can use WebDriverWait to send the keys like below:

I was able to achieve this by using "work item" instead of "Test Case". Using this, I am able to update all the field values.

Postman - add Content-Type = application/json-patch+json | under headers separately. Keep body as "raw" and "JSON" in drop down.

Azure Devops Work Items Rest API Details

The problem was with the docker command provided within the documentation:

SpecFlow scenarios are just plain text files. There is nothing stopping your client from opening up Notepad or any other text editor and writing new scenarios or features. They could even just write them in an e-mail and send it to you.

Visual Studio and the SpecFlow extension just make it easier to write new scenarios, because it enables auto-complete for steps. If your client doesn't need step suggestions, then any text editor will do.

Once you have their new scenarios, you can add new feature files to your test project. This will enable the step bindings and allow you to run the tests.

If you want the client to write scenarios and be able to run them, you are out of luck. That isn't supported unless you create a windows app that imports your step definitions, test dependencies and then parses the feature files into test classes before executing them.

So, you can partially get what you want.

1. Clients can write new scenarios in any text editor they want.
2. You would need to copy those scenarios into feature files in your test project.
3. You would be the one running the tests, not the client.

So here is how I fixed this:

1. I removed DotNetSeleniumExtras packages from code.
   After that, I was finally able to gather performance logs from browser because I got rid of errors shown in my question.
2. After removal of DotNetSeleniumExtras package I lost PageFactory for initialization of page objects.
   I fixed this problem by converting all web elements (properties of page object) into computed properties:

Because of InternalsVisibleTo. This enables access to internal types, methods, etc. to every object calling from the authorized assembly.

In https://github.com/SpecFlowOSS/SpecFlow/blob/master/TechTalk.SpecFlow/AssemblyAttributes.cs the assembly TechTalk.SpecFlow is decorated with some of this attributes, exposing all the internal methods to the listed assemblies:

• TechTalk.SpecFlow.RuntimeTests
• TechTalk.SpecFlow.PluginTests

It's a very common and useful technique used to test methods that should not be accessible to anyone, but that need to be tested.

I have never used SpecFlow or AWS CodeCommit, but a little bit of experimentation (for lack of thorough available documentation) strongly suggests that AndrewF's suspicion is correct:

Syntax highlighting rules highlight invalid statements for a SpecFlow feature file (example found on toolsqa.com) are highlighted with red background. On the left, the same rule seems to cause the grey background for removed invalid statements.

The highlighting rules seem to support And clauses, just not in the Then part of a scenario, although the language grammar seems to allow this. I blame a bad syntax highlighting rule.

_{However, I have a hard time finding a formal grammar specification for Cuccumber/Gherkin that would tell me exactly what is and isn't allowed where (and what a compliant parser would make of it).}

Why didn't I think of checking the source view first? Looking at the HTML/CSS rules of the above diff, one can see the markup in black and white: Red background equals . The same applies to the grey Foo on the left side of the diff.

1. If you still have the Visual Studio Extension (VSIX) for the NUnit Visual Studio Test Adapter (and it appears you do from your comment "We have NUnit3 added in the Extensions"), you need to disable or remove it. The VSIX adapter will be used over the Nuget packaged adapter and causes conflicts with the Nuget packaged adapter. The VSIX extension also shouldn't be used in VS 2017 or higher. You can check in Main Menu -> Tools-> Extensions and Updates and look for Nunit3TestAdapter.

   Using VSIX extensions was the old way to use test adapters and runners. It was brittle because you had one version installed in VS that needed to support many different projects and the VS extensions framework is pretty convoluted with awkward hooks into the build life cycle. The new way is to package test adapters and runners as NuGet packages. There is nothing to install and Visual Studio finds the version-specific test adapter and runner libraries for your project besides your test assemblies. You need to use one or the other, and Nuget packages are preferred now, or Visual Studio will fight against you and you'll have issues similar to what you are seeing.

2. The Visual Studio Test Explorer cache sometimes gets out of whack. Try closing all copies of Visual Studio and cleaning its temp files and folders at C:\Users{$username}\AppData\Local\Temp\VisualStudioTestExplorerExtensions\

3. You might be running into an issue where the test process is running on the is selecting the wrong architecture of the adapter or other library during test discovery orchestration. Try changing the default processor architecture for tests (Main Menu Test -> Test Settings). Try changing x86 to x64 or vice versa.

The behavior of the report is the correct one and sadly this can't be configured to be changed.

What you can do is to adjust how the results are reported back to Azure DevOps. You can configure it via the VSTest element in the srProfile- File.

This example means, that at least one retry has to be passing: