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
{{ message }}
This repository was archived by the owner on Aug 31, 2021. It is now read-only.
The testing.md file which explains the process for writing tests
for the various aspects of LiveCode contains a section on the
TestSkipIf command, which skips a test if a certain requirment
is met. However not all the available requirement options that
TestSkipIf provides were documented.
Information for these requirement options has now been added.
Copy file name to clipboardExpand all lines: docs/development/testing.md
+19-4Lines changed: 19 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,18 +61,33 @@ Before running each test command, the test framework inserts a test library stac
61
61
*`TestAssert pDescription, pExpectTrue`: Make a test assertion. The test is recorded as a failure if *pExpectTrue* is false. *pDescription* should be a short string that describes the test (e.g. "clipboard is clear").
62
62
*`TestSkip pDescription, pReasonSkipped`: Record a test as having been skipped. *pReasonSkipped* should be a short explanation of why the test was skipped (e.g. "not supported on Windows").
63
63
*`TestSkipIf pRequirement, pOptions`: Skip a test if the requirements
64
-
are met. `pOptions` varies depending on the `pRequirement` enum. The
65
-
following requirements are implemented:
66
-
-`ide` - the IDE repo is available. No options.
64
+
are met. `pOptions` varies depending on the `pRequirement` enum (if no
65
+
options are explicitly specified then no options are available for that
66
+
particular `pRequirement`. The following requirements are implemented:
67
+
-`ide` - the IDE repo is available
67
68
-`lcb` - LCB compilation supported
68
-
-`docs` - the docs are available. No options.
69
+
-`docs` - the docs are available
70
+
-`standalone` - the test is running in the standalone test runner
69
71
-`securityPermissions` - Option `set` to skip if a test should not
70
72
set the `securityPermissions`
71
73
-`platform` - options are comma delimited platform strings
72
74
-`processor` - options are comma delimited processor strings
73
75
-`stack` - options are comma delimited stack names to test if they
74
76
are available
75
77
-`environment` - options are comma delimited environment strings
78
+
-`clipboard` - access to the clipboard is available
79
+
-`wait` - the `wait` command is available and works as expected
80
+
-`security` - the security module is available
81
+
-`write` - write access to the filesystem is available
82
+
-`ui` - the test is running in a graphical environment (as opposed
83
+
to the command line)
84
+
-`desktop` - the test is running on a desktop computer
85
+
-`mobile` - the test is running on a mobile device
86
+
-`external` - an external module can be loaded/used. Options are a
87
+
comma delimited list of external module names
88
+
-`database` - an database module can be loaded/used. Options are a
89
+
comma delimited list of external module names
90
+
-`jvm` - the Java Virtual Machine is available
76
91
*`TestSkipIfNot pRequirement, pOptions`: Skip a test if the
77
92
requirements are not met. Requirements and options are the same as for
0 commit comments