How does testing fit into Lithia?

[vknabel]

I‘d really like to have a testing concept which really fits into Lithia.
I really like this about Go. And the fact that test files can be placed beside the actual sources.

As the output format, I‘d like to implement a standard like TAP. But there is also a JSON-format propose, which sounds reasonable and might be an alternative.

Some questions that come to mind:

• What should tests look like?
• As in Go by defining functions?
• Or with describe-it blocks?
• Should there be functions to add cases to write your own BDD framework?
• Expectations or simpler test functions?
• Property based testing?
• Overriding modules in unit tests? (Is this a package manager topic?)

[vknabel]

Idea: what about tests in source files?

[vknabel]

This will actually my preferred way for testing. Creating many small files, all including tests.

Possible as there are no methods. Therefore we need to reduce the testing overhead as much as possible.

Tests should be required to pass for building.

[vknabel]

One open question:
How to restrict the test being run just to one single module instead of all dependencies?

Though, a conclusion isn't urgent. For now, just run all tests.