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
This patch adds extension testing to our continuous integration, by adding a further check target in the
extensions directory. At some point the tests/Makefile will need tweaking to make sure that only
<extension>/tests/ directories are searched for suitable test handlers.
Also TestLoadExtension has been added to the test library to facilitate loading of extensions in the
TestSetup handler. At some point it might make sense for extension tests to automatically load themselves
but for now it seems fine to have them do it explicitly.
Note this does no dependency analysis, so it is currently not possible to test extensions that rely on modules
other than those built in to the engine.
Copy file name to clipboardExpand all lines: docs/testing.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,7 @@ Before running each test command, the test framework inserts a test library stac
48
48
*`TestAssertBroken pDescription, pExpectTrue, pReasonBroken`: The same as `TestAssert`, but marking the test as "expected to fail". *pReasonBroken* should be a short explanation of why the test is currently expected to fail; it should almost always be a reference to a bug report, e.g. "bug 54321".
49
49
*`TestGetEngineRepositoryPath`: A function that returns the path to the main LiveCode engine repository.
50
50
*`TestGetIDERepositoryPath`: A function that returns the path to the LiveCode IDE repository.
51
+
*`TestLoadExtension pName`: Attempt to load the extension with name `pName`, eg `TestLoadExtension "json"` will load the JSON library extension.
51
52
52
53
Tests can have additional setup requirements before running, for example loading custom libraries. If the script test contains a handler called `TestSetup`, this will be run prior to running each test command. For example:
0 commit comments