|
2274.1.5
by patrick crews
Added initial docs for cnf file tricks - using pre-populated datadir for starters |
1 |
**********************************
|
2 |
Writing drizzletest test cases
|
|
3 |
**********************************
|
|
4 |
||
5 |
Synopsis
|
|
6 |
========
|
|
7 |
||
8 |
Here, we discuss various topics related to writing test cases, with a focus on features |
|
9 |
that allow for more complex testing scenarios. Additional documentation for other testing |
|
10 |
tools will come later. |
|
11 |
||
12 |
Using a pre-populated datadir
|
|
13 |
=============================
|
|
14 |
The experimental test runner, dbqp allows for starting a server with a pre-populated datadir |
|
15 |
for a test case. This is accomplished via the use of a .cnf file (versus a master.opt file) |
|
16 |
Over time, this will be the direction for all drizzletest cases. |
|
17 |
||
18 |
The .cnf file shown below tells the test-runner to use the directory drizzle/tests/std_data/backwards_compat_data |
|
19 |
as the datadir for the first server. If a test uses multiple servers, the .cnf file can have additional sections ([s1]...[sN])::
|
|
20 |
||
21 |
[test_servers]
|
|
22 |
servers = [[]]
|
|
23 |
||
24 |
[s0]
|
|
25 |
load-datadir=backwards_compat_data
|
|
26 |
||
27 |
||
28 |
All datadirs are expected to be in tests/std_data. If there is need for the ability to use datadirs outside of this location, |
|
29 |
it can be explored. |
|
30 |