summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjvoisin2014-01-29 15:42:00 +0000
committerjvoisin2014-01-29 15:42:00 +0000
commit1ca20db6741dabfbad567aa20bee92069a5ef5c7 (patch)
tree2cc0e8160d6c96b9c033c5594c3bc953dec4c6f8
parent4ac7cda59cf9a01d820b2a280db6174782715a4b (diff)
Add a testing procedure.
Diffstat (limited to '')
-rw-r--r--TESTING14
1 files changed, 14 insertions, 0 deletions
diff --git a/TESTING b/TESTING
new file mode 100644
index 0000000..017be9c
--- /dev/null
+++ b/TESTING
@@ -0,0 +1,14 @@
1# Automatic testing
2MAT comes with a comprehensive testsuite, that can be called with test.py.
3Currently, it only tests the CLI, and the library, and runs in something
4like 2 minutes on a Core i7/SSD.
5
6# Manual testing
7Since the GUI can not be automatically tested for yet, it has to be carefully
8tested manually. Here are some importants points:
9
10- Is the status bar message the right one for every actions?
11- Are nested archives correctly handled ? Even when they contains unknown-to-MAT formats?
12- When started from a terminal, does it ouputs text/warnings?
13- Does the GUI clean files?
14- Is it correctly translated?