scripts

XML postprocessor tests

These PowerShell scripts test the complete SmartPost intermediate XML path:

Autodesk .cnc dataset
-> xml_last.cps or xml.cps
-> XML
-> post.exe --format xml
-> unchanged downstream .cps
-> NC output

The scripts never edit the downstream postprocessor. Generated XML, NC, log, and CSV files are written below the selected output directory.

Test one dataset

.\scripts\test-xml-roundtrip.ps1 `
  -PostExe "C:\path\to\post.exe" `
  -InputFile "C:\path\to\deep drilling.cnc" `
  -DownstreamPost "C:\path\to\fanuc.cps" `
  -OutputDirectory ".\tmp\roundtrip"

By default, the script tests both commands/smart_post_dialog/xml_last.cps and commands/smart_post_dialog/xml.cps. Use -XmlPost to test a specific file.

Test every dataset in a directory

.\scripts\test-xml-cycle-matrix.ps1 `
  -PostExe "C:\path\to\post.exe" `
  -InputDirectory "C:\path\to\CNC files\Milling\Drilling" `
  -DownstreamPost "C:\path\to\fanuc.cps" `
  -OutputDirectory ".\tmp\cycle-matrix"

The matrix writes results.csv and reports XML export status, XML import status, restored cycle callbacks, internal errors, and detected G81-G89 codes.

Reproduce the turning Section.type limitation

The following test verifies that a turning CNC intermediate is loaded as TYPE_TURNING, while the same data exported through xml_last.cps is restored as TYPE_MILLING. It also confirms that an unchanged turning post rejects the XML section as milling.

.\scripts\test-xml-section-type.ps1 `
  -PostExe "C:\path\to\post.exe" `
  -InputFile ".\tmp\1001.cnc" `
  -DumpPost ".\tmp\post\dump.cps" `
  -TurningPost ".\tmp\post\fanuc turning.cps" `
  -OutputDirectory ".\tmp\section-type"

The script does not edit dump.cps, the turning post, or post.exe.