[Testing]

[anxielray]

• I suggest that all functions be implemented and tested in the Kisumu Language itself to ensure consistency, validate its core capabilities, and identify any limitations early. This approach strengthens the language’s foundation and proves its practicality.
• Another language could be used to do counter-testing, but the main tests should be carried out by the static langauge itself

[kh3rld]

We appreciate this thoughtful suggestion about self-hosting tests. Here's our adapted implementation plan:

Hybrid Testing Approach

1. Core Language Tests (Current Phase)

   // internal/parser/parser_test.go
   func TestIntegerExpressions(t *testing.T) {
       tests := []struct {
           input    string // Kisumu Lang code
           expected int64
       }{
           {"5 + 5", 10},
           {"2 * (3 + 4)", 14},
       }
       
       for _, tt := range tests {
           l := lexer.New(tt.input)
           p := New(l)
           result := p.ParseExpression()
           testIntegerObject(t, result, tt.expected)
       }
   }

2. Self-Testing (Phase 2 - Post v0.8)

   # tests/lang/arithmetic.ksm
   test "Addition" {
       assert(2 + 2 == 4, "Basic addition failed")
       assert(1 + -1 == 0, "Negative addition failed")
   }
   

Implementation Roadmap

Phase	Testing Method	Tools	Coverage Goal
1 (Now)	Go-based unit tests	go test	80% core packages
2 (v0.8)	Kisumu test runner	Custom .ksm tests	50% stdlib
3 (v1.0)	Property-based tests	RapidCheck-like	Critical paths

Why This Staged Approach?

1. Current Limitations:

   • The language lacks control structures needed for test assertions
   • No error handling mechanism yet for test failures

2. Progressive Validation:

   graph LR
   A[Lexer/Parser Go Tests] --> B[Interpreter Go Tests]
   B --> C[Kisumu Integration Tests]
   C --> D[Self-Hosted Test Framework]
   

   Loading

3. Immediate Actions:

   • Create tests/ directory with:

     tests/
     ├── unit/       # Go-based tests
     ├── lang/       # Future .ksm tests
     └── fixtures/   # Test case files
     

   • Add test runner prototype in cmd/test (Go-based)