From: amalec Date: Fri, 22 Jun 2001 01:15:23 +0000 (+0000) Subject: Specfile changes, updates to NEWS X-Git-Tag: 0.10.0~1109 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=13e2018a4cb6d8ca581aa23266207e76d4e939c4;p=check Specfile changes, updates to NEWS git-svn-id: svn+ssh://svn.code.sf.net/p/check/code/trunk@33 64e312b2-a51f-0410-8e61-82d0ca0eb02a --- diff --git a/check/NEWS b/check/NEWS index e69de29..6d973b7 100644 --- a/check/NEWS +++ b/check/NEWS @@ -0,0 +1,10 @@ +Thu Jun 21, 2001: +Released Check 0.6.0 +Features improved unit test reporting options, more complete unit tests, and end-to-end test, and a full API into TestResults + +Check 0.5.2 +Minor edits +Check 0.5.1 +GPL compliance release +Check 0.5.0 +Initial public release diff --git a/check/doc/Makefile.am b/check/doc/Makefile.am index c22dfaa..3982f92 100644 --- a/check/doc/Makefile.am +++ b/check/doc/Makefile.am @@ -17,8 +17,7 @@ html_docs =\ example-1.html\ example-2.html\ example-3.html\ - example-4.html\ - example-5.html + example-4.html example_docs =\ money\ diff --git a/check/doc/example.lyx b/check/doc/example.lyx index 2441b6c..909cfd0 100644 --- a/check/doc/example.lyx +++ b/check/doc/example.lyx @@ -129,99 +129,6 @@ The Check project page is at \layout Section -How to get Check -\layout Subsection - -Anonymous CVS -\layout Standard - -Check is currently under development, so the normal way to get Check is - through CVS. - Follow the following simple instructions: -\layout Enumerate - -Navigate to the directory below which you want the new check directory to - be formed. - That is, if you navigate to /home/luser/foo/bar, the check files will be - in /home/luser/foo/bar/check. -\layout Enumerate - -Issue the following command to login to CVS. - When prompted to supply the anonymous password, simply hit return. -\begin_deeper -\layout Code - -cvs -d:pserver:anonymous@cvs.check.sourceforge.net:/cvsroot/check login -\end_deeper -\layout Enumerate - -Issue the following command to setup the check subdirectory -\begin_deeper -\layout Code - -cvs -z3 -d:pserver:anonymous@cvs.check.sourceforge.net:/cvsroot/check co check -\end_deeper -\layout Enumerate - -To keep current with CVS, use the following command within the check directory -\begin_deeper -\layout Code - -cvs -z3 update -dP -\layout Standard - -Note that you do not have to supply the server directory path or the user - name (it is all kept in the CVS local directory.) -\end_deeper -\layout Standard - -From that point on, using Check should simply be a matter of the standard: - -\layout Code - -$ ./configure -\layout Code - -$ make -\layout Code - -$ make install -\layout Standard - -Of course, since Check comes with its own unit tests, you can substitute - -\begin_inset Quotes eld -\end_inset - -make check -\begin_inset Quotes erd -\end_inset - - for -\begin_inset Quotes eld -\end_inset - -make -\begin_inset Quotes erd -\end_inset - - in the above. -\layout Subsection - -Contributing -\layout Standard - -The author welcomes any and all help with Check, whether through enhancement - requests, bug reports, patches, documentation, etc. - Please visit the Check project page at -\begin_inset LatexCommand \htmlurl[http://sourceforge.net/projects/check/]{http://sourceforge.net/projects/check/} - -\end_inset - -. - Check is free software, licensed under the GPL. -\layout Section - Unit testing in C \layout Standard @@ -685,8 +592,9 @@ The code in main bears some explanation. We then run the suite, using the CRNORMAL flag to specify that we should print a summary of the run, and list any failures that may have occurred. We could also have specified the CRSILENT flag to specify that no output - should occur, and the CRMINIMAL flag to specify that only the run summary - should be printed. + should occur, the CRMINIMAL flag to specify that only the run summary should + be printed, or the CRVERBOSE flag to indicate that all tests should be + reported on, whether they passed or failed. We capture the number of failures that occurred during the run, and use that to decide how to return. The check target created by Automake uses the return value to decide whether @@ -700,12 +608,13 @@ Running suite: Money 0%: Checks: 1, Failures: 1, Errors: 0 \layout Code -check_money.c:9:Core: Amount not set correctly on creation +check_money.c:9:F:Core: Amount not set correctly on creation \layout Standard The first number in the summary line tells us that 0% of our tests passed, and the rest of the line tells us that there was one check, and one failure. - The next line tells us exactly where that failure occurred. + The next line tells us exactly where that failure occurred, what kind of + failure it was (P for pass, F for failure, E for error). \layout Standard Let's implement the money_amount function, so that it will pass its tests. @@ -746,7 +655,7 @@ Running suite: Money 0%: Checks: 1, Failures: 0, Errors: 1 \layout Code -check_money.c:5:Core: (after this point) Received signal 11 +check_money.c:5:E:Core: (after this point) Received signal 11 \layout Standard What does this mean? Note that we now have an error, rather than a failure. diff --git a/check/doc/index.html b/check/doc/index.html index fb4cee0..8a49b53 100644 --- a/check/doc/index.html +++ b/check/doc/index.html @@ -15,22 +15,21 @@

Check was inspired by similar frameworks that currently exist for most programming languages; the most famous example being - JUnit for Java ( www.junit.com - ). There is a list of unit test frameworks for multiple languages - at - www.xprogramming.com/software.htm - . Unit testing has a long history as part of formal quality + JUnit for Java (www.junit.com). There + is a list of unit test frameworks for multiple languages at www.xprogramming.com/software.htm + . Unit testing has a long history as part of formal quality assurance methodologies, but has recently been associated with the lightweight methodology called Extreme Programming. In that methodology, the characteristic practice involves interspersing - unit test writing with coding (" test a little, code a little" - ). While the incremental unit test/code approach is indispensable - to Extreme Programming, it is also applicable, and perhaps - indispensable, outside of that methodology. -

