Run Scripts with Custom Settings
Gint scripts are Gradle scripts, so support all the normal Gradle command line parameters. Gint supports a variety of ways additional ways to control the behavior of running scripts primarily related to properties and Gint control parameters and methods.
- Set using standard Gradle methods like user level Gradle properties.
- Specified as a command parameter. Example: -Dverbose=true.
- Set in user specific /wiki/spaces/GINT2/pages/116555873 file in user home directory.
- Set in /wiki/spaces/GINT2/pages/116555873 in the current directory of the run.
- Set in /wiki/spaces/GINT2/pages/116555873 in the project's target directory.
- Set in /wiki/spaces/GINT2/pages/116555873 in the project's resource directory.
- Set in a /wiki/spaces/GINT2/pages/111935618. However, normally profiles should only be used for test specific properties and data.
- Set dynamically in the test script using methods (see Functions column). There may be some timing restrictions on whether the function call will have affect.
- Before initialize - must proceed gint.initialize is test script
- Before run - must be in the test script and has no affect after testcases start running
- Blank - the function can change the setting anytime including dynamically during the test run. This means it can be used in a testcase resultClosure, successClosure, finalClosure, or inline code.
© 2005 -2024 gint.org