Psklenar/abrt-GUI

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Free comments)
(what to test?)
 
Line 10: 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
+
* 1. abrt-gui
2. produce simple crash
+
* 2. produce simple crash
3. report it by clicking next, next, next and filling something into "how to reproduce"
+
* 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"
+
* 4. see if there is /var/log/abrt.log with my generated "how to reproduce"
  
 
== when to test? ==
 
== when to test? ==

Latest revision as of 16:41, 11 May 2011

this is free for wiki, comment in as you wish


Contents

[edit] why start to write gui test ?

GUI is part which mainly touch end-users.

[edit] which gui framework to use?

dont know much, I took dogtail and use it in python script


[edit] 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"

[edit] when to test?

each built / each week / once a year?

[edit] what was done?

just one preview test :)

[edit] how does it look like now?

[edit] sources

abrtTestLib.py

first.py

second.py

runtest.sh

[edit] test output

Test generates screenshots, look at output with screenshot


[edit] 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