A pure SourcePawn implementation of basic testing and assertions.
- SourceMod 1.10 or later (may still work for 1.8-1.9 but compatibility is no longer guaranteed as of v2.0.0)
If you use git while developing plugins, it is recommended to install this library as a git submodule. This makes it easy to lock to a specific major version or update as desired.
-
Run
git submodule add https://github.com/clugg/sm-testsuite dependencies/sm-testsuitein your repository. -
To lock to a specific branch, run
git submodule set-branch -b YOUR_BRANCH dependencies/sm-testsuite(e.g.git submodule set-branch -b v1.x dependencies/sm-testsuite). To undo this/reset to the default branch, rungit submodule set-branch -d dependencies/sm-testsuite. In both cases an update needs to be run afterwards (see step 4). -
Whenever building plugins with
spcomp, reference the library's include path using-idependencies/sm-testsuite/addons/sourcemod/scripting(this path may differ depending on which directoryspcompis run from). -
To pull the latest from your selected branch, run
git submodule update --remote dependencies/sm-testsuite.
To uninstall the library, run git rm dependencies/sm-testsuite.
Download the source code for the latest release and move all files and directories from the addons/sourcemod/scripting/include directory to your existing addons/sourcemod/scripting/include directory.
A comprehensive API reference is available here.
First, you need to include the library:
#include <testsuite>A section begins with the name of the section and ends by outputting the summary result of all tests executed within that section. If you are using SourceMod 1.10 or later, your tests will automatically be profiled and the time it took to execute the tests will be outputted after the test results.
Test_StartSection("section name");
// your tests here
Test_EndSection();A test begins with the name of the test and ends by outputting the summary result of all assertions within that test. All test methods must conform to the Test_Method typedef, which is simply a function which takes no parameters and returns nothing (void). You can run a test with a custom name, or let SourceMod resolve the test based on the name. Note: when using name-based resolving, if you don't call the method anywhere else, you will get an unused symbol warning.
void it_should_do_something()
{
// your assertions here
}
Test_Run("it_should_do_something", it_should_do_something);
// or
Test_RunFromString("it_should_do_something");An assertion is a statement that something should be a certain way. There are multiple types of assertions. Every assertion method accepts a name as the first parameter to make your test output more human readable. Every assertion you make will count towards the total assertions made in an individual test, and a single failed assertion means the entire test is considered failed. When an assertion fails, the value of the variable being asserted against will be outputted as information. Note: when an assertion fails, the function will continue executing unless you explicitly stop it.
Test_Assert("statement", true);
Test_AssertTrue("value", true);
Test_AssertFalse("value", false);
Test_AssertNull("value", null);
Test_AssertNotNull("value", view_as<Handle>(1));
Test_AssertEqual("matching int", 1, 1);
Test_AssertNotEqual("non-matching int", 1, 2);
Test_AssertFloatsEqual("float", 0.1, 0.1);
Test_AssertFloatsNotEqual("float", 0.1, 0.2);
Test_AssertStringsEqual("string", "hello", "hello");
Test_AssertStringsNotEqual("string", "hello", "world");Test_AssertFloatsEqual accepts an optional fourth parameter to set the threshold under which floats are considered equal. This is used to combat floating point errors and has been set to a sensible default.
Each section's tests and results are outputted within a box shape. The box has a default width of 64, but you can change it per-section if you'd like your the box to better fit your test output.
Test_SetBoxWidth(32);You might want to output some information not directly related to an assertion. However, if you simply use PrintToServer, the information will not align correctly with the rest of the test output. A special function is provided for this, which uses VFormat internally, meaning you can treat it in a similar way to Format.
Test_Output("here is some information: %d", 1);#include <testsuite>
void it_has_no_asserts()
{
Test_Output("I have no strong feelings one way or the other.");
}
void it_should_pass_all()
{
Test_Assert("statement", true);
Test_AssertTrue("value", true);
Test_AssertFalse("value", false);
Test_AssertNull("value", null);
Test_AssertNotNull("value", view_as<Handle>(1));
Test_AssertEqual("value", 1, 1);
Test_AssertNotEqual("value", 1, 2);
Test_AssertFloatsEqual("value", 0.1, 0.1);
Test_AssertFloatsNotEqual("value", 0.1, 0.2);
Test_AssertStringsEqual("value", "hello", "hello");
Test_AssertStringsNotEqual("value", "hello", "world");
Test_Output("here is some information: %d", 1);
}
void it_should_fail_all()
{
Test_Assert("statement", false);
Test_AssertTrue("value", false);
Test_AssertFalse("value", true);
Test_AssertNull("value", view_as<Handle>(1));
Test_AssertNotNull("value", null);
Test_AssertEqual("value", 1, 2);
Test_AssertNotEqual("value", 1, 1);
Test_AssertFloatsEqual("value", 0.1, 0.2);
Test_AssertFloatsNotEqual("value", 0.1, 0.1);
Test_AssertStringsEqual("value", "hello", "world");
Test_AssertStringsNotEqual("value", "hello", "hello");
Test_Output("here is some information: %d", 1);
}
void it_should_fail_some()
{
Test_AssertTrue("value", true);
Test_AssertFalse("value", true);
}
public void OnPluginStart()
{
Test_SetBoxWidth(56);
Test_StartSection("passing section");
Test_Run("it_has_no_asserts", it_has_no_asserts);
Test_Run("it_should_pass_all", it_should_pass_all);
Test_EndSection();
Test_SetBoxWidth(36);
Test_StartSection("failing section");
Test_Run("it_should_fail_all", it_should_fail_all);
Test_EndSection();
Test_StartSection("both section");
Test_Run("it_should_pass_all", it_should_pass_all);
Test_Run("it_should_fail_all", it_should_fail_all);
Test_Run("it_should_fail_some", it_should_fail_some);
Test_EndSection();
Test_SetBoxWidth(20);
Test_StartSection("empty section");
Test_EndSection();
}This plugin will produce the following output:
|------------------------------------------------------|
| passing section |
|------------------------------------------------------|
| |
| it_has_no_asserts |
| i I have no strong feelings one way or the other. |
| ✓ PASS |
| |
|------------------------------------------------------|
| |
| it_should_pass_all |
| ✓ statement |
| ✓ value == true |
| ✓ value == false |
| ✓ value == null |
| ✓ value != null |
| ✓ value == 1 |
| ✓ value != 2 |
| ✓ value == 0.100000 |
| ✓ value != 0.200000 |
| ✓ value == "hello" |
| ✓ value != "world" |
| i here is some information: 1 |
| Assertions: 10 passed |
| ✓ PASS |
| |
|------------------------------------------------------|
| Tests: 2 passed |
| Time: 0.004358s |
|------------------------------------------------------|
|----------------------------------|
| failing section |
|----------------------------------|
| |
| it_should_fail_all |
| ✗ statement |
| ✗ value == true |
| i value = false |
| ✗ value == false |
| i value = true |
| ✗ value == null |
| i value = 1 |
| ✗ value != null |
| i value = 0 |
| ✗ value == 2 |
| i value = 1 |
| ✗ value != 1 |
| i value = 1 |
| ✗ value == 0.200000 |
| i value = 0.100000 |
| ✗ value != 0.100000 |
| i value = 0.100000 |
| ✗ value == "world" |
| i value = "hello" |
| ✗ value != "hello" |
| i value = "hello" |
| i here is some information: 1 |
| Assertions: 10 failed |
| ✗ FAIL |
| |
|----------------------------------|
| Tests: 1 failed |
| Time: 0.002570s |
|----------------------------------|
|----------------------------------|
| both section |
|----------------------------------|
| |
| it_should_pass_all |
| ✓ statement |
| ✓ value == true |
| ✓ value == false |
| ✓ value == null |
| ✓ value != null |
| ✓ value == 1 |
| ✓ value != 2 |
| ✓ value == 0.100000 |
| ✓ value != 0.200000 |
| ✓ value == "hello" |
| ✓ value != "world" |
| i here is some information: 1 |
| Assertions: 10 passed |
| ✓ PASS |
| |
|----------------------------------|
| |
| it_should_fail_all |
| ✗ statement |
| ✗ value == true |
| i value = false |
| ✗ value == false |
| i value = true |
| ✗ value == null |
| i value = 1 |
| ✗ value != null |
| i value = 0 |
| ✗ value == 2 |
| i value = 1 |
| ✗ value != 1 |
| i value = 1 |
| ✗ value == 0.200000 |
| i value = 0.100000 |
| ✗ value != 0.100000 |
| i value = 0.100000 |
| ✗ value == "world" |
| i value = "hello" |
| ✗ value != "hello" |
| i value = "hello" |
| i here is some information: 1 |
| Assertions: 10 failed |
| ✗ FAIL |
| |
|----------------------------------|
| |
| it_should_fail_some |
| ✓ value == true |
| ✗ value == false |
| i value = true |
| Assertions: 1 passed / 1 failed |
| ✗ FAIL |
| |
|----------------------------------|
| Tests: 1 passed / 2 failed |
| Time: 0.003146s |
|----------------------------------|
|------------------|
| empty section |
|------------------|
| No tests run! |
| Time: 0.000000s |
|------------------|
The output is designed to be fairly simple and eye-catching for when assertions do fail.
✓denotes that the assertion has passed✗denotes that the assertion has failedidenotes information - provided either byTest_Outputor automatically when an assertion fails
Note that if you are using a SourceMod version lower than 1.10, you will not see the time output.
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.