1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
|
title:: Writing tests
summary:: Get started with writing unit tests
categories:: Testing
related:: Reference/SCDocSyntax, Classes/SCDoc
To write, use and develop UnitTests, you need to
list::
## install a sourcecode version of SuperCollider
## install the code::UnitTesting:: Quark
## change your environment to include only core library functionality
## run UnitTests
::
section:: install a sourcecode version of SuperCollider
Download or clone SuperCollider from github: https://github.com/supercollider/supercollider.
It is not needed to compile SuperCollider from its sources, you can instead use a pre-compiled binary and include the relevant folders (code::SCClassLibrary, HelpSource, testsuite/classlibrary:: in your environment. See below for an example.
section:: install the code::UnitTesting:: Quark
The code::UnitTest:: framework is not part of the core library but provided as a quark.
To install it, run
code::
Quarks.install("UnitTesting");
::
and recompile the language.
section:: Change your environment to include only core library functionality
In order to mimick the standard SuperCollider installation, make sure that you have only the class library installed.
Best practise is to create a separate code::.yaml:: configuration file that resides parallel to the default one. You can do this either interactively from within the preferences of your IDE (code::Preferences>Interpreter::), or programatically
code::
~sclangConf = "SCLANG_CONF".getenv;
LanguageConfig.addIncludePath(~travisBuildDir +/+ "testsuite/classlibrary");
+ LanguageConfig.addExcludePath(~travisBuildDir +/+ "testsuite/classlibrary/server");
+ LanguageConfig.addExcludePath(Quarks.folder +/+ "UnitTesting/tests");
+ postf("Writing configuration to %\n", ~sclangConf);
+ LanguageConfig.store(~sclangConf);
::
section:: Organisation
Core class code::UnitTest::s are located in the directory
1. UnitTests go into parrallel directlry
2. server-related tests go into `server` subdir (travis)
3. UnitTests should use assert and assertFloat
4. look at existing UnitTests to understand what are good UnitTests
5. UnitTest setup
8. run UnitTests either automatically (UnitTest.runAll), interactively (UnitTEst.gui), or individually by class (MyClass.test / TestMyClass.run << synonyms)
section:: Writing new tests
The simplest way is to look at an existing help file or class document, and read this document and link::Reference/SCDocSyntax::
|
