File: check_single_server.sb

package info (click to toggle)
mysql-sandbox 3.2.05-1.1
  • links: PTS
  • area: main
  • in suites: forky, sid, trixie
  • size: 916 kB
  • sloc: perl: 9,878; sh: 191; makefile: 8
file content (47 lines) | stat: -rw-r--r-- 1,540 bytes parent folder | download | duplicates (2)
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
# This is a sample user defined test
# that you can run using test_sandbox
#
# There are two kind of tests: shell and sql
# the test type is defined by a keyword 
# followed by a colon.

# The 'shell' test requires a 'command', which is
# passed to a shell.
# The 'expected' label is a string that you
# expect to find within the shell output.
# If you don't expect anything, you can just 
# say "expected = OK", meaning that you will
# be satisfied with a ZERO exit code reported 
# by the operating system.
# The 'msg' is the description of the test
# that is shown to you when the test runs.
shell:
command  = make_sandbox $TEST_VERSION -- --no_confirm --sandbox_directory=msb_XXXX
expected = sandbox server started
msg      = sandbox creation

# The 'sql' test requires a 'path', which is the
# place where the test engine expects to find a
# 'use' script.
# The 'query' is passed to the above mentioned script
# and the output is captured for further processing.
# The 'expected' parameter is a string that you want 
# to find in the query output.
# The 'msg' parameter is like the one used with the
# 'shell' test.
sql:
path    = $SANDBOX_HOME/msb_XXXX
query   = select 10 * 10
expected = 100
msg      = checking database response

# All strings starting with a $ are expanded to their 
# corresponding environment variables. 
# For example, if $SANDBOX_HOME is /home/sb/tests,
# the line below will expand to
# command = /home/sb/tests/msb_5_1_30/stop

shell:
command  = $SANDBOX_HOME/msb_XXXX/stop
expected = OK
msg      = stopped