jUnit throws exception
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
legacy-article
learn-legacy-article-disclaimer-text
Resolution
- Liferay relies on a fully initialized OSGi container for its services. The test code is invoking a static Liferay utility class that relies on an OSGi service tracker during runtime. This tracker locates and uses the specific OSGi service implementation. Since the setup doesn't involve initializing the OSGi container, invoking an out-of-the-box Liferay class (e.g., Validator.isNotNull()) will likely fail.
- Unfortunately, we don't offer specific examples of JUnit test setups that build a complete OSGi container for testing purposes. The best recommendation for the situation is to consider mocking all the Liferay classes and methods your custom code interacts with during the test. This allows you to isolate and test your code without requiring a full Liferay OSGi container.
did-this-article-resolve-your-issue