No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
'''this is free for wiki, comment in as you wish''' | |||
== why start to write gui test ? == | == why start to write gui test ? == | ||
GUI is part which mainly touch end-users. | GUI is part which mainly touch end-users. |
Revision as of 13:47, 11 May 2011
this is free for wiki, comment in as you wish
why start to write gui test ?
GUI is part which mainly touch end-users.
which gui framework to use?
dont know much, I took dogtail and use it in python script
what to test?
Now I created the first simple test procedure with abrt on latest rhel6
1. abrt-gui 2. produce simple crash 3. report it by clicking next, next, next and filling something into "how to reproduce" 4. see if there is /var/log/abrt.log with my generated "how to reproduce"
when to test?
each built / each week / once a year?
what was done?
just one preview test :)
how does it look like now?
sources
test output
Test generates screenshots, look at output with screenshot
there are simple test report
Free comments
give your ideas here
is dogtail suitable? Is there any other GUI framework ?
what to automate?
- start with test procedure from test days