Recent changes to Home

Home modified by Lukas Kucera

Lukas Kucera — Mon, 10 Feb 2014 10:14:26 -0000

--- v6
+++ v7
@@ -17,7 +17,7 @@
 - Micro-framework then evaluates test case as failed and adjusts statistics for test case and suite that contains this test case,

 **Usage**
-1 At the beginning, user has to create test suite(s),
+- At the beginning, user has to create test suite(s),
 - Then adds test cases to created suites,
 - Adds suite to test plan,
 - Previous steps are done for each suite(s) and case(s) as necessary,

Home modified by Lukas Kucera

Lukas Kucera — Mon, 10 Feb 2014 10:14:08 -0000

--- v5
+++ v6
@@ -11,18 +11,18 @@
 - Dynamic adding and removing of tests into suite and suites into test plan.

 **Theory of Operation**
-1 User includes this file - ut.h,
-+ User writes test case in form of functions with this format: void {function name}(void),
-+ In every test case user uses asserts functions which evaluates logical expressions or (not)expected values with real ones and in case of fail records that failure into test case,
-+ Micro-framework then evaluates test case as failed and adjusts statistics for test case and suite that contains this test case,
+- User includes this file - ut.h,
+- User writes test case in form of functions with this format: void {function name}(void),
+- In every test case user uses asserts functions which evaluates logical expressions or (not)expected values with real ones and in case of fail records that failure into test case,
+- Micro-framework then evaluates test case as failed and adjusts statistics for test case and suite that contains this test case,

 **Usage**
 1 At the beginning, user has to create test suite(s),
-+ Then adds test cases to created suites,
-+ Adds suite to test plan,
-+ Previous steps are done for each suite(s) and case(s) as necessary,
-+ Test plan or particular test suite only is then run,
-+ After every suite is tested, it has to be destroyed by appropriate call.
+- Then adds test cases to created suites,
+- Adds suite to test plan,
+- Previous steps are done for each suite(s) and case(s) as necessary,
+- Test plan or particular test suite only is then run,
+- After every suite is tested, it has to be destroyed by appropriate call.

 **Changelog**
 *v2.7*

Home modified by Lukas Kucera

Lukas Kucera — Mon, 10 Feb 2014 10:13:37 -0000

--- v4
+++ v5
@@ -26,6 +26,7 @@

 **Changelog**
 *v2.7*
+- published selftest of the library: two test cases - one with all positive 34 assertions that should pass and one with all 35 negative assertions that should fail
 - fixed non-counting some assertions
 - added support for comparison of wchar_t

Home modified by Lukas Kucera

Lukas Kucera — Mon, 10 Feb 2014 10:10:21 -0000

--- v3
+++ v4
@@ -25,3 +25,18 @@
 + After every suite is tested, it has to be destroyed by appropriate call.

 **Changelog**
+*v2.7*
+- fixed non-counting some assertions
+- added support for comparison of wchar_t
+
+*v2.6.2*
+- fixed warnings and errors that came up from CppCheck
+
+*v2.6.1*
+- fix of documentation bugs only
+
+*v2.6*
+- many bugfixes
+- first public release
+
+*Note: for older changes please check repository log.*

Home modified by Lukas Kucera

Lukas Kucera — Mon, 10 Feb 2014 10:09:06 -0000

--- v2
+++ v3
@@ -1,23 +1,27 @@
-Introduction
+**Introduction**

 This is an unit test micro-framework written in C language. Supports test cases and test suites. This library is capable of single test case statistics, test suite statistics and over-all statistics. Each test case is recorded in human readable format and tester can determine source of test failure. Test suite is a group of test cases that tests same functionalities or belong together by logic.
 Features

-List of features:
-    assert for every basic type (except wide strings and wide chars),
-    statistics and info for each failure,
-    statistics and info for each test case,
-    statistics and info for test suite,
-    dynamic adding and removing of tests into suite and suites into test plan.
+**Features**
+- Assertion for every basic type (except wide strings),
+- Statistics and info for each failure,
+- Statistics and info for each test case,
+- Statistics and info for test suite,
+- Dynamic adding and removing of tests into suite and suites into test plan.

