From Fedora Project Wiki
No edit summary |
|||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''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? == | == which gui framework to use? == | ||
dont know much, I took [https://fedorahosted.org/dogtail dogtail] and use it in python script | dont know much, I took [https://fedorahosted.org/dogtail dogtail] and use it in python script | ||
| Line 4: | Line 10: | ||
== what to test? == | == what to test? == | ||
Now I created the first simple test procedure with abrt on latest rhel6 | 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? == | == what was done? == | ||
| Line 24: | Line 32: | ||
[http://people.redhat.com/psklenar/pub/runtest.sh runtest.sh] | [http://people.redhat.com/psklenar/pub/runtest.sh runtest.sh] | ||
==== test output ==== | ==== test output ==== | ||
Test generates screenshots, look at [http://people.redhat.com/psklenar/pub/output output with screenshot] | |||
= | = Free comments = | ||
''give your ideas here'' | |||
is dogtail suitable? | is dogtail suitable? ''Are there any other GUI frameworks ? '' | ||
what to automate? | what to automate? | ||
* start automate test procedures from test days | |||
Latest revision as of 16:41, 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
Free comments
give your ideas here
is dogtail suitable? Are there any other GUI frameworks ?
what to automate?
- start automate test procedures from test days