File: README

package info (click to toggle)
libdbi-drivers 0.9.0-13
  • links: PTS
  • area: main
  • in suites: forky, sid, trixie
  • size: 7,160 kB
  • sloc: ansic: 19,030; sh: 10,963; xml: 2,759; makefile: 584
file content (51 lines) | stat: -rw-r--r-- 1,862 bytes parent folder | download | duplicates (6)
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
Tests cases to libdbi framework
======================================

The tests they are in this directory are to cover the functions describe in the
libdbi reference guide. Each *.c file covers specific functions and are
grouped following the documentation.

We are using the Cgreen unit test framework. You will need the Cgreen
to execute the tests. You can get it, http://sourceforge.net/projects/cgreen,
compiling and install in your system. 

Fortunately the libdbi test framework provide it for you. No worry about it.
 
Steps to execute the tests
==============================

- Local tests:

* Install Cgreen (optional, we provide it)
* cd ~/libdbi-drivers/tests
* make check
* answers the questions about your database engine
* see the results of the tests.

- How to submit the tests results to dashboard

* You will need install the cmake package. It provides the 
  ctest tool which we use to submit the tests results. You can
  get it from www.cmake.org or check with your distro packages.

* Edit the file test_dbi.cfg (which was generated by ./configure script)
  and changes:
  type=[can be Experimental or Continuous or Nightly]
  tag=[tag to identify your build]
  dbengine strings
 
 You can change 'sitename' if you want.
 
* Run the script ./run_test.sh. It will start dbi_test with correct 
  options to generate a CDash reporter. 
* When the script finished CTest will automatically submitted the results 
  to a dashboard.
* Now you can see the results at http://my.cdash.org/index.php?project=libdbi-drivers

Notes
=====

Submit the tests results to a dashboard is a very useful because the developers can 
see what happens more quickly without the need of cut-and-paste the tests results
in mail list. We can see too how many platforms the libdbi framework runs, checking build and
configure, tests coverage and more others things.