Testing strategies about kalix-jvm-sdk

[octonato]

That's fine. It's good to try it locally first since interacting with CI is mostly a slow process.

Ultimately, whatever strategy we pick, we want it running on CI and that for each PR.

[franciscolopezsancho]

I'll start creating a script that

• clones the java-sdk
• install the archetypes on local
• generate a new project from that local archetype
• run both tests (unit and it)
• and copy the relevant files from samples (maybe one by one starting with the Impl) while running the tests.

[octonato]

You mean one script that does that all?

This is better done by the CI using its scripting facilities. At the end, it's the same, but there are a few other things already in place.

[franciscolopezsancho]

I don't know how many of all the cases we are going to tackle with this but I thought it could be a useful first iteration. I totally agree that done in CI is the way to go. What I thought is first testing all this in local to have it fleshed out and later if we find it useful, yeah, moving it to CI. Makes sense or you would rather start developing it in CI?

[franciscolopezsancho]

I created #57 to start with, @octonato
I think I need to do a couple of tests before I copy all the files (it, unit tests and CounterImpl) but this is close to what we were discussing, I think.

[franciscolopezsancho]

In the Makefile we have run-test-impl that tests if sample and codegen are in sync. In order for this to work the codegen should not create test asserting for failure. I uploaded the file trinity/src/test/com/example/domain/CounterTest.java which has an implementation that passes as long as the CounterImpl contains the required methods. If the codegen would create such a file CounterTest we then could run-test-impl and test the sample is in sync with the codegen. LMKWYT

[franciscolopezsancho]

I removed the mocking creation from the codegen. This is how it would look the PR https://github.com/franciscolopezsancho/akkaserverless-codegen/pull/1

[franciscolopezsancho]

I added to that PR:

• generation of Tests and [Counter]Impl such is not mocking anything and mvn verify pass in a clean project
• generation of Main. It was broken by missing SERVICE variable. mvn verify -Pit pass in a clean project

I think that's ready to merge @octonato

[johanandren]

For the record: Inclusion of code-gen now has brought integration tests in the form of using the current state of codegen and maven plugin with the sample projects which then run integration tests against a dev mode proxy as part of PR validation etc.

[patriknw]

I guess this has been done.