Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete test coverage of the DSL #88

Open
MateuszKowalewski opened this issue Jul 1, 2023 · 2 comments
Open

Complete test coverage of the DSL #88

MateuszKowalewski opened this issue Jul 1, 2023 · 2 comments
Labels
enhancement New feature or improvement of programmer experience

Comments

@MateuszKowalewski
Copy link
Contributor

It seems not the whole implementation of the DSL is currently under test, or used in the example projects.

This seems risky.

As the DSL isn't such large complete test coverage seems doable.

The concrete use examples don't need so much tests OTOH. They are kind of test on their own. But the DSL (and it's implementation) should be imho under automated tests completely.

@TomasMikula
Copy link
Owner

It seems not the whole implementation of the DSL is currently under test, or used in the example projects.

This seems risky.

As the DSL isn't such large complete test coverage seems doable.

Agreed.

The concrete use examples don't need so much tests OTOH. They are kind of test on their own. But the DSL (and it's implementation) should be imho under automated tests completely.

Isn't that like saying that your Akka app doesn't need tests because it is already kind of a test (of Akka) on its own 😄

Don't necessarily look at tests of the examples as tests of Libretto. They are just tests of the examples 😉

@TomasMikula TomasMikula added the enhancement New feature or improvement of programmer experience label Jul 2, 2023
@MateuszKowalewski
Copy link
Contributor Author

Isn't that like saying that your Akka app doesn't need tests because it is already kind of a test (of Akka) on its own 😄

Don't necessarily look at tests of the examples as tests of Libretto. They are just tests of the examples 😉

Sure!

That part was more about priorities.

I think the examples have very high value. That's more or less a kind of starting point when you want to build something yourself.

But that code doesn't need much testing. Example input needs to output expected output. That's all.

I didn't look in detail what the test do actually. It was really mostly about the prios. Having tests for examples but not for the core of the whole system seemed a little bit off regarding prios.

Of course it's not bad to have properly tested examples! But for end-user code the framework should be mostly safe to use. It shouldn't be possible (in obvious ways) to construct bad or nonsensical programs anyway. That's the whole point of really type-safe APIs and "making illegal states unrepresentable". The type-checker does "the testing" for you! At least that should be the goal, imho.

@TomasMikula TomasMikula changed the title Test coverage Complete test coverage of the DSL Jul 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or improvement of programmer experience
Projects
None yet
Development

No branches or pull requests

2 participants