ctrl+shift+p filters: :st2 :st3 :win :osx :linux


by SublimeText ALL

Testing Sublime Text Packages


  • 1.5.4
  • github.​com
  • github.​com
  • 1 month ago
  • 59 minutes ago
  • 7 years ago


  • Total 2K
  • Win 994
  • Mac 731
  • Linux 548
Aug 2 Aug 1 Jul 31 Jul 30 Jul 29 Jul 28 Jul 27 Jul 26 Jul 25 Jul 24 Jul 23 Jul 22 Jul 21 Jul 20 Jul 19 Jul 18 Jul 17 Jul 16 Jul 15 Jul 14 Jul 13 Jul 12 Jul 11 Jul 10 Jul 9 Jul 8 Jul 7 Jul 6 Jul 5 Jul 4 Jul 3 Jul 2 Jul 1 Jun 30 Jun 29 Jun 28 Jun 27 Jun 26 Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19
Windows 0 0 0 0 1 2 0 0 0 1 1 0 1 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 1 0 0 0 0 0 0 0 0 0
Mac 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 1 1 0 1 0 0 0 0 0 1 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0




Github Action codecov

This is a unittest framework for Sublime Text. It runs unittest testcases on local machines and CI services such as Travis CI, Circle CI and AppVeyor. It also supports testing syntax_test files for the new sublime-syntax format.

Deprecation of supports of CircleCI, Travis and Appveyor.

It is too much work to maintain supports for circleci, travis, appveyor and github actions at the same time. As most users host their projects on github, we are going to only support github actions and deprecate supports for circleci, travis and appveyor.

There is no plan to remove the corresponding scripts from the repo in a near future, but they are not maintained any more and may be removed if they are broken.

Sublime Text 4

Sublime Text 4 is now supported. However test coverage on Python 3.8 packages is still not working now.


  1. Before testing anything, you have to install UnitTesting via Package Control.
  2. Your package!
  3. TestCases should be placed in test*.py under the directory tests (configurable, see below). The testcases are then loaded by TestLoader.discover.

Here are some small examples

Running Tests Locally

UnitTesting can be triggered via the command palette command UnitTesting. Enter the package name in the input panel and hit enter, a console should pop up and the tests should be running. To run only tests in particular files, enter <Package name>:<filename>. <filename> should be a unix shell wildcard to match the file names, <Package name>:test*.py is used in default.

You could run the command UnitTesting: Test Current Package to run the current package. The current package will be first reloaded by UnitTesting and then the tests will be executed.

It is also possible to generate test coverage report via coverage by using the command UnitTesting: Test Current Package with Coverage. The file .coveragerc is used to control the coverage configurations. If it is missing, UnitTesting will ignore the tests directory.

GitHub Actions

These environmental variables are used

  • PACKAGE: the package name, it is needed if the repo name is different from the package name.
  • SUBLIME_TEXT_ARCH: x32 (Sublime Text 3 only) or x64
  • UNITTESTING_TAG: a specific version of UnitTesting to use

To enable GitHub Actions, copy the file build.yml to your repository.

Coverage reports

We support Codecov, Coveralls and Codacy. Codecov is recommended as it supports merging reports from different CIs.


To submit coverage report to codecov.io:

  1. install codecov
  2. run codecov after success

For GitHub Actions, copy the CODECOV_TOKEN from codecov.io to GitHub's Secret tab.


To submit coverage report to coveralls.io:

  1. install python-coveralls
  2. run coveralls after success


To submit coverage report to codacy.com:

  1. install both coverage and codacy-coverage

    pip install coverage codacy-coverage
  2. generate the xml report: coverage xml -o coverage.xml

  3. run python-codacy-coverage

Installing Package Control and Dependencies

If your package uses Package Control dependencies, you may want to install Package Control by uncommenting the line of install_package_control in Travis CI and AppVeyor configuration files.

Testing syntax_test files

Check this for an example.


Use a different test directory

The default test directory is “tests”. To change the test directory, add a file unittesting.json to your repo with the corresponding directory name, eg unittest:

"tests_dir" : "unittest"

Redirect test result to a file

The test result could be redirected to a file by specifying the output variable in unittesting.json.

"output" : "foo.txt"

Deferred testing

Tests can be written using the Deferrable testcase, such that you are able to run sublime commands from your test cases and yield control to sublime text runtime and continue the execution later. Would be useful to test asynchronous codes.

An example would be found in here.

To activate deferred testing, put the following line in unittesting.json.

"deferred": true,

PS: this idea was inspired by Plugin UnitTest Harness.

DeferrableTestCase is used to write the test cases. They are executed by the DeferringTextTestRunner and the runner expects not only regular test functions, but also generators. If the test function is a generator, it does the following

  • if the yielded object is a callable, the runner will evaluate the callable and check its returned value. If the result is True, the runner continues the generator, if not, the runner will wait until the condition is met.

  • If the yielded object is an integer, say x, then it will continue the generator after x ms.

  • Otherwise, the yield statement would yeild to any queued jobs.

Async testing

By default, the tests are running in the main thread and can block the graphic inference. Asychronized testing could be used if you need the interface to respond.

Async tests are usually slower than the sync tests because the interface takes time to respond but it is useful when there are blocking codes in the tests. An example would be found in here.

However, it is known that async test does not work very well with coverage. In general, it is recommended to use deferred testing over async testing since there is no need to worry about race condition.

To activate async testing on Travis CI and AppVeyor, put the following line in unittesting.json.

"async": true,

Note: if async is true, deferred is forced to be false (relaxation of this is in progress)


Add Test Current Package build

It is recommended to add the following in your .sublime-project file so that c+b would invoke the testing action.

    "name": "Test Current Package",
    "target": "unit_testing_current_package",

Docker container

Check https://github.com/SublimeText/UnitTesting/tree/master/docker


Thanks guillermooo and philippotto for their efforts in AppVeyor and Travis CI macOS support.