Description Andrew Overholt 2011-06-20 09:29:47 EDT

We should document the manual testing we do for each EPP project.  A rough start of this:

== ChangeLog ==
* ensure ChangeLog preferences are set
* make a change in a Linux Tools CVS repo and press Ctrl-Alt-p
* verify that ChangeLog entry gets written
* verify that Ctrl-clicking on files in ChangeLog opens them

== RPM ==
* create an RPM project
* edit the .spec a bit, using templates and completion
* verify Ctrl-Alt-c uses ChangeLog name/email

== Valgrind ==
* generate massif graph; click around graph and details table and verify code opens
* run memcheck and verify source code integration works
* FIXME need something here for helgrind
* FIXME need something here for cachegrind

== OProfile ==
* ensure error messages are present for requiring the running of the installation script
* after <tt># opcontrol --deinit</tt> and <tt># </tt>, verify OProfile shows values for a binary that generates samples (ex. factorial)
* double-click in output to verify source integration functions properly

== Autotools ==
* create a hello world autotools project
* ensure project builds and can run

== GProf/GCov ==
* open gmon.out and *.gcda to verify viewers come up
* ensure linking with source code functions properly

== SystemTap ==
* click around SystemTap views and perspective a bit