# Editable Test Values in Dev Mode

**URL:** https://community.tulip.co/t/editable-test-values-in-dev-mode/8310
**Category:** Product Suggestions
**Created:** [May 11, 2023, 8:47pm UTC](https://community.tulip.co/t/editable-test-values-in-dev-mode/8310 "2023-05-11T20:47:53Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![John](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/john/32/4971_2.png) [@John](https://community.tulip.co/u/John)
#### Post date: [May 11, 2023, 8:47pm UTC](https://community.tulip.co/t/editable-test-values-in-dev-mode/8310/1 "2023-05-11T20:47:53Z")

</div>

Debugging across apps and tables in larger solutions in Dev mode can be tough if there are dependencies between applications. I would like to be able to enter “dummy” values into variables and tables records in Dev Mode in order to make debugging single steps easier.

The use-case here came up in office hours today. The user (@don.feeney) has one application that collects a value at the end of a long process. In another application, a different user needs to enter a similar value. If the second value is out of a specified range calculated from the first value, a quality event is triggered. In order to test this, the user has to go into tables manually to update several columns in a table, or commit to running the first application every time.

If they could just enter the values they want to test against, this could be solved.