The BDD Testing Framework provides a set of tools for easily creating BDD / TDD style tests for your OutSystems Applications.

The main focus is testing the logic of your modules, by exercising the critical actions that support your app's use cases.

You can check the introductory article that covers the basics of how to use the framework, as well as other articles for using the REST API and creating data-driven tests. 

You can also check this demo video where we show how to use the framework to create a test for a piece of logic of the eCommerce app.

Main highlights of the component:

• Create test scenarios and steps that are conformant to the principles of Behavior Driven Development.
• Enable Test Driven Development - you can define scenarios and steps early in the app design stage and write the test code when the features have been implemented.
• Easily add scenarios and steps by dragging and dropping web blocks (Scenario + Given / When / Then clauses).
• Each step is implemented in its own action, making sure that steps are sequential and occur in the same request.
• Enhance Test Maintenance - test outputs are identical to what is designed in Service Studio, making it easy to pinpoint step failures and evaluate the code behind them.
• Supports multiple tests in the same page and evaluating final stats (number of successful / failed tests).
• Includes dedicated Setup/Teardown steps for more complex test scenarios.
• REST API for running tests and obtaining results, so that you can more easily integrate with your own tools.
• Application and Screen Templates for fast setup of tests.

In an effort to improve customer service, we provide you with the following list of some known limitations with the BDDFramework. This is not a complete list of all existing limitations but is intended to help guide the determination of BDDFramework’s suitability to serve a particular purpose. 

• The BDDFramework is not supported in Production environments, nor should it be published and consumed by other OutSystems Applications in such environments.

• The BDDFramework is only supported in OutSystems 11 onward. 

• Server Actions being tested by a test that uses the BDDFramework need to be set to Public.

• Testing client-side actions of Reactive Web applications or Mobile applications is not supported.

• Testing Screen Actions and Preparation Actions of Traditional Web applications is not supported. Please check here how you can use the framework to test server-side actions of OutSystems applications.

• Creating tests using a Reactive Web or Mobile module is not supported.

• Tests built with the BDDFramework that include actions that perform an AbortTransaction explicitly or implicitly (for example: through an ExceptionHandler with AbortTransaction set to “Yes”) are not supported. This also includes tests that call actions in the application being tested which perform an AbortTransaction. The AbortTransaction operation impacts the internal status of the BDDFramework, making the test results unpredictable.

• The BDDFramework does not support tests being run in parallel over the same OutSystems environment. Running tests in parallel will make the test results unpredictable.