Validation and troubleshooting
Paxter has no standalone verify or database-validation command. Use these checks before relying on a workflow.
Validate the project
dotnet build Paxter.sln --configuration Release
dotnet test Paxter.sln --no-build --configuration Release
Validate a workflow safely
- Use a dedicated test environment and non-sensitive test data.
- Start with
Headless: trueandNeedVideo: false. - Set
Verbose: truein your local configuration when troubleshooting. - Review the generated HTML report and
output.jsonafter each run.
Common errors
| Message or symptom | Likely cause | What to check |
|---|---|---|
| Configuration file not found | paxter.yaml is not in the current working directory. | Run from the configuration directory or change into it first. |
| YAML test file not found | The path supplied to run does not exist. | Use an absolute path or verify the relative path. |
| Browser launch failure | Playwright browser binaries are unavailable or ChromiumPath is invalid. | Run paxter setup, or leave ChromiumPath empty to use Paxter's managed browser. |
| Unsupported conversion line | The converter does not recognise that Playwright statement. | Review the conversion log and add a supported action manually. |