Testing
- Q155: How do I write a unit test in EK9?
- Q156: How do I assert conditions in a test in EK9?
- Q157: How do I run tests and see results in EK9?
- Q204: How do I write black-box tests with expected output files in EK9?
- Q205: How do I write parameterized tests in EK9?
- Q206: How do I measure test coverage in EK9?
- Q207: What test output formats does EK9 support for CI/CD?
- Q208: How do I test output containing dynamic values like dates, GUIDs, or timestamps?
- Q209: How do I test that code throws or does not throw exceptions in EK9?
- Q804: Why does EK9 have a built-in test framework instead of using JUnit or pytest?
- Q805: How do I organise tests relative to production code in EK9?
- Q806: How do I group tests and control execution order in EK9?
- Q807: How do I run specific tests or list available tests in EK9?
- Q808: How do I mock dependencies in EK9 tests without Mockito?
- Q809: How does EK9 enforce test quality at compile time?
- Q810: How do I test output containing dynamic values like dates or GUIDs in EK9?
- Q811: How do coverage thresholds and exit codes work in EK9?
- Q953: How do @Test programs work with command-line arguments, timeouts, and expected output?