gnustep/tools-make
0
0
Fork 0
mirror of https://github.com/gnustep/tools-make.git synced 2025-04-22 22:00:49 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

clarify a little

Browse source 
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@36397 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Richard Frith-MacDonald 2013-03-22 16:21:46 +00:00
parent 7cdc25ba25
commit 9a85fa7ebc
1 changed files with 13 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
TestFramework/README
View file

@ -4,10 +4,13 @@ TestFramework
This testsuite is a general framework for testing the core GNUstep
libraries. Since, in part, we are testing the very basic level of
an Objective-C runtime, we can't use more complete unit tests, such
as OCUnit <http://www.sente.ch/software/ocunit/>.
The aim of this framework is to provide a simple, yet reasonably
comprehensive regression test mechanism for Objective-C development.
an Objective-C runtime, we support testing plain C or C++ as well
as Objective-C, and aim for better flexibility, ease-of-use, and
and portability than older frameworks such as as OCUnit.
The aim of this framework is to provide a very simple, yet reasonably
comprehensive regression test mechanism, primarily for Objective-C
development.
Please run the GNUstep testsuite (using this framework) often, when
adding new features, fixing bugs and running on new platforms.
@ -42,8 +45,8 @@ or where a group of tests within a project is to be run:
gnustep-tests base/NSArray
You may run an individual test file by using the gnustep-tests script with the
name of the Objective-C test source file:
You may run an individual test file by using the gnustep-tests script
with the name of the Objective-C test source file:
gnustep-tests mytest.m
gnustep-tests base/NSDate/general.m
@ -120,6 +123,10 @@ eg.
(gdb) break testStart if line == 42
(gdb) run
If you use the --debug command line option, and any tests fail, then the
debugger (gdb) will automatically be started for you with breakpoints set
to the testStart() function of the failed tests.
You can use the --debug command line option in conjunction with the --failfast
option to have testing stopped at the first failure and the gdb debugger
automatically launched to debug the failed testcase with a breakpoint set