diff options
Diffstat (limited to 'doc/how-to-test')
| -rw-r--r-- | doc/how-to-test | 41 |
1 files changed, 41 insertions, 0 deletions
diff --git a/doc/how-to-test b/doc/how-to-test new file mode 100644 index 00000000..425a2b34 --- /dev/null +++ b/doc/how-to-test @@ -0,0 +1,41 @@ +How to test before releasing new update: + +I. Build and install +=================== +a) build the packages as scratch in koji +b) download and install (the best is to create a local repo and try to install it using yum) +c) create a repository and try to update from previous packages +d) start the daemon and check logs for any sign of a problem +e) try to update from previous Fedora version using created repository + +II. Crash detection +===================== + == 1. Default crash detection == + a) kill some C/C++ app with kill -9 and watch if it's detected by abrt + b) edit some packaged python script to raise an exception and watch is abrt + detects it + c) use our saved kerneloopses and test detection of oopses + + == 2. Advanced crash detection == + a) crash some app that comes from unsigned package - abrt should ignore it + b) disable the gpg check and try repeat step a) - abrt shouldn't ignore it + +- try to add some crash-time action and test if it works + +III. Reporting +============= + == 1. Reporting to bugzilla == + a) try to report some crash to bz using gui + - gui should ask for login+pass + - crash should be reported after filling the right credentials + b) try to report using gui without gnome-keyring + - gui should ask for login+pass + - crash should be reported after filling the right credentials + - login+pass won't be saved + c) try to report every supported crash abrt detects C/C++, oops, python script + d) try to report some crash with bad backtrace - this should fail + e) repeat this with cli + +- test reporting with all reporters plugins like: ticketuploader, filetransport, etc.. + repeating the step 'a' to 'e' + |