Hello. I ran into an issue with JoobyTest a few days ago, where the test environment was not being loaded when running an integration test, causing application startup errors for missing configuration properties, which were defined in application.test.conf. This happens because the env property of Jooby is lazily loaded when getEnvironment() is called, and there is no call to this method when the Jooby constructor is called. Here is a sample app that reproduces the issue. The issue may be resolved by adding a call to getEnvironment() or getConfig() to the example app's initializer block. I will also open a PR to fix this issue.
Let me know if there is anything I can clarify or help with. Thanks in advance.
Hello. I ran into an issue with
JoobyTesta few days ago, where the test environment was not being loaded when running an integration test, causing application startup errors for missing configuration properties, which were defined inapplication.test.conf. This happens because theenvproperty ofJoobyis lazily loaded whengetEnvironment()is called, and there is no call to this method when theJoobyconstructor is called. Here is a sample app that reproduces the issue. The issue may be resolved by adding a call togetEnvironment()orgetConfig()to the example app's initializer block. I will also open a PR to fix this issue.Let me know if there is anything I can clarify or help with. Thanks in advance.