# Development workflow//testing

**URL:** <https://community.holistics.io/t/development-workflow-testing/660>\
**Category:** Feature Suggestions\
**Created:** [January 11, 2022, 6:12pm UTC](https://community.holistics.io/t/development-workflow-testing/660 "2022-01-11T18:12:06Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![Khai\_To](https://community.holistics.io/user_avatar/community.holistics.io/khai_to/32/128_2.png) [@Khai\_To](https://community.holistics.io/u/Khai_To)\
**Post date:** [June 18, 2022, 4:21pm UTC](https://community.holistics.io/t/development-workflow-testing/660/15 "2022-06-18T16:21:39Z")

</div>

Hi @Alex_H, @DataGeekDude, @Abdel,  
Thank you so much for all the use cases and suggestions. I would love to discuss the complete workflow with you guys. I will try to setup a call with you soon to further understand it.

This could be something that we’re planning to do is [dynamic modeling](https://community2.holistics.io/t/query-parameters-for-dynamic-dimensions-measures-and-more/686). Dynamic modeling in combination with Preview Reporting would definitely help you guys.

* * *

For the comment from @Abdel

> [@Abdel](#):
>
> the preview mode is very manual, so testing needs to be manually. If you have 20 reports depending, you cannot go through them all manually.

Could you specify what do you mean by testing? Do you want to test:

- if there are broken reports
- or test how will the data of the reports be altered due to modeling changes?

---

_[View the full topic](https://community.holistics.io/t/development-workflow-testing/660)._
