Testing self made library activities before publishing and with the debug option without having the test-cases and test-data in the Library project?

For testing self made library activities I used in “Windows Legacy” projects a separate test-project, so I wouldn’t have to publish all my test-cases and test-data. Within this Test project I used “Invoke workflow” with the path of the workflow.
Within “Windows” and “Modern” projects this seems not to be possible anymore.

You can invoke the workflow, but if this invoked workflow has invoked workflows itself, the path is not recognized anymore.

e.g. I have a library for getting specific data using API calls. My library activaty for ‘Get specific item’ has invoked a private workflow ‘Get token’.

What might be the best option for testing these library activities before publishing and with the debug option without having the test-cases and test-data in the Library project?

@Maarten_Oderkerk

Welcome to the community

you can use invoke process I guess

cheers

It’s best to publish them as an alpha version and then install them in your test project. Otherwise it’s not a real test.