I need to be able to deliver executable tests to the client and allow them to configure their parameters without having edit access to feature files, Visual Studio or the project itself. Clients will execute tests from command files (running dotnet test) and should be able to do this independently without help from our team. I've tried to hook tests up to Excel sheets and JSON files using the ExternalData plugin and have the client configure parameters in either of those document types.
Problem: The tests become immutable during the build and the client cannot modify inputs using the Excel or JSON files our tests reference. The client is not and should not be able to rebuild the project or even edit feature files. This is a requirement - we're allowing them to see the steps, but don't want them to modify feature files out of fear they will break the tests by accident.
If the above use case was covered by ExternalData the plugin could be used more as a supplement rather than an alternative way of writing tests.
Please sign in to leave a comment.