Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Linux Tools Project/EPP Testing"
(→OProfile) |
(→GProf/GCov) |
||
Line 61: | Line 61: | ||
== GProf/GCov == | == GProf/GCov == | ||
− | * open gmon.out and *.gcda to verify viewers come up | + | * open gmon.out and *.gcno/*.gcda to verify viewers come up |
* ensure linking with source code functions properly | * ensure linking with source code functions properly | ||
== SystemTap == | == SystemTap == | ||
* click around SystemTap views and perspective a bit | * click around SystemTap views and perspective a bit |
Revision as of 13:21, 18 August 2011
Contents
Eclipse IDE for C/C++ Linux Developers Manual Testing
The Linux Tools team is responsible for an EPP package (look for it here). The following is a list of our manual test steps. Test projects can be found in this archive file: http://fedorapeople.org/~overholt/LinuxToolsTestProjects.zip.
ChangeLog
- ensure ChangeLog preferences are set
- make changes (add, remove, modify) in a Linux Tools CVS repo and press Ctrl-Alt-p
- verify that ChangeLog entry gets written and that new and removed are automatically filled in
- verify that Ctrl-clicking on files in ChangeLog opens them
- pick a C file and do a Ctrl-Alt-c in a function
- verify that the C function is specified in the ChangeLog
- pick a java file and do Ctrl-Alt-C in a method
- verify that the Java method is specified in the ChangeLog
- for ChangeLog + SVN testing, use http://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/autotools/trunk/org.eclipse.linuxtools.cdt.autotools
- for ChangeLog + CVS testing, use :pserver:anonymous@dev.eclipse.org:/cvsroot/org.eclipse module: www/linuxtools
Note that Ctrl-Alt-p conflicts with the Subversive "Create patch" keybinding but after disabling it, you should be able to prepare a ChangeLog entry.
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 # opcontrol --deinit and # echo 0 > /proc/sys/kernel/nmi_watchdog, 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 from C Project Wizard
- ensure project builds and can run executable
- verify there is a Configure console for the project as well as a build console
- open project's configure.ac file and verify macros colourized and outline view exists
- hover over AC_INIT and make sure hover exists
- open project properties and ensure there is an Autotools item in the tree
- open it and make sure that there are General and Configure Settings tabs
- click on Configure Settings tab to make sure view comes up ok
- do the same for General tab and click on Tools and Editors sub-tabs
- open C/C++ -> Build Settings -> Discovery and verify that there are language settings chosen and that the view has parse build output checked
- close property view
- open up sample/hello.c in the hello world project
- ensure that there are no warnings or errors in editor
- close Eclipse and restart
- verify that there are no warnings or errors in open hello.c file
- from Project menu select Reconfigure project and make sure project reconfigures
- verify there is a Configure console as well as the configuration appears in the CDT Global Build Console
- from Project menu select Autotools
- verify there is autoconf, automake, aclocal, autoheader, libtoolize, autoreconf
- select autoheader
- in the autoheader menu, add --help option and hit OK
- verify that there is an Autotools console and that it contains the help info for autoheader
- create a C++ hello world project from the C++ project wizard
- verify it builds and runs the executable
- import a CVS project and use C project wizard
- make sure project builds and runs
GProf/GCov
- open gmon.out and *.gcno/*.gcda to verify viewers come up
- ensure linking with source code functions properly
SystemTap
- click around SystemTap views and perspective a bit