dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Akira Hayakawa <ruby.wktk@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Introduce writeboost-test-suite
Date: Sun, 3 Jul 2016 22:51:52 +0900	[thread overview]
Message-ID: <dcb100df-628c-0473-d192-60e48df30e8f@gmail.com> (raw)

Hi,

To test my ssd-caching module dm-writeboost (https://github.com/akiradeveloper/dm-writeboost)
I used to add tests to forked device-mapper-test-suite but I found that it's not easy to maintain
the tests because Ruby doesn't give us compile-time type checking and the code base is bit messy
because of historical reason.

So I started to develop my own test suite from scratch.

writeboost-test-suite is written in Scala. The functionality is similar to device-mapper-test-suite but
more functionalities added. It's easy to write tests safely because of static typing.

https://github.com/akiradeveloper/writeboost-test-suite

I've almost had the work done. Most of the writeboost tests are migrated and fixes the bugs in the
framework core in the course of migration.

Despite the name of the project, it's versatile. Any device-mapper targets can be tested on this framework
and actually some targets (linear, flakey and LUKS) are slightly tested, to use them in writeboost tests.

Theoretically, it's possible to test caching and thin-provisioning targets on this framework. If RH developers
feels the device-mapper-test-suite is hard to maintain and looking for alternative, very welcome.

- Akira

                 reply	other threads:[~2016-07-03 13:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dcb100df-628c-0473-d192-60e48df30e8f@gmail.com \
    --to=ruby.wktk@gmail.com \
    --cc=dm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).