@Ihor Chekanov I guess also without tooling, you can manually map things like this:
- Feature: create a static Suite
- Scenario: add as a test case
- Background: use Shared steps for this
- Given, When: add as as test case steps (leave expected results empty)
- Then: either add this as Expected result to the last step in the test case, or add it as a seperate step
Another way could be to write the Gherkin scripts in Specflow and publish those to PicklesDoc and leave it there.
In Test Plan you could make Suites for the features and add Test Cases as scenario's, just like above. Instead of copy-pasting all the steps from Specflow/PickesDoc to Test Plan, simply put a link to the relevant Feature in PicklesDoc so testers can find it there for manual testing just in case they incidentally want to test manually.
Personally, if I look at our functional testers, I believe it would be nice if one could write tests in Test Plan, e.g. like written above and then push/pull to Specflow. So a developer can create the code behind the steps in using his techniscal toolchain (VS/Visual Studio) and our functional testers can keep away from the technical tooling like VS. That way our testers can feel at home in Devops and developers feel at home in VS. However apparently a tool whach could have been helpful for that was depricated, see https://docs.specflow.org/projects/specflow-excel/en/latest/
Not sure why it's no longer supported.
You might also want to check this:
https://support.specflow.org/hc/en-us/community/posts/360012819997-Support-for-SpecFlow-Excel-in-current-SpecFlow-versions