Development and Testing

Development, Testing, and Contribution

Build, test, benchmark, and document AuroraScript changes consistently.

Applies to 4.0.0.

Home · Performance and Benchmarks

On this page

• Local Build
• Testing
• Documentation and Schema
• Pre-commit Checks
• Next steps

Local Build

The main library, tests, and language tools are .NET projects. Restore dependencies first, then build the project you need.

dotnet build src/AuroraScript.csproj -c Release
dotnet build language-tools/AuroraScript.Mcp/AuroraScript.Mcp.csproj -c Release
dotnet build language-tools/AuroraScript.VisualStudio/AuroraScript.VisualStudio.csproj -c Release

Testing

The functional test project targets net8.0, net9.0, and net10.0. Install the corresponding runtimes locally before running each target.

dotnet test tests/AuroraScript.Tests/AuroraScript.Tests.csproj -c Release

When adding or changing language semantics, cover the normal path, diagnostics, cross-module behavior, and observable boundary conditions. Do not encode timing assertions in functional tests; detect performance regressions through benchmarks.

Documentation and Schema

documents/ is the packaged language material for tooling and MCP. When changing a public API or language feature, update the corresponding schema, examples, and Wiki together; avoid updating only a README or only code.

Pre-commit Checks

• Build and test every affected project.
• Run the relevant benchmark, or at least --smoke, when changing a hot path.
• Check that Wiki links, versions, and API pages are synchronized.
• Do not commit bin/, obj/, local publish folders, or machine-specific configuration.

Next steps

• Performance and Benchmarks for benchmark commands and baselines.
• Tooling for language-tool integration.