diff options
| author | jvoisin | 2014-01-29 15:42:00 +0000 |
|---|---|---|
| committer | jvoisin | 2014-01-29 15:42:00 +0000 |
| commit | 1ca20db6741dabfbad567aa20bee92069a5ef5c7 (patch) | |
| tree | 2cc0e8160d6c96b9c033c5594c3bc953dec4c6f8 | |
| parent | 4ac7cda59cf9a01d820b2a280db6174782715a4b (diff) | |
Add a testing procedure.
| -rw-r--r-- | TESTING | 14 |
1 files changed, 14 insertions, 0 deletions
| @@ -0,0 +1,14 @@ | |||
| 1 | # Automatic testing | ||
| 2 | MAT comes with a comprehensive testsuite, that can be called with test.py. | ||
| 3 | Currently, it only tests the CLI, and the library, and runs in something | ||
| 4 | like 2 minutes on a Core i7/SSD. | ||
| 5 | |||
| 6 | # Manual testing | ||
| 7 | Since the GUI can not be automatically tested for yet, it has to be carefully | ||
| 8 | tested 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? | ||
