[Feature Request]: Add end-to-end integration tests using a test runner to validate core system workflows

[divyanshim27]

Summary

Celtrix does not appear to have a comprehensive integration test suite that validates core system workflows end-to-end. Unit tests (if present) are insufficient for a platform-level project where the interaction between components is as important as the individual components themselves. The absence of integration tests means regressions in cross-component behavior may go undetected until they reach users.

Problem

• There is no visible integration test directory or test runner configuration in the repository.
• Core workflows (initialization, command processing, plugin lifecycle, etc.) are not covered by automated tests that exercise the full system stack.
• Contributors making changes to core modules have no safety net to verify they have not broken downstream behavior.
• For a GSSoC project accepting many simultaneous PRs, the risk of integration regressions is elevated.

Impact

• Regressions in cross-component interactions can land in main undetected.
• Maintainers must manually verify system-level behavior during review, adding significant overhead.
• The project cannot reliably guarantee stability across releases without integration coverage.

Proposed Solution

1. Set up a test runner (Jest or Vitest, depending on the existing ecosystem) with a dedicated tests/integration/ directory.
2. Write integration tests for the following core workflows:
   • System initialization and shutdown (clean startup → ready state → graceful exit)
   • Core command/request processing (valid input → expected output, invalid input → error handling)
   • Error propagation (a failure in one module does not crash the entire system)
3. Add test scripts to package.json:

   "scripts": {
     "test:unit": "vitest run tests/unit",
     "test:integration": "vitest run tests/integration",
     "test": "vitest run"
   }

4. Wire integration tests into the CI pipeline (once CI is established) so they run on every PR.
5. Target 70% integration coverage on core workflow paths in the initial PR.

Additional Notes

• I will write mock/stub implementations for any external dependencies (filesystem, network) to keep tests hermetic and fast.
• I am happy to set up the full test infrastructure and write an initial meaningful test suite.
• Could you assign this to me?

Labels: enhancement, testing, infrastructure, help wanted, GSSoC 2026

[divyanshim27]

Hey @maintainers ,
Please assign it to me under GSSoC 2026.
/assign /claim /claim-assignment