Currently we don't have a test procedure to make sure that amora is working
correctly.
Even if we do some common tests when developing, it would be nice to create
a workbook of tests.
I think that we should include things like:
- Dongle removal
- Client/server disconnection
- Screenshots
- Mouse events
- Keyboard events
Any further ideas should be added in this issue.
Original issue reported on code.google.com by cavalcan...@gmail.com on 12 Feb 2008 at 8:53
Original issue reported on code.google.com by
cavalcan...@gmail.com
on 12 Feb 2008 at 8:53