Skip to main content

Creating mock data sets is the single most time consuming task when creating unit tests. Often data already exists in the project database which, after some careful adjusting, is suitable for unit tests. I would like to easily import this data into a mock data set to speed up creating unit tests.

Hi @J. de Lange,

Perhaps this enrichment can be of help?: 

2024.1 Enrichment

(2024.1 | Thinkwise Documentation (thinkwisesoftware.com))


Hi @J. de Lange,

Perhaps this enrichment can be of help?: 

2024.1 Enrichment

(2024.1 | Thinkwise Documentation (thinkwisesoftware.com))

Looks promising! I’ll try it, thank you.


NewNeeds feedback

I do feel the Enrichment could be made available with a Task in the Mock data screen for example. So if that is what you would like, then we change the idea to that 😄


Adding the task at the mock data screen would really help, but also being able to set a where clause would be very helpful, in that case it could retrieve the data from the table / view (columns for which the checkbox is checked) and then with a certain where clause to only get a couple of records into the mock data. (Maybe the where clause could listen to the filled in data in a mock data set, and then the task would overwrite and add new data?)

In most cases during development testing you already have the data correctly in your own database, but also the other irrelevant records. 


...being able to set a where clause would be very helpful…

Agreed!


I do feel the Enrichment could be made available with a Task in the Mock data screen for example. So if that is what you would like, then we change the idea to that 😄

I think this is a great idea. The enrichment already definitely helps but this would be a lot more convenient and it makes it easier to get the entire team using this.
 

As Robbert mentioned, a where clause is definitely a must for us. The database contains way more data then I would ever like to have in a mock set.


Needs feedbackOpen

FYI: Added this Idea to the 

 


OpenPlanned

This is planned to be resolved with the Roadmap 2025 H1 efforts.