Add unit testing guidelines to Contribute.md

[Copilot]

The Contribute.md documentation lacked practical guidance on how to add unit tests when contributing to AL-Go, despite the repository having comprehensive unit test infrastructure.

Changes

• Added "Testing your contributions" overview explaining when to add unit tests
• Enhanced "Unit tests" section with:
  • Step-by-step instructions for creating Pester test files
  • Example test structure following Arrange-Act-Assert pattern
  • Best practices (mocking, InModuleScope, cleanup)
  • Commands to run tests locally (pwsh -File Tests/runtests.ps1 -Path Tests)

Example

Import-Module (Join-Path $PSScriptRoot '../Actions/.Modules/MyModule.psm1') -Force

Describe "MyFeature tests" {
    It 'Should do something specific' {
        # Arrange
        Mock Write-Host { }
        
        # Act
        $result = MyFunction -Parameter "value"
        
        # Assert
        $result | Should -Be "expected"
    }
}

Original prompt

I want you to look through the Contribute.md and make add some notes on how you can add tests when you're contributing to AL-Go

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[aholstrup1]

@copilot Remove the E2E things for now. To begin with I just want unit tests described

[Copilot]

@copilot Remove the E2E things for now. To begin with I just want unit tests described

Removed all E2E testing documentation. The Contribute.md now focuses exclusively on unit test guidelines. (87fa8eb)