consultkillo.blogg.se

1. #Code c emptystack and freestack link list how to#
2. #Code c emptystack and freestack link list mac os#

But make is failed in test/ because test/Makefile doesn't exist. We find that make go down to test/ to build. Make: Leaving directory `/tmp/stack/test' Make: Entering directory `/tmp/stack/test' & /bin/sh /tmp/stack/config/missing -run automake-1.10 -foreign Makefile Make will detect Makefile.am is changed and update Makefile and so on automatically after we change Makefile.am and run make. Next, to build test/test-stack.c in test/ directory, we need to specify that there is test/ directory as sub directory in Makefile.am. Makefile.am: ACLOCAL_AMFLAGS = $$ACLOCAL_ARGS The following test code is a whole test code to test "a newly created stack should be empty".įirst, put the following configuration to use ACLOCAL_ARGS environment variable for autogen.sh with aclocal invoked via make: Writing tests with Cutter means that writing a program that verifies a target program works as we expected at the specific situation. Test/test-stack.c: void test_new_stack (void) Ĭut_assert() is a macro that fails if the first argument is 0, passes otherwise. Next, we write a test with the stack API:

In this tutorial, we make a test program as test/test-stack.c.įirst, we need to include cutter.h to use Cutter.Īnd we need to include stack.h that declares API for test target stack implementation. There are source codes of this program in sample/stack/.Ī test program is put into test/. We assume that Cutter is already installed into your system.

#Code c emptystack and freestack link list how to#

We will learn how to use Cutter with writing a stack implementation. Cutter is a testing framework and respects to xUnit style. Cutter provides many useful test support features with portability due to GLib.

#Code c emptystack and freestack link list mac os#

GLib is a very portable library that works on not only UNIX-like system but also Windows and Mac OS X. It's important that both a program and tests are works well on several environment easily.Ĭutter requires only GLib. If tests of the program works on the environment too, we can verify the program works well on the environment easily. It's better that a program works on several environment without many costs. For this reason, we can build our program and tests on several environment easily. GNU build system lessens disparities on build environment. We use GNU build system (GNU Autoconf/GNU Automake/GNU Libtool) for build system. To write tests, we use Cutter that is a unit testing framework for C. We write a program (library) that implements a stack in C.