dotcsv Module Tests

A standalone Blazium project for validating the native dotcsv module.

This project mirrors the other Blazium module test projects. It uses the native Autowork test runner and exercises the script-facing API exposed by CSV, DSVImporter, DSVExporter, CSVImporter, and CSVExporter.

Requirements

• A Blazium editor build that includes the dotcsv and autowork modules.
• The Blazium executable on your PATH, or a direct path to the executable.

These tests were created against the Blazium csv-module branch after adding modules/dotcsv.

Running Tests

From this project directory:

blazium --headless -s run_tests.gd

On Windows with a local source checkout:

path/to/blazium/bin/blazium.windows.editor.x86_64.console.exe --headless -s run_tests.gd

The process exits with the Autowork failure count. A successful run exits with 0.

Coverage

The suite validates:

• DSVImporter: quoted fields, escaped quotes, embedded line endings, invalid delimiters, and uneven row handling.
• DSVExporter: CRLF output, quote and delimiter escaping, row padding, and file export.
• CSVImporter: typed field conversion, headers, column type unification, disabled unification, colors, vectors, arrays, and dictionaries.
• CSVExporter: typed rows, dictionaries with dynamic headers, hex color output, packed color arrays, and round-trip behavior.
• CSV: property access, load_string, load_file, save_to_string, header mode, and indexed row mode.
• ResourceImporterCSV: editor-class availability when the running build exposes editor classes.

Troubleshooting

If ClassDB.class_exists("CSV") fails, rebuild Blazium with the dotcsv module enabled.

If ClassDB.instantiate("Autowork") fails, rebuild Blazium with the autowork module enabled.

If file-based tests fail, make sure the project is run from this directory so res:// resolves to the test project.

License

MIT License. See LICENSE.