Psklenar/abrt-GUI

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 9: Line 9:
 
  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"
 +
  
 
== what was done? ==
 
== what was done? ==
 
just one preview test :)
 
just one preview test :)
  
=== how does it look ===
+
=== how does it look like now? ===
 
==== sources ====
 
==== sources ====
 
[http://people.redhat.com/psklenar/pub/abrtTestLib.py abrtTestLib.py]
 
[http://people.redhat.com/psklenar/pub/abrtTestLib.py abrtTestLib.py]
Line 26: Line 27:
  
 
''there are simple test report''
 
''there are simple test report''
 +
 +
= TODO =
 +
 +
is dogtail suitable?
 +
 +
what to automate?
 +
- start with test procedure from test days

Revision as of 13:35, 11 May 2011

Contents

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"


what was done?

just one preview test :)

how does it look like now?

sources

abrtTestLib.py

first.py

second.py

runtest.sh

test output

there are screenshots, look at output with screenshot

there are simple test report

TODO

is dogtail suitable?

what to automate?

- start with test procedure from test days