Troubleshooting

Required command was not provided

Symptoms The CLI prints the following error:

Required command was not provided. Unrecognized command or argument ‘…’

Resolution The upgraded CLI expects a mandatory “command” parameter. Please make sure to update your command line scripts according to the new parameter syntax. See an example in the upgrade guide above.

Unrecognized command or argument

Symptoms The CLI prints the following error:

Unrecognized command or argument ‘…’

Resolution The upgraded CLI uses kebab casing in the parameters. Please check the casing of the provided command or argument. See the CLI parameters.

Cannot find the specified JSON file - FeatureData.json

Symptoms: The CLI prints the following error:

Error: Cannot find the specified JSON file: <…some path..>\FeatureData.json

Resolution LivingDocPlugin v3.5 does not generate a “FeatureData.json” file anymore, the default file name has been changed to “TestExecution.json”. Please make sure to update the command line parameters when calling the CLI. Also make sure that you updated the LivingDocPlugin and the CLI to the same version.

Standalone HTML does not load

Symptoms When opening the standalone LivingDoc.html only a “Loading…” message is displayed, but the content is not loaded. In the browser console the following error is displayed:

Uncaught TypeError: e.tree.Nodes[0] is undefined

Resolution This error might occur if the LivingDocPlugin has been updated to v3.5, and the generated JSON (“TestExecution.json”) is being passed to an older version of the CLI. Please update the CLI to the same version as the LivingDocPlugin.

No “TestExecution.json” generated

Symptoms When running the SpecFlow tests there is no “TestExecution.json” generated.

Resolution Please check:

  1. Check the package version of the SpecFlow.Plus.LivingDocPlugin NuGet package in your SpecFlow project. You have to upgrade the NuGet package to at least v3.5 to have the new “TestExecution.json” output generated. Also make sure that you updated the LivingDocPlugin and the CLI to the same version.
  2. Check your specflow.json configuration. You might have configured a custom file path for the LivingDocPlugin.
  3. If you use the default configuration search for the file in the output directory of the SpecFlow project (in the same folder where the test assembly is located).