Unit tests

Bug #298201 reported by Lionel Dricot on 2008-11-14
Affects Status Importance Assigned to Milestone

Bug Description

Autant prendre des bonnes habitudes dès le début !

Ce serait bien de pondre des tests unitaires sur à peu près tout dans GTG

1) trouver un framework de tests en python (le plus facile/populaire)

2) Implémenter des tests unitaires pour le backend et l'intelligence système (genre : lire un projet d'un backend, ajouter une tâche, la supprimer, réécrire le projet et comparer les outputs)

3) Pour le GUI, on fait comment ? Des tests qui appellent les fonctions des bouttons ?

Changed in gtg:
importance: Undecided → Wishlist
Changed in gtg:
milestone: none → 0.2
Changed in gtg:
importance: Wishlist → Medium
status: New → Confirmed
chaica (chaica) wrote :

Hey this is the beginning of a test series for the backends. Please feel free to comment.

chaica (chaica) wrote :

As planned here is the full series of tests for localfile backend.
You just need to put the file in GTG/backends and it shoud be fine. The code is documented but ask me if something is not clear about test policies.

You need a directory like ~/.local/share/gtg (supplied by xdg.BaseDirectory.xdg_data_home) 'cause some files are created during the tests, if you don't have one the app will create it.

I guess you guys can easy improve test quality, but it should be a good start.
Let me know what you think about it!

Carl Chenet

Chaica > thanks for the excellent work ! The test is merged in rev 196 and works fine. As for now, we consider this bug as fixed. Every specific test that should be done should be requested in its own separate bug.

Changed in gtg:
assignee: nobody → ploum
status: Confirmed → Fix Committed
Changed in gtg:
milestone: 0.2 → 0.1.1
Changed in gtg:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers