# UnitTest classes inheriting from LitiumApplicationTestBase fail due to database connection timeout

**URL:** <https://forum.litium.com/t/unittest-classes-inheriting-from-litiumapplicationtestbase-fail-due-to-database-connection-timeout/405>\
**Category:** Questions\
**Tags:** litium-5\
**Created:** [December 5, 2018, 7:34am UTC](https://forum.litium.com/t/unittest-classes-inheriting-from-litiumapplicationtestbase-fail-due-to-database-connection-timeout/405 "2018-12-05T07:34:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![StephenM](https://avatars.discourse-cdn.com/v4/letter/s/4da419/32.png) [@StephenM](https://forum.litium.com/u/StephenM)\
**Post date:** [December 5, 2018, 7:34am UTC](https://forum.litium.com/t/unittest-classes-inheriting-from-litiumapplicationtestbase-fail-due-to-database-connection-timeout/405/1 "2018-12-05T07:34:34Z")

</div>

I guess this probably applies to all versions of Litium 5 and up.

I would like to avoid at all costs setting-up too much in my unittests, but at least in version 5 there are cases were I can’t get around a service resolving something from the global IoC. With all the necessary NuGet packages included I finally ended up with a database connection timeout. Which makes sense, because I don’t want to connect to a database in my UnitTest’s!

Is there any way to get around this?

Litium version: Litium 5

---

<div class="post-metadata">

**Author:** ![patric.forsgard](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.litium.com/patric.forsgard/32/10_2.png) [@patric.forsgard](https://forum.litium.com/u/patric.forsgard)\
**Post date:** [December 5, 2018, 9:19am UTC](https://forum.litium.com/t/unittest-classes-inheriting-from-litiumapplicationtestbase-fail-due-to-database-connection-timeout/405/2 "2018-12-05T09:19:36Z")

</div>

It’s not possible to start the application without an database. To be able to answer if it exists a workaround that you can use we need to know what your test is dependent of and maybe the exception you was getting before adding Litium as an runnable application.