The incremental - test/code approach provides three main benefits to the developer: -

+ unit test writing with coding (" test a little, code a + little"). While the incremental unit test/code approach is + indispensable to Extreme Programming, it is also applicable, and + perhaps indispensable, outside of that methodology. + +

The incremental test/code approach provides three main benefits + to the developer:

+

  1. Because the unit tests use the interface to the unit being tested, they allow the developer to think about how the @@ -57,6 +56,8 @@ trails; with it, you can take the most direct path to where you want to go.

    +

    Information about Check

    +

    Look at the Check homepage for the latest information on Check: http://check.sourceforge.net @@ -66,11 +67,71 @@ HREF="http://sourceforge.net/projects/check/">http://sourceforge.net/projects/check/

    -

    Check can be dowloaded from here.

    -

    A tutorial introduction to Check can be found here.

    + +

    Getting Check

    +

    Check can be dowloaded from here.

    + +

    Contributing

    + +

    The author welcomes any and all help with Check, whether + through enhancement requests, bug reports, patches, documentation, + etc. Please visit the Check project page at http://sourceforge.net/projects/check/ + +

    To contribute to Check, you should download the source through + anonymous CVS, following these simple instructions:

    +
      +
    1. Navigate to the directory below which you want the new check + directory to be formed. That is, if you navigate to + /home/luser/foo/bar, the check files will be in + /home/luser/foo/bar/check.
      2. + +
    2. Issue the following command to login to CVS. When prompted + to supply the anonymous password, simply hit return. +
      +
      +$ cvs -d:pserver:anonymous@cvs.check.sourceforge.net:/cvsroot/check login
+
      +
      +
      3. +
    3. Issue the following command to setup the check subdirectory +
      +
      +$ cvs -z3 -d:pserver:anonymous@cvs.check.sourceforge.net:/cvsroot/check co check
+
      +
      +
      4. + +
    4. To keep current with CVS, use the following command within the +check directory +
      +
      +$ cvs -z3 update -dP 
+
      +
      + +

      Note that you do not have to supply the server directory + path or the user name (it is all kept in the CVS local + directory.) +

      5. +
    + +

    From that point on, using Check should simply be a matter of + the standard: +

    +

    + 
    +$ ./configure
+$ make
+$ make install
+
    +
    +

    Of course, since Check comes with its own unit tests, you can (and should) + substitute "make check" for "make" in the above.

    + SourceForge Logo diff --git a/check/rpm/check.spec b/check/rpm/check.spec index d8debe4..372031b 100644 --- a/check/rpm/check.spec +++ b/check/rpm/check.spec @@ -1,15 +1,16 @@ Summary: A unit test framework for C Name: check -Version: 0.5.2 +Version: 0.6.0 Release: 1 Epoch: 1 -Source: http://prdownloads.sourceforge.net/check/check-0.5.2.tar.gz +Source: http://prdownloads.sourceforge.net/check/check-0.6.0.tar.gz Group: Development/Tools Copyright: GPL URL: http://check.sourceforge.net Prefix: %{_prefix} BuildPrereq: lyx sgml-tools BuildRoot: %{_tmppath}/%{name}-%{version}-root +Packager: Arien Malec %description Check is a unit test framework for C. It features a simple interface for defining unit tests, putting little in the way of the developer. Tests are run in a separate address space, so Check can catch both assertion failures and code errors that cause segmentation faults or other signals. The output from unit tests can be used within source code editors and IDEs. @@ -45,7 +46,6 @@ rm -rf ${RPM_BUILD_ROOT} %doc %{_prefix}/share/doc/%{name}-%{version}/example-2.html %doc %{_prefix}/share/doc/%{name}-%{version}/example-3.html %doc %{_prefix}/share/doc/%{name}-%{version}/example-4.html -%doc %{_prefix}/share/doc/%{name}-%{version}/example-5.html %doc %{_prefix}/share/doc/%{name}-%{version}/example.html %doc %{_prefix}/share/doc/%{name}-%{version}/example.lyx %doc %{_prefix}/share/doc/%{name}-%{version}/example.sgml @@ -68,5 +68,7 @@ rm -rf ${RPM_BUILD_ROOT} %doc %{_prefix}/share/doc/%{name}-%{version}/money/config.h.in %changelog +* Thu Jun 21 2001 Arien Malec +- Updated for 0.6.0, removed example-5.html * Sat Jun 2 2001 Arien Malec - First packaging. diff --git a/check/tests/Makefile.am b/check/tests/Makefile.am index 0af06be..c789552 100644 --- a/check/tests/Makefile.am +++ b/check/tests/Makefile.am @@ -1,6 +1,7 @@ TESTS=check_check check_list check_check_msg test_output.sh noinst_PROGRAMS=check_check check_list check_stress check_check_msg ex_output +EXTRA_DIST=test_output.sh check_check_SOURCES= \ check_check.c diff --git a/check/tests/Makefile.in b/check/tests/Makefile.in index d40cfde..ea58b26 100644 --- a/check/tests/Makefile.in +++ b/check/tests/Makefile.in @@ -70,6 +70,7 @@ have_sgmltools = @have_sgmltools@ TESTS = check_check check_list check_check_msg test_output.sh noinst_PROGRAMS = check_check check_list check_stress check_check_msg ex_output +EXTRA_DIST = test_output.sh check_check_SOURCES = check_check.c