From 69dd49a814b90b9003185b86f4ebe010ae83cb0f Mon Sep 17 00:00:00 2001
From: "Richard W.M. Jones" <rjones@redhat.com>
Date: Wed, 26 Sep 2012 12:03:16 +0100
Subject: guestfs-testing(1): Start by running libguestfs-test-tool. (cherry
 picked from commit 9b7813c5bd91d53e358deee64ab42b00b42c37ba) (cherry picked
 from commit 7d674f2fbfa663366c957f8662822f55ed1f2e1c)

---
 examples/guestfs-testing.pod | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/examples/guestfs-testing.pod b/examples/guestfs-testing.pod
index 9bab630c..20160dd8 100644
--- a/examples/guestfs-testing.pod
+++ b/examples/guestfs-testing.pod
@@ -27,6 +27,20 @@ https://www.redhat.com/mailman/listinfo/libguestfs
 
 =head1 TESTS
 
+=head2 Run libguestfs-test-tool
+
+Run:
+
+ libguestfs-test-tool
+
+This command does a very simple, non-destructive test that basic
+libguestfs is functioning.  You don't need to run it as root.
+
+If it I<doesn't> print C<===== TEST FINISHED OK =====>, report it as a
+bug.  It is very important that you include the B<complete, unedited>
+output of C<libguestfs-test-tool> in your bug report.  See the
+L</BUGS> section at the end of this page.
+
 =head2 Check KVM acceleration is being used.
 
 If your host has hardware virt acceleration, then with a hot cache
-- 
cgit