# Process debugger expression resolver++

**URL:** <https://forum.flowable.org/t/process-debugger-expression-resolver/623>\
**Category:** Uncategorized\
**Created:** [June 7, 2017, 7:22am UTC](https://forum.flowable.org/t/process-debugger-expression-resolver/623 "2017-06-07T07:22:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin.grofcik](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/martin.grofcik/32/71_2.png) [@martin.grofcik](https://forum.flowable.org/u/martin.grofcik)\
**Post date:** [June 7, 2017, 7:22am UTC](https://forum.flowable.org/t/process-debugger-expression-resolver/623/1 "2017-06-07T07:22:37Z")

</div>

I added new blog post about process debugger expressions/scripts resolver and the possibility to integrate runtime scripts evaluation into process testing and modeling.

> **[Process debugger expression resolver++](https://gromar01.wordpress.com/2017/06/07/process-debugger-expression-resolver/)**
>
> The natural and until now missing part of the process debugger was expression resolver. Let’s start a simple one task process with the init form: When the process instance is started with var…

Any feedback is welcome.  
Martin

---

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [June 9, 2017, 8:40am UTC](https://forum.flowable.org/t/process-debugger-expression-resolver/623/2 "2017-06-09T08:40:28Z")

</div>

I like the idea a lot. Nice work on the UI side of things.  
Imho, a cool thing would be to have a tool (or API?) that generates a unit test (given a certain process instance id), based on the same logic you have now. Not sure if it should be saved as a sequence of method calls there, or a process definition, like you have now.