aRts audio server
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Timothy Pearson c5c1052f4b Remove additional unneeded tq method conversions 8 年之前
..
README.test Copy of aRts for Trinity modifications 10 年之前
remotetest.idl Copy of aRts for Trinity modifications 10 年之前
test.h Updated obsolete GPL license addresses to current GPL address 10 年之前
testanyref.cc Updated obsolete GPL license addresses to current GPL address 10 年之前
testbuffer.cc Updated obsolete GPL license addresses to current GPL address 10 年之前
testchangenotify.cc Revert previous commit...some bugs crept in since last build test a week ago and I woul prefer to fix them over the next few days before commiting this patch set. 9 年之前
testdispatcher.cc Updated obsolete GPL license addresses to current GPL address 10 年之前
testflowsystem.cc Updated obsolete GPL license addresses to current GPL address 10 年之前
testifacerepo.cc rename the following methods: 8 年之前
testnotification.cc Updated obsolete GPL license addresses to current GPL address 10 年之前
testremote.cc Revert previous commit...some bugs crept in since last build test a week ago and I woul prefer to fix them over the next few days before commiting this patch set. 9 年之前
testwrapper.cc Remove additional unneeded tq method conversions 8 年之前
value.idl Copy of aRts for Trinity modifications 10 年之前
value_impl.cc Updated obsolete GPL license addresses to current GPL address 10 年之前
wrapper.idl Copy of aRts for Trinity modifications 10 年之前

README.test

                  C++ automatic testing similar to JUnit
Stefan Westerfeld <stw@kde.org>

What it is:
===========

These tests use a little testing framework, which consists currently only
of the file test.h. It is very much inspired by JUnit (www.junit.org), but it
is maybe even simpler. But it integrates nicely in Makefile.am automatic
testing. You can simply type

make check

to see if all tests pass. The motivation behind it is, when you are working
on a large project, it is often impossible to test quickly whether everything
still works all right after changes (which you should before committing ...).
This is even more true if you are not working alone on the code.

With a consistent set of tests that verify whether everything is still all
right, things like breaking one thing while fixing another can be made less
likely at least.

How to add a new set of tests:
==============================

1. create a new .cc file, for this example we'll suppose testarithmetic.cc
2. #include "test.h"
3. create a struct which will hold all your tests

struct TestArithmetic : public TestCase {
TESTCASE(TestArithmetic);
};

4. if you want to, override the following methods:

void setUp()
{
/*
* This method is supposed to build a little test world, which will be
* built for each test method that is executed - the idea is that your
* tests will use this environment to test in.
*/
}
void tearDown()
{
/*
* This method should completely destroy your test world again, so
* that for the next test, a fresh one can be created.
*/
}

5. define new tests like this

TEST(arithmetic) {
long a = 2;
long b = 2;
long c = a+b;

testAssert(c < 5); // you assert that this condition is true
testEquals(4,c); // you assert that the first (expected) value
} // equals the second (computed) value

6. define a main for your test like this

TESTMAIN(TestArithmetic);

7. add the following to the Makefile.am (you may want to add more source files,
as required)

testarithmetic_SOURCES = testarithmetic.cc

8. add it to check_PROGRAMS