Here are some great questions from Alex Ruinen about the K Test Manager on ODC and the answers. Thanks Alex!

Hi Alex,

Thank you so much for the questions. This will help me improve the help. And to be honest I just moved the help over to ODC and haven't updated it.

• In which application/library do I have to write the tests? (K test manager/k test core/my own application)

Write your tests in your own application. Either expose the test API from the application containing the code, or expose service actions for logic you want to test to a separate application that implements the unit tests. If you expose the test API from a separate application then your main application does not need to depend on K Test Core when it deploys to production.

If you did write your tests in K Test Manager or K Test Core, then they would be overwritten when you upgrade to the next version, so thats not an option.

• Do you mean to make a service action out of it? Or is it old documentation?

Yes, unfortunately internal only is not yet available in ODC, so ignore that. Although in that case it would be best to use Bearer authentication for the tests. Now that events are available I am considering adding the possibility of subscribing to an event for the start of a test and publishing the results. But I will leave the existing API in places if I do that.

• Does this mean that the "k test core" needs to be deployed to production as well? 

Yes, if you built the unit tests in the main application and not in a separate test application.

• Is it old documentation that still needs some rework? Or is the framework still not up-to-date for ODC?

Yes, its the documentation that hasn't been updated. The main point of the documentation is correct though. The framework is working on ODC. I am using it to test a suite of applications and components in ODC.

Kind regards,

Stuart