Lines Matching full:testsuite
51 * Testsuite::
5531 File: gdbint.info, Node: Releasing GDB, Next: Testsuite, Prev: Start of New Year Procedure, Up: Top
6169 File: gdbint.info, Node: Testsuite, Next: Hints, Prev: Releasing GDB, Up: Top
6171 18 Testsuite
6174 The testsuite is an important component of the GDB package. While it
6180 The GDB testsuite uses the DejaGNU testing framework. The tests
6184 18.1 Using the Testsuite
6187 To run the testsuite, simply go to the GDB object directory (or to the
6188 testsuite's objdir) and type `make check'. This just sets up some
6190 the testsuite is running, you'll get mentions of which test file is in
6192 testsuite is finished, you'll get a summary that looks like this:
6209 real problems, whether in GDB or in the testsuite. Expected failures
6220 testsuite before and after the change, to confirm that there are no
6222 run the testsuite with all supported configurations and a variety of
6244 18.2 Testsuite Organization
6247 The testsuite is entirely contained in `gdb/testsuite'. While the
6248 testsuite includes some makefiles and configury, these are very minimal,
6251 `testsuite/lib/gdb.exp' contains common utility procs useful for all
6252 GDB tests, while the directory `testsuite/config' contains
6256 The tests themselves are to be found in `testsuite/gdb.*' and
6269 This is the base testsuite. The tests in it should apply to all
6313 styles, it's worth having a mix of styles in the testsuite; for
6319 File: gdbint.info, Node: Hints, Next: GDB Observers, Prev: Testsuite, Up: Top
7565 * running the test suite: Testsuite. (line 19)
7698 * test suite: Testsuite. (line 6)
7699 * test suite organization: Testsuite. (line 79)
7764 * writing tests: Testsuite. (line 131)
7813 Node: Testsuite244100
