File: UnitTestScript.schelp

package info (click to toggle)
supercollider 1%3A3.13.0%2Brepack-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 80,292 kB
  • sloc: cpp: 476,363; lisp: 84,680; ansic: 77,685; sh: 25,509; python: 7,909; makefile: 3,440; perl: 1,964; javascript: 974; xml: 826; java: 677; yacc: 314; lex: 175; objc: 152; ruby: 136
file content (56 lines) | stat: -rw-r--r-- 1,398 bytes parent folder | download | duplicates (4)
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
TITLE:: UnitTestScript
summary:: run test scripts
categories:: Testing
related:: Classes/UnitTest, Classes/UnitTestResult

DESCRIPTION::
In order to make sure a method works correctly, a test can be implemented that assures the correct behavior.

It is a common practice to write tests to clarify how an object should respond, and it may avoid inconsistencies on the long run.

Test scripts are simply plain text files ending with TELETYPE::_unittest.scd::, which are interpreted.
Scripts may be located next to a class in the classpath or one folder below.
If they return a function, the code::UnitTestScript:: is passed in, allowing to call methods like assert etc. (see link::Classes/UnitTest::)

code::UnitTestScript:: mimics some of the behavior of link::Classes/Method::, to be compatible with link::Classes/UnitTest::.






CLASSMETHODS::
PRIVATE:: initClass, findTestScripts, new, findTestMethods, allScripts, runTest

INSTANCEMETHODS::

PRIVATE:: name, path, init, runScript

EXAMPLES::

An example script

NOTE::
This should be in a file TELETYPE::myUnitTest_unittest.scd::
::

code::
{ |test|
	"Kant test".postln;
	"5 + 7 = ".post;
	(5 + 7).postln;
	test.assertEquals(5 + 7, 12, "five plus seven should always be twelve");
}
::

To run only the test scripts:

code::
UnitTestScript.run;
::

The scripts are to be found under the class UnitTestScript in the GUI:

code::
UnitTest.gui
::