# Testing Vision Templates directly in IDE - Template uses stale project Scripts?

**URL:** <https://forum.inductiveautomation.com/t/testing-vision-templates-directly-in-ide-template-uses-stale-project-scripts/47961>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [June 18, 2021, 5:23pm UTC](https://forum.inductiveautomation.com/t/testing-vision-templates-directly-in-ide-template-uses-stale-project-scripts/47961 "2021-06-18T17:23:59Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![WillMT10](https://avatars.discourse-cdn.com/v4/letter/w/7feea3/32.png) [@WillMT10](https://forum.inductiveautomation.com/u/WillMT10)\
**Post date:** [June 18, 2021, 6:51pm UTC](https://forum.inductiveautomation.com/t/testing-vision-templates-directly-in-ide-template-uses-stale-project-scripts/47961/6 "2021-06-18T18:51:50Z")

</div>

Are you importing your script or calling the full name?

> [@Import from global and project script library failing randomly](http://forum.inductiveautomation.com/t/import-from-global-and-project-script-library-failing-randomly/18822/2):
>
> Try not importing it at all. Just call shared.util.MWESLogging.getLog(). Due to object lifetimes in the gateway, it is unwise to ever import anything from shared.\* or project.\*. Just use the full names wherever you need them. It shouldn’t be a problem in the client either, but the designer also has weirdness. Import all you want from java. That is a pure jython operation and is effectively bulletproof. Other than the fact you can’t use wildcards. See this topic:

---

_[View the full topic](https://forum.inductiveautomation.com/t/testing-vision-templates-directly-in-ide-template-uses-stale-project-scripts/47961)._