Kaapi v1.0: Enhancing the whole test suite

Describe the bug -
Our test suite has critical infrastructure issues that reduce reliability and maintainability:

Test cases are tightly coupled to a global seed.json file for initial data setup
Critical paths lack adequate test coverage
Multiple flaky or skipped tests exist in the codebase
Test execution time has significantly increased

Expected behavior -

Tests should be isolated and self-contained, managing their own test data
Each test suite should use fixtures or factories independent of global seed data
Changes to production seed data (seed.json) should not affect test stability
Critical code paths should have comprehensive test coverage
All tests should be deterministic and pass consistently
No skipped or flaky tests should exist without documented reasons
test suite not taking long to finish its execution

Navigation Menu