You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dialogic uses Unit Tests to ensure specific parts function as expected. These tests run on every git push and pull request. The framework to do these tests is called gdUnit4 and our tests reside in the /Tests/Unit path. We recommend installing the gdUnit4 add-on from the AssetLib, with this add-on, you can run tests locally.
To get started, take a look at the existing files in the path and read the documentation to create your first test.
Interacting with the Source Code
All methods and variables in the Dialogic 2 source code prefixed with an underscore (_) are considered private, for instance: _remove_character().
While you can use them, they may change in their behavior or change their signature, causing breakage in your code while moving between versions.
Most private methods are used inside public ones; if you need help, check the documentation.
Public methods and variables can be found in our Class Reference.
During the Alpha and Beta version stages, code may change at any Dialogic Release to allow drafting a better design.
Changelogs will accommodate for these changes and inform you on how to update your code.