From 1ca20db6741dabfbad567aa20bee92069a5ef5c7 Mon Sep 17 00:00:00 2001
From: jvoisin
Date: Wed, 29 Jan 2014 15:42:00 +0000
Subject: Add a testing procedure.

---
 TESTING | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 TESTING

(limited to 'TESTING')

diff --git a/TESTING b/TESTING
new file mode 100644
index 0000000..017be9c
--- /dev/null
+++ b/TESTING
@@ -0,0 +1,14 @@
+# Automatic testing
+MAT comes with a comprehensive testsuite, that can be called with test.py.
+Currently, it only tests the CLI, and the library, and runs in something
+like 2 minutes on a Core i7/SSD.
+
+# Manual testing
+Since the GUI can not be automatically tested for yet, it has to be carefully
+tested manually. Here are some importants points:
+
+- Is the status bar message the right one for every actions?
+- Are nested archives correctly handled ? Even when they contains unknown-to-MAT formats?
+- When started from a terminal, does it ouputs text/warnings?
+- Does the GUI clean files?
+- Is it correctly translated?
-- 
cgit v1.3