-Usage
-    User includes this file - ut.h,
-    User writes test case in form of functions with this format: void {function name}(void),
-    In every test case user uses asserts functions which evaluates logical expressions or (not)expected values with real ones and in case of fail records that failure into test case,
-    Micro-framework then evaluates test case as failed and adjusts statistics for test case and suite that contains this test case,
-    At the beginning, user has to create test suite(s),
-    Then adds test cases to created suites,
-    Adds suite to test plan,
-    Previous steps are done for each suite(s) and case(s) as necessary,
-    Test plan or particular test suite only is then run,
-    After every suite is tested, it has to be destroyed by appropriate call.
+**Theory of Operation**
+1 User includes this file - ut.h,
++ User writes test case in form of functions with this format: void {function name}(void),
++ In every test case user uses asserts functions which evaluates logical expressions or (not)expected values with real ones and in case of fail records that failure into test case,
++ Micro-framework then evaluates test case as failed and adjusts statistics for test case and suite that contains this test case,
+
+**Usage**
+1 At the beginning, user has to create test suite(s),
++ Then adds test cases to created suites,
++ Adds suite to test plan,
++ Previous steps are done for each suite(s) and case(s) as necessary,
++ Test plan or particular test suite only is then run,
++ After every suite is tested, it has to be destroyed by appropriate call.
+
+**Changelog**

Home modified by Lukas Kucera

Lukas Kucera — Wed, 04 Dec 2013 11:10:10 -0000

--- v1
+++ v2
@@ -1,8 +1,23 @@
-Welcome to your wiki!
+Introduction

-This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].
+This is an unit test micro-framework written in C language. Supports test cases and test suites. This library is capable of single test case statistics, test suite statistics and over-all statistics. Each test case is recorded in human readable format and tester can determine source of test failure. Test suite is a group of test cases that tests same functionalities or belong together by logic.
+Features

-The wiki uses [Markdown](/p/utest/wiki/markdown_syntax/) syntax.
+List of features:
+    assert for every basic type (except wide strings and wide chars),
+    statistics and info for each failure,
+    statistics and info for each test case,
+    statistics and info for test suite,
+    dynamic adding and removing of tests into suite and suites into test plan.

-[[members limit=20]]
-[[download_button]]
+Usage
+    User includes this file - ut.h,
+    User writes test case in form of functions with this format: void {function name}(void),
+    In every test case user uses asserts functions which evaluates logical expressions or (not)expected values with real ones and in case of fail records that failure into test case,
+    Micro-framework then evaluates test case as failed and adjusts statistics for test case and suite that contains this test case,
+    At the beginning, user has to create test suite(s),
+    Then adds test cases to created suites,
+    Adds suite to test plan,
+    Previous steps are done for each suite(s) and case(s) as necessary,
+    Test plan or particular test suite only is then run,
+    After every suite is tested, it has to be destroyed by appropriate call.

Discussion for Home page

Lukas Kucera — Wed, 04 Dec 2013 11:08:47 -0000

ntroduction

This is an unit test micro-framework written in C language. Supports test cases and test suites. This library is capable of single test case statistics, test suite statistics and over-all statistics. Each test case is recorded in human readable format and tester can determine source of test failure. Test suite is a group of test cases that tests same functionalities or belong together by logic.
Features

List of features:

assert for every basic type (except wide strings and wide chars),
statistics and info for each failure,
statistics and info for each test case,
statistics and info for test suite,
dynamic adding and removing of tests into suite and suites into test plan.

Usage

User includes this file - ut.h,
User writes test case in form of functions with this format: void {function name}(void),
In every test case user uses asserts functions which evaluates logical expressions or (not)expected values with real ones and in case of fail records that failure into test case,
Micro-framework then evaluates test case as failed and adjusts statistics for test case and suite that contains this test case,
At the beginning, user has to create test suite(s),
Then adds test cases to created suites,
Adds suite to test plan,
Previous steps are done for each suite(s) and case(s) as necessary,
Test plan or particular test suite only is then run,
After every suite is tested, it has to be destroyed by appropriate call.

Example

Following example shows one test case - foo_test and one test suite - foo suite.
void foo_test( void )
{
// utd macro is necessary to insert for details of failure.
ut.assert.are_equal_i8( 0x7F, 0x7F, utd );
ut.assert.is_true( 0xFFFF > 0xFF, utd );
ut.assert.is_null( null, utd );
}

int main( void )
{
int r = 0;

// Create new suite
ut_suite_t* foo = ut.suite.create( "foo" );

// Suite was allocated
if ( foo != null )
{
// Add test to suite
if ( ut.suite.add( foo, foo_test, "foo test" ) )
{

// Add suite to test plan
if ( ut.add( foo ) )
{
// Run test plan
ut.run();

// Get result from test plan
if ( ut.result() == UT_SUCCESS )
{
// Return 0 as OK
r = 0;
}
else if ( ut.result() == UT_FAIL )
{
r = -2;
}
else if ( ut.result() == UT_UNKNOWN )
{
r = -3;
}
else
{
r = -4;
}

// Remove everything
ut.remove_all();
}
}
// Destroy suite
ut.suite.destroy( foo );
foo = null;
}
return r;
}

Home modified by Lukas Kucera

Lukas Kucera — Wed, 04 Dec 2013 10:55:38 -0000

Welcome to your wiki!

This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].

The wiki uses Markdown syntax.

Project Members:

Lukas Kucera (admin)