tests.txt


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
63
64
65
66
67
68
69
70

Tests for DBus binding test rig:

Tests are functions which will perform a particular transformation on the input and return the result. The should be defined as a DBus signature and description of the function. For example:

<annotation name="org.freedesktop.DBus.Description" value="Returns the sum of the values in the input list"/>
<method name="sum" >
   <arg type="ay" direction="in"/>
   <arg type="u" direction="out"/>
</method>

<annotation name="org.freedesktop.DBus.Description" value="Returns the sum of the values in the input list"/>
<method name="sum" >
   <arg type="ai" direction="in"/>
   <arg type="x" direction="out"/>
</method>

<annotation name="org.freedesktop.DBus.Description" value="Given a map of A => B, should return a map of B => a list of all the As which mapped to B"/>
<method name="mapping_invert" >
   <arg type="a{ss}" direction="in"/>
   <arg type="a{sas}" direction="out"/>
</method>

<annotation name="org.freedesktop.DBus.Description" value="This method returns the contents of a struct as separate values"/>
<method name="destruct" >
   <arg type="(sun)" direction="in"/>
   <arg type="s" direction="out"/>
   <arg type="u" direction="out"/>
   <arg type="n" direction="out"/>
</method>

<annotation name="org.freedesktop.DBus.Description" value="Given any compound type as a variant, return all the primitive types recursively contained within as an array of variants"/>
<method name="primitize" >
   <arg type="v" direction="in"/>
   <arg type="av" direction="out"/>
</method>

<annotation name="org.freedesktop.DBus.Description" value="inverts it's input"/>
<method name="invert" >
   <arg type="b" direction="in"/>
   <arg type="b" direction="out"/>
</method>

<annotation name="org.freedesktop.DBus.Description" value="triggers sending of a signal from the supplied object with the given parameter"/>
<method name="triggersignal" >
   <arg type="o" direction="in"/>
   <arg type="t" direction="in"/>
</method>

<signal name="triggered">
   <arg type="t"/>
</signal>

<signal name="trigger">
   <arg type="q"/>
   <arg type="d"/>
</signal>

<annotation name="org.freedesktop.DBus.Description" value="when the trigger signal is received, this method should be called on the sending service/object."/>
<method name="signalresponse" >
   <arg type="q" direction="in"/>
   <arg type="d" direction="in"/>
</method>


Clients try and cause these to fail in the most obscure way possible. Servers make sure all of their methods are called each run. Output format: