Add taskfile for building and running tests

[dmcgowan]

Taskfile is better for cross platform building and provides a cleaner interface for defining build functionality.

This cleans up the integration test runners

For example

task test:integration -- -v -run TestStream

[Copilot]

Pull request overview

This PR introduces a Taskfile.yml to provide a cross-platform task runner interface for building artifacts and running tests, and refactors the integration test runners to support per-test execution with forwarded flags (including a Windows PowerShell runner).

Changes:

• Add Taskfile.yml with build/test/lint/proto/clean tasks, including integration test support via gotestsum.
• Update integration/test.sh to discover tests dynamically and forward selected flags.
• Add integration/test.ps1 for running integration tests on Windows; ignore Task’s .task/ state directory.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 6 comments.

File	Description
Taskfile.yml	Adds task-based build/test/lint/proto workflows intended to replace/augment Make targets
integration/test.sh	Switches integration runner to dynamic test discovery + flag parsing, runs tests one-by-one
integration/test.ps1	New Windows integration runner with per-test process execution and flag parsing
.gitignore	Ignores .task/ directory created by Task

Comments suppressed due to low confidence (4)

integration/test.sh:33

• If test discovery fails or produces zero tests, the script currently exits successfully (loop runs zero times) and also may terminate early because grep returns exit code 1 when there are no matches. It would be safer to handle the -test.list pipeline explicitly (|| true) and then fail with a clear message when tests is empty.

# Discover tests from the binary (respects build tags).
readarray -t tests < <(../_output/integration.test -test.list '.*' 2>/dev/null | grep '^Test')

integration/test.sh:60

• The -run filtering uses Bash regex matching ([[ ... =~ ... ]]), which doesn’t match Go’s -run/-test.list regexp semantics (RE2). To keep behavior consistent with go test -run, consider passing the pattern to integration.test -test.list <pattern> and using that output as the filtered test list instead of re-implementing matching in Bash.

if [ -n "$run_pattern" ]; then
    filtered=()
    for test in "${tests[@]}"; do
        [[ "$test" =~ $run_pattern ]] && filtered+=("$test")
    done
    tests=("${filtered[@]}")

integration/test.ps1:29

• When the test binary can’t be executed or -test.list returns nothing, $tests becomes empty and the script will currently report success (no loop iterations). Consider treating an empty test list as an error with a helpful message so CI/local runs don’t silently skip integration tests.

# Discover tests from the binary (respects build tags).
# Pass flags as an array to prevent PowerShell splitting on dots.
$tests = & $testBin @('-test.list', '.*') 2>$null | Where-Object { $_ -match '^Test' }

integration/test.ps1:52

• The -run filtering uses PowerShell/.NET regex via -match, which can differ from Go’s -run regexp semantics (RE2). For consistency with go test -run, consider discovering tests with -test.list <pattern> (using the provided pattern) instead of filtering the full list with a different regex engine.

# Parse TESTFLAGS forwarded from the task invocation.
#   -run <pattern>  filters which discovered tests to run (not passed to binary)
#   -v              changes gotestsum output format (handled in Taskfile; skip here)
#   anything else   is normalised to -test.<flag> and forwarded to the binary
$runPattern = $null
$binaryFlags = @()
if ($env:TESTFLAGS) {
    $tokens = ($env:TESTFLAGS -split '\s+') | Where-Object { $_ }
    for ($i = 0; $i -lt $tokens.Count; $i++) {
        switch -Regex ($tokens[$i]) {
            '^-run$'     { $runPattern = $tokens[++$i]; break }
            '^-run=(.+)' { $runPattern = $Matches[1];  break }
            '^-v$'       { break } # handled by gotestsum format in Taskfile
            '^-test\.'   { $binaryFlags += $tokens[$i]; break }
            '^-(.+)'     { $binaryFlags += "-test.$($Matches[1])"; break }
        }
    }
}
if ($runPattern) { $tests = $tests | Where-Object { $_ -match $runPattern } }

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 8 out of 9 changed files in this pull request and generated 9 comments.

Comments suppressed due to low confidence (4)

.github/workflows/ci.yml:68

• GitHub Actions best practice is to pin third-party actions to a full commit SHA for supply-chain safety. arduino/setup-task@v2 is referenced by tag here; consider pinning it to a specific commit SHA.

      - uses: arduino/setup-task@v2
        with:
          version: 3.x
          repo-token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/ci.yml:103

• GitHub Actions best practice is to pin third-party actions to a full commit SHA for supply-chain safety. arduino/setup-task@v2 is referenced by tag here; consider pinning it to a specific commit SHA.

      - uses: arduino/setup-task@v2
        with:
          version: 3.x
          repo-token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/ci.yml:144

• GitHub Actions best practice is to pin third-party actions to a full commit SHA for supply-chain safety. arduino/setup-task@v2 is referenced by tag here; consider pinning it to a specific commit SHA.

      - uses: arduino/setup-task@v2
        with:
          version: 3.x
          repo-token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/ci.yml:283

• GitHub Actions best practice is to pin third-party actions to a full commit SHA for supply-chain safety. arduino/setup-task@v2 is referenced by tag here; consider pinning it to a specific commit SHA.

      - uses: arduino/setup-task@v2
        with:
          version: 3.x
          repo-token: ${{ secrets.GITHUB_TOKEN }}