cutter-users-en — A ML for Cutter users in English

[cutter-users-en] [ANN] Cutter 1.2.7

[Kentaro H. <ha...@cl...>]

Hi,

Cutter 1.2.7 has been released:
  http://cutter.osdn.jp/
  http://cutter.osdn.jp/reference/news.html#news.release-1-2-7

Install:
  http://cutter.osdn.net/reference/install.html

= Topics

This is a maintenance release of Cutter.
In this release, some support for Ubuntu (EOL) release was dropped, and
added support for Ubuntu 18.04/19.04.

=== Cutter

==== Improvements

  * [deb][ubuntu] Dropped support for Ubuntu 14.04/17.04/17.10/18.10.
  * [gstreamer] Restricted GStreamer 1.14 or later as non supported version explicitly.
  * [deb][ubuntu] Added support for Ubuntu 18.04/19.04
  * [homebrew] Added support for custom Homebrew path. In the previous versions,
    /usr/local/share/aclocal was expected as Homebrew's aclocal path.
  * [travis] Added macOS as CI target.
  * [doc][tutorial] Added a description about OS that need DYLD_LIBRARY_PATH
    [GitHub#41] [Patch by Douglas Lovell]
  * [doc][tutorial] Updated an explanation about loading shared library.

=== cppcutter

==== Fixes

  * Fixed returning invalid address because of wrong c_str() usage in Message class.
    [GitHub#39][Reported by dcb314]

=== Thanks

  * dcb314
  * Douglas Lovell

-- 
Kentaro Hayashi <ha...@cl...>

[cutter-users-en] [ANN] Cutter 1.2.5

[HAYASHI K. <ha...@cl...>]

Hi,

Cutter 1.2.5 had been released:
  http://cutter.sourceforge.net/
  http://cutter.sourceforge.net/reference/news.html#news.release-1-2-5

Install:
  http://cutter.sourceforge.net/reference/install.html

In this release, there is a bugfix about GCutter.
Please upgrade Cutter if you use Cutter with GLib support.

= Topics

== Update supported release

In this release, we began to support Ubuntu 15.04 and CentOS 7.
On the other hand, Ubuntu 13.10 was dropped.

Note that there is no package updates because Cutter use SourceForge
infrastructure to provide package. The service is still offline.
We will provide Cutter packages after that service is restored.

== Supported GStreamer again

In this release, Cutter gstreamer plugin is ported for GStreamer 1.0.
You can run Cutter test with gst-launch-1.0 command.

=== Cutter

==== Improvements

  * [deb][ubuntu] Changed to release packages via Launchpad PPA. [GitHub #13]
  * Supported LCOV 1.11.
  * [doc][ubuntu] Updated install document how to install via Launchpad PPA.
  * [doc][tutorial] Added mising slash in LD_LIBRARY_PATH. [GitHub #14]
    [Patch by Masafumi Yokoyama]
  * [doc] Added Project Hatohol which is operational integrated management software
    as a Cutter user. [GitHub #15] [Patch by Noriki Nakamura]
  * [doc] Added missing --location option in travis recipe. [GitHub#13] [Reported by Kiyoshi Ikehara]
  * [OS X] Supported terminal-notifier notification. [GitHub #17] [Patch by Hiroshi Hatake]
  * Supported gdk-pixbuf 2.31.0 or later. The result of inspect is a bit changed because
    gdk-pixbuf 2.31.0 introduces pixel-bytes property. [GitHub #19] [Reported by mtasaka]
  * Ported Cutter gstreamer plugin for GStreamer 1.0.
  * [deb][ubuntu] Dropped Ubuntu 13.10. (Saucy Salamander)
  * [deb][ubuntu] Supported Ubuntu 15.04. (Vivid Vervet)
  * [rpm][centos] Supported CentOS 7.

=== GCutter

==== Fixes

* Fixed a bug that monitoring source is unexpectedly removed twice.
  As a result, there was a possibility that reissued source ID is also removed.

=== Thanks

  * Masafumi Yokoyama
  * Noriki Nakamura
  * Kiyoshi Ikehara
  * Hiroshi Hatake
  * mtasaka

-- 
HAYASHI Kentaro <ha...@cl...>

[cutter-users-en] [ANN] Cutter 1.2.4

[HAYASHI K. <ha...@cl...>]

Hi,

Cutter 1.2.4 had been released:
  http://cutter.sourceforge.net/
  http://cutter.sourceforge.net/reference/news.html#news.release-1-2-4

Install:
  http://cutter.sourceforge.net/reference/install.html

The MacPorts package for Cutter is imported into the
official repository. Please use the official repository.
The Fedora package for Cutter is also imported into the
official repository. Please use the official one.
You don't need to register yum repository anymore on Fedora.

Highlight
=========

Update supported release
------------------------

In this release, we began to support Ubuntu 14.04 which is released
at Apr 17, 2014. On the other hand, Ubuntu 12.10 (Quantal Quetzal) was dropped.

Supported release:

* Ubuntu 14.04 (Trusty Tahr)

Dropped release:

* Ubuntu 12.10 (Quantal Quetzal)

Note that there are some bugfixes which is related to exception handling
and crash bug, please update it.

Here is a summary of changes:

=== Cutter

==== Improvements

  * Supported Ubuntu 14.04 (Trusty Tahr).

==== Changes

  * Dropped Ubuntu 12.10 (Quantal Quetzal) support.

==== Fixes

  * Added -fexceptions to use C code with C++ exceptions. [Reported by OBATA Akio]
  * Fixed a problem that bash isn't found when executing make check on FreeBSD.
  * Fixed a crash bug because of double free allocated memory. [GitHub #12] [Reported by Kazuhiro Yamato]

=== Thanks

  * OBATA Akio
  * Kazuhiro Yamato

-- 
HAYASHI Kentaro <ha...@cl...>

[cutter-users-en] [ANN] Cutter 1.2.3

[HAYASHI K. <ha...@cl...>]

Hi,

Cutter 1.2.3 had been released:
  http://cutter.sourceforge.net/
  http://cutter.sourceforge.net/reference/news.html#news.release-1-2-3

Install:
  http://cutter.sourceforge.net/reference/install.html

The MacPorts package for Cutter is imported into the
official repository. Please use the official repository.
The Fedora package for Cutter is also imported into the
official repository. Please use the official one.
You don't need to register yum repository anymore on Fedora.

Highlight
=========

Update supported release
------------------------

Long time has passed since Cutter 1.2.2 had released, so
supported release has been also updated now!

Dropped release:

* Debian 6.0 (squeeze)
* Ubuntu 10.04 (Lucid Lynx)
* Ubuntu 11.04 (Natty Narwhal)
* Ubuntu 11.10 (Oneiric Ocelot)
* Ubuntu 13.04 (Raring Ringtail)
* Fedora 17

Supported release:

* Debian 8.0 (jessie)
* Ubuntu 13.10 (Saucy Salamander)
* Fedora 20

Here is a summary of changes:

== [release-1-2-3] 1.2.3: 2014-02-09

=== Cutter

==== Improvements

  * [doc] Removed a needless period from installation link. [GitHub #6] [Patch by Masafumi Yokoyama]
  * Supported lcov 1.10. [cutter-users-ja:92] [Reported by Siganai SE]
  * [doc] Updated download URL on SF.net. [cutter-users-ja:91] [Reported by Siganai SE]
  * [doc] Updated XML report format. [cutter-users-ja:91] [Reported by Siganai SE]
  * Added more trace logs for loader. It helps you to investigate the case when no tests are loaded.
  * [doc] Updated Cygwin's setup.exe URL.
  * Added --log-level option. The value of default log level is "critical|error|warning|message".

==== Fixes

  * [loader] Fixed a bug that ELF loader can't collect symbol because of wrong comparison.
  * Fixed memory leaks on loading all modules.
  * Fixed a warning from GCC 4.8.1 on Ubuntu 13.10 [GitHub #9] [Reported by Kazuhiro Yamato]

=== CppCutter

==== Improvements

  * Supported cppcut_assert_equal(const type_info &, const type_info &) [GitHub #4] [Patch by Kazuhiro Yamato]
  * Supported to catch unhandled C++ exception in test case. 
    This change avoids to crash when unexpected exception is thrown. [GitHub #8] [Suggested by Kazuhiro Yamato] [Patch by Kazuhiro Yamato]
  * Supported to call destructors of objects on a stack even when an assertion is failed. [GitHub #10] [Patch by Kazuhiro Yamato]

==== Fixes

  * [Clang] Fixed a compile error which is caused by missing std::type_info forward declaration.
  * Fixed an invalid memory access when an exception is thrown in cutter's assertion function. [GitHub #11] [Patch by Kazuhiro Yamato]

=== GCutter

==== Fixes

  * [doc] Fixed a signal name typo about gcut-egg example.

=== Thanks

  * Kazuhiro Yamato
  * Masafumi Yokoyama
  * Siganai SE


-- 
Clear Code,. Inc
HAYASHI Kentaro <ha...@cl...>
3-27-12, Hongo, Bunkyo-ku, Tokyo, 113-0033, Japan
TEL:03-6231-7270 FAX:03-6231-7271

Re: [cutter-users-en] cutter links with libselinux

[Kouhei S. <ko...@co...>]

Hi,

In <CAH...@ma...>
  "[cutter-users-en] cutter links with libselinux" on Fri, 3 Jan 2014 16:11:07 -0500,
  Chris Bare <chr...@gm...> wrote:

> I'm trying to run cutter on an embedded arm system and developing from a
> debian arm system running in qemu.
> Most programs I build in the vm work fine on the embedded target, but
> cutter is linking with libselinux.so.1 which is not available on my target.
> Is there any way to stop it from linking with this?
> I've looked at the configure and Makefiles, but I don't even see
> libselinux, so it must be a dependency from some other library, but I can't
> tell which.

I tried "objdump -p .../XXX.so | grep NEED" to find the
libselinux.so dependency. It seems that libgio-2.0.so
depends on libselinux.so:

  % objdump -p /usr/lib/x86_64-linux-gnu/libgio-2.0.so | grep NEED | grep selinux
    NEEDED               libselinux.so.1

I looked into GLib's configure and found "--disable-selinux"
option:

  % ./configure --help | grep selinux
    --disable-selinux       build without selinux support

Could you try building GLib with "--disable-selinux" option
and use the built GLib to build Cutter?


Thanks,
--
kou

[cutter-users-en] cutter links with libselinux

[Chris B. <chr...@gm...>]

I'm trying to run cutter on an embedded arm system and developing from a
debian arm system running in qemu.
Most programs I build in the vm work fine on the embedded target, but
cutter is linking with libselinux.so.1 which is not available on my target.
Is there any way to stop it from linking with this?
I've looked at the configure and Makefiles, but I don't even see
libselinux, so it must be a dependency from some other library, but I can't
tell which.

-- 
Chris Bare

Re: [cutter-users-en] Is there a way to loop over tests with different settings?

[Kouhei S. <ko...@cl...>]

Hi,

In <CAH...@ma...>
  "[cutter-users-en] Is there a way to loop over tests with different settings?" on Wed, 4 Dec 2013 15:42:31 -0500,
  Chris Bare <chr...@gm...> wrote:

> I am writing test cases for a serial protocol library. I would like to be
> able to run all the tests at various different baud rates. My only idea so
> far is to create a .c file for each baud rate and #include the actual test
> implementation in each file. Is there a better way?

How about the following idea?

= Pass baud rate by environment variable and run Cutter N times

Create the following shell script

run-test.sh:
--
#!/bin/sh

set -e

baud_rates="1024 2048 4096"
for baud_rate in ${baud_rates}; do
    BAUD_RATE=${baud_rate} cutter ...
done
--

*.c:
--
#include <stdlib.h>

static int baud_rate;

void
cut_setup(void)
{
  baud_rate = atoi(getenv("BAUD_RATE"));
}

void
test_XXX(void)
{
  assert_equal(YYY, your_function(baud_rate));
}
--


Thanks,
--
kou

[cutter-users-en] Is there a way to loop over tests with different settings?

[Chris B. <chr...@gm...>]

I am writing test cases for a serial protocol library. I would like to be
able to run all the tests at various different baud rates. My only idea so
far is to create a .c file for each baud rate and #include the actual test
implementation in each file. Is there a better way?

-- 
Chris Bare

[cutter-users-en] [ANN] Cutter 1.2.2

[HAYASHI K. <ha...@cl...>]

Hi,

Cutter 1.2.2 had been released:
  http://cutter.sourceforge.net/
  http://cutter.sourceforge.net/reference/news.html#news.release-1-2-2

Install:
  http://cutter.sourceforge.net/reference/install.html

The MacPorts package for Cutter is imported into the
official repository. Please use the official repository.

Highlight
=========

Supported Ubuntu 12.10 (Quantal Quetzal)
----------------------------------------

Ubuntu 12.10 (Quantal Quetzal) had been released.

This release provides new version of Cutter.

Fixed a bug that wrong data function is searched
------------------------------------------------

Cutter supports convinience test data API.
If you use test data API, you need to define data function.

  http://cutter.sourceforge.net/reference/cutter-Convenience-test-data-API.html#gcut-add-datum

There was a bug that wrong data function is searched.
This release fixes the bug above.

Upgrade Cutter if you use CppCutter.

Changes
=======

Here is a summary of changes:

== [release-1-2-2] 1.2.2: 2012-10-29

We began to support Ubuntu 12.10 (Quantal Quetzal).
There are some improvements and fixed bugs.

=== Cutter

==== Improvements

  * [doc] Added release procedure documentation.
  * [doc] Improved documentation about Travis-CI configuraion.
  * Supported Ubuntu 12.10 (Quantal Quetzal).

==== Fixes

  * [sample][GTK+] Fixed missing GLIB_LIBS that has flags for GModule.
    [Reported by Hiroshi Umemoto]

=== CppCutter

==== Fixes

  * Fixed a bug that wrong data function is searched.

=== GCutter

==== Fixes

  * [sample] Fixed missing function call in sample code.

=== Thanks

  * Hiroshi Umemoto


-- 
HAYASHI Kentaro <ha...@cl...>

[cutter-users-en] [ANN] Cutter 1.2.1

[HAYASHI K. <ha...@cl...>]

Hi,

Cutter 1.2.1 had been released:
  http://cutter.sourceforge.net/
  http://cutter.sourceforge.net/reference/news.html#news.release-1-2-1

Install:
  http://cutter.sourceforge.net/reference/install.html

The MacPorts package for Cutter is imported into the
official repository. Please use the official repository.

Highlight
=========

Supported Ubuntu Precise/Fedora 17
----------------------------------

Ubuntu Precise and Fedora 17 had been released.
Since then, there is no new release of Cutter.

This release provides new version of Cutter.
And more, it supports Ubuntu Precise and Fedora 17 packages.

The package signing key is changed
----------------------------------

The package signing key is changed since this release.
Here is the new signing key:

  % gpg --list-keys --fingerprint F07C74AC
  pub   1024D/F07C74AC 2012-08-07
        Key fingerprint = C3EB A34F 9495 FCF5 9FB3  65E7 1879 0411 F07C 74AC
  uid                  Cutter Key (Cutter Official Signing Key) <cut...@li...>

If you have already installed Cutter packages, you need to
import the new key by the followings:

Debian/Ubuntu:

  % sudo apt-get update
  % sudo apt-get -V -y --allow-unauthenticated install cutter-keyring

CentOS/Fedora:

  % sudo yum makecache
  % sudo yum install --nogpgcheck -y cutter-release

Travis CI integration script
----------------------------

The Cutter project uses Travis CI.
  http://travis-ci.org/#!/clear-code/cutter

This release provides the easy setup script to support Travis CI with
Cutter on your projects.

Here is the example how to use this setup script in .travis.yml:
(see: https://github.com/groonga/groonga/blob/master/.travis.yml about detail)

install:
  - curl https://raw.github.com/clear-code/cutter/master/data/travis/setup.sh | sh

If you want to know how to use Cutter on Travis CI integration in detail,
see Travis CI integration page as following:
  http://cutter.sourceforge.net/reference/travis-ci-integration.html

Changes
=======

Here is a summary of changes:

== [release-1-2-1] 1.2.1: 2012-08-15

We began to support Ubuntu Precise/Fedora 17.
There are some UI related improvements and fixed bugs.

=== Cutter

==== Improvements

  * [UI][GTK+] Supported GTK+ < 2.22 for Debian GNU/Linux squeeze.
  * [UI][console] Supported growlnotify.exe for windows.
  * [UI][GTK+] Added menubar.
  * [UI][GTK+] Improved to log an error message for showing URI.
  * [UI][GTK+] Supported --with-fallback-browser option to customize 
    fallback browser.
  * Improved to use "()" as a part of function of backtrace.
  * [UI][console] Added more color acceptable TERMs 
    (xterm-256color, screen-256color, screen-color)
  * Added Travis CI integration.
  * Supported backtrace on SIGBUS [Patch by Kiwamu Okabe]
  * Added Homebrew related paths by default on Mac OS X.

==== Changes

  * [doc][Mac OS X] Recommended to use the official MacPorts repository.
    [Suggested by Hiroshi Umemoto]
  * Supported Fedora 17.
  * Dropped Fedora 16 support.
  * Supported Ubuntu Precise.

==== Fixes

  * [Clang] Fixed not to add extra "()" for function name of backtrace.
  * Fixed compilation failure on MinGW.

=== CppCutter

==== Improvements

  * Supported nested namespace test case built by g++

=== Thanks

  * Hiroshi Umemoto 
  * Kiwamu Okabe

-- 
HAYASHI Kentaro <ha...@cl...>

Re: [cutter-users-en] cutter on Fedora 17

[HAYASHI K. <ha...@cl...>]

Thank you for using Cutter!

We can't announce the release schedule of Cutter which supports Fedora 
17 yet.
But we want to support Fedora 17 as soon as possible.

So, please look forward to new release of Cutter!

[cutter-users-en] cutter on Fedora 17

[le c. <yve...@es...>]

Hello,

I began to use cutter on ubuntu a few month ago and then I migrate 
recently to the last fedora release
I would like to know if it's planned to have the possiblity to install 
cutter with yum on fedora 17 ?
Thanks,
Yves Le Chevalier

Re: [cutter-users-en] Memory debugging with Valgrind

[Kouhei S. <ko...@co...>]

Hi,

In <201...@lo...>
  "[cutter-users-en] Memory debugging with Valgrind" on Sat, 7 Jan 2012 00:13:40 +0000,
  "Eric P. Mangold" <er...@te...> wrote:

> I just started using Cutter today, and mostly I'm very impressed with
> it. I've ported my test suite from another unit-test framework - and it
> is running correctly.

Great!

> The problem is when I try to run my test suite under Valgrind in order
> to detect any memory leaks and other problems that my test-suite may
> expose.
> 
> There are well over 300 reported errors internal to the cutter library,
> presumably becase it's not cleaning up dynamic memory before quitting
> the process... The other unit-test framework I was using made this
> use-case easy, as my test-suite was compiled to an executable (as
> opposed to a library), and it could be run under valgrind without issue.

It's caused by GLib. GLib is a generic utility
library. Cutter is based on GLib.

GLib implements object system as GObject. GObject exports
initialize function but doesn't export finalize function. So
some allocated memories aren't cleaned. Valgrind says they
are "possibly lost" or "still reachable".

> Any ideas how I might solve this, or develop a workaround are
> appreciated.

I don't have a good idea but have some hints:

  * You should add "--keep-opening-modules" option to
    cutter. (See also test/run-test.sh in Cutter source tar.gz.)
    If you don't add the option, Valgrind don't report any
    errors of your program because Cutter unload test
    program, a shared library. 

  * You can determine whether you can ignore an error report
    by backtrace. If a backtrace includes your project's
    path, your project may have a memory leak. Otherwise,
    the error report doesn't have a relationship with your
    project.

    For example, Cutter includes a sample project that uses
    Cutter in $PREFIX/share/cutter/stack. You can create a
    program that has a memory leak with the following changes.

    before (test/test-stack.c):
      void
      teardown (void)
      {
          if (stack)
              stack_free(stack);
      }

    after (test/test-stack.c):
      void
      teardown (void)
      {
      /*
          if (stack)
              stack_free(stack);
      */
      }

    With changed pogram, you will get the following Valgrind output:

      ==30825== 4 bytes in 1 blocks are indirectly lost in loss record 8 of 1,101
      ==30825==    at 0x4C2779D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
      ==30825==    by 0x4C27927: realloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
      ==30825==    by 0x7E04793: stack_realloc (stack.c:50)
      ==30825==    by 0x7E0485A: stack_push (stack.c:66)
      ==30825==    by 0x7C01FE0: test_push (test-stack.c:35)
      ==30825==    by 0x4E807DE: invoke (cut-test.c:422)
      ==30825==    by 0x4E80A64: run (cut-test.c:471)
      ==30825==    by 0x4E80BC4: cut_test_run (cut-test.c:515)
      ==30825==    by 0x4E73375: run_test (cut-test-case.c:416)
      ==30825==    by 0x4E73500: run (cut-test-case.c:451)
      ==30825==    by 0x4E7395E: run_tests (cut-test-case.c:561)
      ==30825==    by 0x4E73D00: cut_test_case_run_tests (cut-test-case.c:632)

    The output include "stack.c:50" and
    "stack.c:66". cut-*.c are Cutter library programs but
    stack.c is our program. If a backtrace includes our
    program file, it will be our problem not Cutter.
    
  * You may determine whether your project has a problem or
    not by. If there are "definitely lost" or "indirectly
    lost" blocks, your project may have a problem.

    For example, here is an output by the above program that
    has a memory leak:

      ==30813== LEAK SUMMARY:
      ==30813==    definitely lost: 32 bytes in 2 blocks
      ==30813==    indirectly lost: 4 bytes in 1 blocks
      ==30813==      possibly lost: 34,305 bytes in 162 blocks
      ==30813==    still reachable: 99,593 bytes in 947 blocks
      ==30813==         suppressed: 0 bytes in 0 blocks

    Here is an output by the original stack program:

      ==31368== LEAK SUMMARY:
      ==31368==    definitely lost: 0 bytes in 0 blocks
      ==31368==    indirectly lost: 0 bytes in 0 blocks
      ==31368==      possibly lost: 34,305 bytes in 162 blocks
      ==31368==    still reachable: 99,577 bytes in 946 blocks
      ==31368==         suppressed: 0 bytes in 0 blocks

    Cutter will be reported "possibly lost" and "still
    reachable" but not reported "definitely lost" and
    "indirectly lost".


I hope that they help you.


Thanks,
--
kou

[cutter-users-en] Memory debugging with Valgrind

[Eric P. M. <er...@te...>]

Hi!

I just started using Cutter today, and mostly I'm very impressed with
it. I've ported my test suite from another unit-test framework - and it
is running correctly.

The problem is when I try to run my test suite under Valgrind in order
to detect any memory leaks and other problems that my test-suite may
expose.

There are well over 300 reported errors internal to the cutter library,
presumably becase it's not cleaning up dynamic memory before quitting
the process... The other unit-test framework I was using made this
use-case easy, as my test-suite was compiled to an executable (as
opposed to a library), and it could be run under valgrind without issue.

Any ideas how I might solve this, or develop a workaround are
appreciated.

--
Thanks,
Eric Mangold

[cutter-users-en] [ANN] Cutter 1.2.0

[Kouhei S. <ko...@cl...>]

Hi,

Happy new year!

Cutter 1.2.0 had been released:
  http://cutter.sourceforge.net/
  http://cutter.sourceforge.net/reference/news.html#news.release-1-2-0

Install:
  http://cutter.sourceforge.net/reference/install.html

The MacPorts package for Cutter is imported into the
official repository. Please use the official repository.

Highlight
=========

UI changes
----------

The GTK+ UI fully support all test types now.

The console UI changes message output on test failure, error
and so on.

Old:

  F....F.

  1) Failure: test_build_fixture_path
  <cut_build_path(cut_take_string(g_get_current_dir()), cuttest_get_base_dir(), "a", "b", "c", NULL) == cut_build_fixture_path("c", "d", NULL)>
  expected: <"/home/kou/work/c/cutter/test/a/b/c">
    actual: <"/home/kou/work/c/cutter/test/a/b/c/d">

  diff:
  ? "/home/kou/work/c/cutter/test/a/b/c/d"

  test/cutter/test-cut-test-utils.c:124: test_build_fixture_path(): cut_assert_equal_string(cut_test_context_take_string(cut_test_context_current_peek(), (cut_utils_build_path(cut_test_context_take_string(cut_test_context_current_peek(), (g_get_current_dir())), cuttest_get_base_dir(), "a", "b", "c", ((void *)0)))), cut_test_context_build_fixture_path( cut_test_context_current_peek(), "c", "d", ((void *)0)), )

  2) Failure: test_build_path
  <expected == cut_build_path("a", "b", "c", "d", NULL)>
  expected: <"a/b/c">
    actual: <"a/b/c/d">

  diff:
  ? "a/b/c/d"

  test/cutter/test-cut-test-utils.c:103: test_build_path(): cut_assert_equal_string(expected, cut_test_context_take_string(cut_test_context_current_peek(), (cut_utils_build_path("a", "b", "c", "d", ((void *)0)))), )

  Finished in 0.012739 seconds (total: 0.002901 seconds)

  7 test(s), 14 assertion(s), 2 failure(s), 0 error(s), 0 pending(s), 0 omission(s), 0 notification(s)
  71.4286% passed

The above shows all messages after all tests are finished.

New:

  F
  ===============================================================================
  Failure: test_build_fixture_path
  <cut_build_path(cut_take_string(g_get_current_dir()), cuttest_get_base_dir(), "a", "b", "c", NULL) == cut_build_fixture_path("c", "d", NULL)>
  expected: <"/home/kou/work/c/cutter/test/a/b/c">
    actual: <"/home/kou/work/c/cutter/test/a/b/c/d">

  diff:
  ? "/home/kou/work/c/cutter/test/a/b/c/d"

  test/cutter/test-cut-test-utils.c:124: test_build_fixture_path(): cut_assert_equal_string(cut_test_context_take_string(cut_test_context_current_peek(), (cut_utils_build_path(cut_test_context_take_string(cut_test_context_current_peek(), (g_get_current_dir())), cuttest_get_base_dir(), "a", "b", "c", ((void *)0)))), cut_test_context_build_fixture_path( cut_test_context_current_peek(), "c", "d", ((void *)0)), )
  ===============================================================================
  ....F
  ===============================================================================
  Failure: test_build_path
  <expected == cut_build_path("a", "b", "c", "d", NULL)>
  expected: <"a/b/c">
    actual: <"a/b/c/d">

  diff:
  ? "a/b/c/d"

  test/cutter/test-cut-test-utils.c:103: test_build_path(): cut_assert_equal_string(expected, cut_test_context_take_string(cut_test_context_current_peek(), (cut_utils_build_path("a", "b", "c", "d", ((void *)0)))), )
  ===============================================================================
  .

  Finished in 0.011594 seconds (total: 0.004129 seconds)

  7 test(s), 14 assertion(s), 2 failure(s), 0 error(s), 0 pending(s), 0 omission(s), 0 notification(s)
  71.4286% passed

The above shows a message immediately.

By this change, you can debug immediately.

C++ support is improved
-----------------------

This release adds some assertions for
C++. (e.g. cppcut_assert_not_equal())

Changes
=======

Here is a summary of changes:

== [release-1-2-0] 1.2.0: 2011-12-31

We improved C++ support and test runner interface.

=== Cutter

==== Improvements

  * [UI][console] Changed to show messages on failure, error
    and so on immediately. You need to use
    --show-detail-immediately=no command line option
    to show messages on end of test like earlier versions.
  * [UI][GTK+] Supported iterated test.
  * [UI][GTK+] Supported re-run test.
  * [UI][GTK+] Unified cancel button and re-run button.

==== Changes

  * Enabled deprecated GLib API. You need to use
    --disable-deprecated-glib-api configure option to
    disable deprecated GLib API.
  * Supported Fedora 16.
  * Dropped Fedora 15 support.

=== CppCutter

==== Improvements

  * Added more supported types by cppcut_assert_equal().
  * Added cppcut_assert_not_equal().
  * Added cppcut_assert_null().
  * Added cppcut_assert_not_null().
  * Added cppcut_assert_operator().

Thanks,
--
kou

[cutter-users-en] [ANN] Cutter 1.1.9

[Kouhei S. <ko...@cl...>]

Hi,

Cutter 1.1.9 had been released:
  http://cutter.sourceforge.net/
  http://cutter.sourceforge.net/reference/news.html#news.release-1-1-9

Install:
  http://cutter.sourceforge.net/reference/install.html

Packages for Ubuntu Oneiric, Ubuntu Natty and CentOS 6 are
added.

We had been moved the repository to GitHub from SF.net:
  https://github.com/clear-code/cutter/

Here is a summary of changes:

== [release-1-1-9] 1.1.9: 2011-10-22

We move the repository to GitHub from SF.net.

=== Cutter

==== Changes

  * Added Ubuntu Oneiric Ocelot support.
  * Added CentOS 6 support.

==== Fixes

  * Fixed as success test count with thread. [SF.net #3383253]
    [Reported by Romain Tartière]

=== Thanks

  * Romain Tartière


Thanks,
--
kou

Re: [cutter-users-en] Raw graphics testing

[Kouhei S. <ko...@cl...>]

Hi,

In <CAK...@ma...>
  "[cutter-users-en] Raw graphics testing" on Wed, 19 Oct 2011 09:10:46 +0200,
  Iñigo Martínez <ini...@gm...> wrote:

> I recently started using cutter for testing the robustness of my code
> between changes and it has been very useful, thank you.

Thanks. :-)

> Should I have raw graphics file stored in the disk, load and compare
> the entire memory space of my written data agains the loaded file ?
> 
> What is done in these cases ?

Cutter has image diff support by gdk-pixbuf:
  http://cutter.sourceforge.net/reference/cutter-Assertions-with-gdk-pixbuf-support.html

Here are sample output for image diff:
  http://cutter.sourceforge.net/reference/news.html#idp10123760


gdk-pixbuf API reference:
  http://developer.gnome.org/gdk-pixbuf/stable/


Thanks,
--
kou

[cutter-users-en] Raw graphics testing

[Iñigo M. <ini...@gm...>]

Hi:

I recently started using cutter for testing the robustness of my code
between changes and it has been very useful, thank you.

I have been working on a program that uses SDL and draws graphics
based on some data. I can test data by comparing the data extracted
from there, but I'm not sure about what should be the best way to test
my drawing code.

Should I have raw graphics file stored in the disk, load and compare
the entire memory space of my written data agains the loaded file ?

What is done in these cases ?

Best regards,

[cutter-users-en] [ANN] Cutter 1.1.8

[Kouhei S. <ko...@cl...>]

Hi,

Cutter 1.1.8 had been released a week ago:
  http://cutter.sourceforge.net/
  http://cutter.sourceforge.net/reference/news.html#news.release-1-1-8

Install:
  http://cutter.sourceforge.net/reference/install.html

I'm sorry for late announcement.


We may move the repository to GitHub from SF.net.


Here is a summary of changes:

== [release-1-1-8] 1.1.8: 2011-07-31

=== Cutter

==== Improvements

  * Supported notify-send availability detection.
  * Added --mode=play option that plays test result from
    test log.
  * Updated documents for Solaris 10.
  * Supported assertion failures in other thread. Bug #3341429
    [Reported by Romain Tartière]
  * Fixed a problem that GTK+ test runner doesn't show test
    result quickly.
    [Patch by Tobias Gruetzmacher]

==== Changes

  * Added Debian GNU/Linux wheezy support.
  * Removed Ubuntu Maverick Meerkat support.
  * Added Ubuntu Natty Narwhal support.
  * Removed Fedora 14 support.
  * Added Fedora 15 support.

=== cut-diff

==== Improvements

  * Made --label option optional.

=== Thanks

  * Romain Tartière
  * Tobias Gruetzmacher

Thanks,
--
kou

Re: [cutter-users-en] Snappier GTK GUI?

[Kouhei S. <ko...@co...>]

Hi,

In <201...@23...>
  "[cutter-users-en] Snappier GTK GUI?" on Sun, 31 Jul 2011 13:38:20 +0200,
  Tobias Gruetzmacher <tob...@23...> wrote:

> I recently started using cutter and I really like it!

Thanks! :-)

> I was annyoyed by the GUI sitting around doing nothing while the
> testsuite was running. I tried to process events in cb_start_test,
> cb_complete_test and/or cb_pass_assertion, but those all trigger some
> kind of endless loop in
> test-soupcut-assertions/test_message_equal_content_type. So until
> someone figures out what goes wrong there, I propose the attached patch
> to at least update the UI after every test case.

I've applied your patch.

But we should use more better solution as you said... It
seems that CutStreamReader has a problem...


Thanks,
--
kou

[cutter-users-en] Snappier GTK GUI?

[Tobias G. <tob...@23...>]

Hi,

I recently started using cutter and I really like it!

I was annyoyed by the GUI sitting around doing nothing while the
testsuite was running. I tried to process events in cb_start_test,
cb_complete_test and/or cb_pass_assertion, but those all trigger some
kind of endless loop in
test-soupcut-assertions/test_message_equal_content_type. So until
someone figures out what goes wrong there, I propose the attached patch
to at least update the UI after every test case.

Greetings, Tobi

-- 
My blog: http://blog.23.gs/
GPG-Key 0xE2BEA341 - signed/encrypted mail preferred
http://www.fli4l.de/ - ISDN- & DSL-Router on one disk!
Registered FLI4L-User #00000003

Re: [cutter-users-en] Best practice for using cutter with multithreaded programs

[Kouhei S. <ko...@cl...>]

Hi,

In <201...@bl...>
  "Re: [cutter-users-en] Best practice for using cutter with multithreaded programs" on Sat, 28 May 2011 11:37:31 +0200,
  Romain Tartière <ro...@bl...> wrote:

> On Sat, May 28, 2011 at 10:12:47AM +0900, Kouhei Sutou wrote:
>> Do you know cut_get_current_test_context() and
>> cut_set_current_test_context()?
>>   http://cutter.sourceforge.net/reference/cutter-Cutter.html#cut-get-current-test-context
>> 
>> It seems that they are what you want. :-)
> 
> Yay!  It's precisely what I missed.  I changed the code using this and
> it rocks.

It's good news. ;-)


Thanks,
--
kou

Re: [cutter-users-en] Best practice for using cutter with multithreaded programs

[Romain T. <ro...@bl...>]

On Sat, May 28, 2011 at 10:12:47AM +0900, Kouhei Sutou wrote:
> Do you know cut_get_current_test_context() and
> cut_set_current_test_context()?
>   http://cutter.sourceforge.net/reference/cutter-Cutter.html#cut-get-current-test-context
> 
> It seems that they are what you want. :-)

Yay!  It's precisely what I missed.  I changed the code using this and
it rocks.

Thanks!

Romain

-- 
Romain Tartière <ro...@bl...>        http://romain.blogreen.org/
pgp: 8234 9A78 E7C0 B807 0B59  80FF BA4D 1D95 5112 336F (ID: 0x5112336F)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)

Re: [cutter-users-en] Best practice for using cutter with multithreaded programs

[Kouhei S. <ko...@cl...>]

Hi,

In <201...@bl...>
  "[cutter-users-en] Best practice for using cutter with multithreaded programs" on Fri, 27 May 2011 22:03:23 +0200,
  Romain Tartière <ro...@bl...> wrote:

> I am willing to perform some unit test on multi-threaded software I am
> writing and of course am using cutter to do so (what else?).

Thanks! ;)

> Basically, the code I want to test is run by a threads which seats
> between the application main thread (the cutter unit test) and some
> custom user thread (setup from the cutter unit test for the test
> purpose):
> 
> 
> The idea:
> ------------------8<-------------------------
> #include <cutter.h>
> 
> void *
> my_thread (void *arg) {
>     ... read messages ...
>     ... then do something ...
>     ... and we want to check that we got the good thing ...
> 
>     // You can't cut_* from the thread.  It would fail with:
>     // cut_test_context_push_backtrace: assertion `context != NULL'
>     // failed
> }
> 
> void
> test_complex_code (void)
> {
>     ComplexObject *o = complex_object_new ();
>     complex_object_add_service (o, 1, my_thread);
> 
>     complex_object_send_data (o, 1, ... write message ...);
> 
>     // cut_assert_my_thread_received_message
>     // cut_assert_my_thread_received_correct_data
> }
> ------------------8<-------------------------
> 
> Of course I can do thread synchronization from the unit test but the
> idea is that tests should be simple...  So I am wondering if I am
> missing some useful existing function suitable for my case or if I
> really need to do somewhat complex to perform my tests (or should I
> really look for another tool to perform (simple) integration tests... if
> so, recommendations for such a tool are welcomed).

Do you know cut_get_current_test_context() and
cut_set_current_test_context()?
  http://cutter.sourceforge.net/reference/cutter-Cutter.html#cut-get-current-test-context

It seems that they are what you want. :-)


Thanks,
--
kou

[cutter-users-en] Best practice for using cutter with multithreaded programs

[Romain T. <ro...@bl...>]

Hello!

I am willing to perform some unit test on multi-threaded software I am
writing and of course am using cutter to do so (what else?).

Basically, the code I want to test is run by a threads which seats
between the application main thread (the cutter unit test) and some
custom user thread (setup from the cutter unit test for the test
purpose):


The idea:
------------------8<-------------------------
#include <cutter.h>

void *
my_thread (void *arg) {
    ... read messages ...
    ... then do something ...
    ... and we want to check that we got the good thing ...

    // You can't cut_* from the thread.  It would fail with:
    // cut_test_context_push_backtrace: assertion `context != NULL'
    // failed
}

void
test_complex_code (void)
{
    ComplexObject *o = complex_object_new ();
    complex_object_add_service (o, 1, my_thread);

    complex_object_send_data (o, 1, ... write message ...);

    // cut_assert_my_thread_received_message
    // cut_assert_my_thread_received_correct_data
}
------------------8<-------------------------

Of course I can do thread synchronization from the unit test but the
idea is that tests should be simple...  So I am wondering if I am
missing some useful existing function suitable for my case or if I
really need to do somewhat complex to perform my tests (or should I
really look for another tool to perform (simple) integration tests... if
so, recommendations for such a tool are welcomed).

Thanks for your advices!

Romain

-- 
Romain Tartière <ro...@bl...>        http://romain.blogreen.org/
pgp: 8234 9A78 E7C0 B807 0B59  80FF BA4D 1D95 5112 336F (ID: 0x5112336F)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)