Thread: [Cgdb-devel] Test suite
Brought to you by:
bobbybrasko,
crouchingturbo
From: Mike M. <mmu...@cs...> - 2004-02-29 06:21:27
|
The test suite in tgdb isn't working for me... I get the following result: === tgdb tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /home/mike/prog/cgdb/tgdb/testsuite/config/unix.exp as tool-and-target-specific interface file. Running /home/mike/prog/cgdb/tgdb/testsuite/tgdb.base/_sanity.exp ... Running /home/mike/prog/cgdb/tgdb/testsuite/tgdb.base/basic.exp ... FAIL: timeout buffering commands FAIL: timeout sink_after_buffered_commands Running /home/mike/prog/cgdb/tgdb/testsuite/tgdb.base/overloaded.exp ... ERROR: couldn't load tgdb.base/overloaded into tgdb_driver. make[2]: *** [check-DEJAGNU] Error 1 On a related note... do you think we should create a top level test suite directory so that one 'make check' can test all the aspects of the tool that we have tests for? Since we're creating new classes, I feel like testing should be integrated into the development from the start. Does this make any sense? Mike |
From: Bob R. <bo...@br...> - 2004-02-29 13:33:41
|
On Sun, Feb 29, 2004 at 01:12:10AM -0500, Mike Mueller wrote: > The test suite in tgdb isn't working for me... I get the following > result: >=20 > =3D=3D=3D tgdb tests =3D=3D=3D >=20 > Schedule of variations: > unix >=20 > Running target unix > Using /usr/share/dejagnu/baseboards/unix.exp as board description > file for target. > Using /usr/share/dejagnu/config/unix.exp as generic interface file > for target. > Using /home/mike/prog/cgdb/tgdb/testsuite/config/unix.exp as > tool-and-target-specific interface file. > Running /home/mike/prog/cgdb/tgdb/testsuite/tgdb.base/_sanity.exp > ... > Running /home/mike/prog/cgdb/tgdb/testsuite/tgdb.base/basic.exp ... > FAIL: timeout buffering commands > FAIL: timeout sink_after_buffered_commands > Running /home/mike/prog/cgdb/tgdb/testsuite/tgdb.base/overloaded.exp > ... > ERROR: couldn't load tgdb.base/overloaded into tgdb_driver. > make[2]: *** [check-DEJAGNU] Error 1 >=20 >=20 > On a related note... do you think we should create a top level test > suite directory so that one 'make check' can test all the aspects of > the tool that we have tests for? Since we're creating new classes, > I feel like testing should be integrated into the development from > the start. Does this make any sense? Do you have dejagnu installed? Try=20 $ runtest --version I am ~/.dejagnurc Expect version is 5.32.2 Tcl version is 8.3 Framework version is 1.4.2.x Ok, here is the deal. The testsuite was originally written for TGDB only. The dejagnu tool, is good for testing programs that receive text as input and then have text as output. Basically, it uses regexp to determine if you think it passed based of off it's output. How do you propose we test the functionality of CGDB? Make CGDB work in a mode were it just output's text. (It doesn't display a gui?) Or should we fire off a few Email's to the dejagnu list and see if they have any advice? Thanks, Bob Rossi |
From: Mike M. <mmu...@cs...> - 2004-02-29 16:00:30
|
$ runtest --version WARNING: Couldn't find the global config file. Expect version is 5.37.1 Tcl version is 8.3 Framework version is 1.4.3 I'm mainly referring to the fact that we're writing libraries to do things like KUI, so the dejagnu tests might apply there too. I'm not saying we should be testing the gui, because that would probably be impossible. Since there are libraries in tgdb and cgdb that merit testing, shouldn't the test suite be at the top level? Mike On Sat, 28 Feb 2004, Bob Rossi wrote: :Do you have dejagnu installed? :Try :$ runtest --version :I am ~/.dejagnurc :Expect version is 5.32.2 :Tcl version is 8.3 :Framework version is 1.4.2.x : :Ok, here is the deal. The testsuite was originally written for TGDB :only. The dejagnu tool, is good for testing programs that receive text :as input and then have text as output. Basically, it uses regexp to :determine if you think it passed based of off it's output. : :How do you propose we test the functionality of CGDB? Make CGDB work in :a mode were it just output's text. (It doesn't display a gui?) : :Or should we fire off a few Email's to the dejagnu list and see if they :have any advice? : :Thanks, :Bob Rossi : |
From: Bob R. <bo...@br...> - 2004-02-29 23:32:06
|
On Sun, Feb 29, 2004 at 10:50:59AM -0500, Mike Mueller wrote: > $ runtest --version > WARNING: Couldn't find the global config file. > Expect version is 5.37.1 > Tcl version is 8.3 > Framework version is 1.4.3 Ok, this looks good. Did you do make && make install before you did make check? > I'm mainly referring to the fact that we're writing libraries to do > things like KUI, so the dejagnu tests might apply there too. I'm > not saying we should be testing the gui, because that would probably > be impossible. Since there are libraries in tgdb and cgdb that > merit testing, shouldn't the test suite be at the top level? I agree with you. Initially, the idea was to not couple tgdb to cgdb. This way, another process could check out just cgdb/tgdb and have a working testsuite. Can you think of a good solution that would keep this relationship true? or should we abandon this relationship and combine the testsuite into a top-level testsuite? Bob Rossi |