Check this examples
https://www.outsystems.com/forge/component-overview/11274/bdd-framework-example-multiple-scenario
What I would do is create a traditional web app and do all the bdds there and reference any core action to test the logic that you are using to do all your backend processes behind, this way you will call the actions that you are using on the frontend to trigger your features.
It's not a good thing to do tests in the same module of the application.
Imagine:
- You have an application where you create a user by clicking on a button.
In the application that you created to do the bdds, you will need to call the server actions on the core modules that you used to do the create user. You will need to reference those actions and create a block to the different scenarios or the scenario. Where you have the setup, given, when, then teardown. You have all that information on the link you shared.