linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ckulkarnilinux@gmail.com (Chaitanya Kulkarni)
Subject: Introducing Unit test framework based on nvme-cli
Date: Wed, 26 Oct 2016 23:48:36 -0700	[thread overview]
Message-ID: <1477550917-6472-1-git-send-email-chaitanya.kulkarni@hgst.com> (raw)

Hi,

Introducing nvme-cli based unit test framework. All the test cases use commands implemented in nvme-cli.

The goal is to have simple, lightweight, and easily usable framework which we can used to
develop various categories of unit tests based on nvme-cli and improve overall development.

Over the period of time since release of the nvme-cli various test cases are developed which are now integral part of our device deriver testing.

These test cases are evolved with nvme-cli and can be used for nvme-cli testing. 

I would like to take this opportunity and share first set of test cases which has most frequently used generic NVMe features from cli :-

1. nvme_attach_detach_ns_test.py
2. nvme_compare_test.py
3. nvme_create_max_ns_test.py
4. nvme_error_log_test.py
5. nvme_flush_test.py
6. nvme_format_test.py
7. nvme_get_features_test.py
8. nvme_read_write_test.py
9. nvme_smart_log_test.py
10. nvme_writeuncor_test.py
11. nvme_writezeros_test.py

Please have a look at README for an overview and process of adding new test case. 
Framework also has a sample template which can be used readily to write new test case.

Assumptions for current implementation :-
1. nvme-cli is already installed on the system.
2. Only one test case can be executed at any given time.
3. Each test case has logical PRE, RUN and POST sections.
4. It assumes that driver is loaded and default namespace "/dev/nvme0n1" is present. 
(It is easy to add driver load/unload in pre and post sections of test cases as per requirement.)

I?d like to know what features, test cases most people would want as a part of this framework.
Any suggestions are welcome, I'd like to implement them.

On approval I would like to submit more test cases to enhance the framework.

Patch Ref :- [PATCH] Unittest framework based on nvme-cli.

Regards,
Chaitanya

             reply	other threads:[~2016-10-27  6:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27  6:48 Chaitanya Kulkarni [this message]
2016-10-27  6:48 ` [PATCH] Unittest framework based on nvme-cli Chaitanya Kulkarni
2016-11-16 17:58 ` Introducing Unit test " Christoph Hellwig
2016-11-16 18:35   ` Keith Busch
2016-11-16 19:43     ` J Freyensee
2016-11-16 21:37       ` Keith Busch
2016-11-17 12:36         ` Sagi Grimberg
2016-11-17 12:40           ` Christoph Hellwig
2016-11-17 16:05           ` Keith Busch
2016-11-22  2:45             ` Stephen Bates

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=1477550917-6472-1-git-send-email-chaitanya.kulkarni@hgst.com \
    --to=ckulkarnilinux@gmail.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).