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.
Linux Tools Project/EPP Testing
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
- create a hello world C project
- add the line: void *p = malloc(5000);
- build and right click on binary and choose Profile using Valgrind
- this should use memcheck and bring up the Valgrind window with error noted for unfreed malloc
- verify error marker is in hello.c and that clicking on error in Valgrind window brings up line in editor
- click on X icon in Valgrind window to verify error marker is removed
- right click on binary and choose Profiling Configurations
- under Valgrind, choose the current configuration for a.out and then in the Valgrind option tab select massif
- generate massif graph; click around graph and details table and verify code opens for snapshots
- test helgrind's xml output parsing and expand/collapse of results
- run cachegrind and test all plug-ins options and the expected output
OProfile
- ensure error messages are present for requiring the running of the installation script
- perform # opcontrol --deinit and # echo 0 > /proc/sys/kernel/nmi_watchdog
- create project with factorial.c program below
- for factorial project, go to Project Properties->Autotools->Configure Settings->Advanced and click on Debug (-g)
- profile binary using OProfile and verify OProfile shows values
- double-click in OProfile output to verify source integration functions properly
#include <stdio.h> long long factorial(int x) { long long result = x; while (x > 1) result = result * (x-- - 1); return result; } main() { long long x; int i; for (i = 0; i < 1000000; ++i) x = factorial(20); printf("result is %Ld\n", x); }
Autotools
- create a hello world gnu autotools project named "hello" from new 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 entry in the tree
- open it and make sure that there are General and Configure Settings tree entries
- click on Configure Settings tree entry to make sure view comes up ok on right
- do the same for General tree entry and click on Tools and Editors tabs
- open C/C++ Build -> Discovery Options 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 Invoke 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 autotools project (sourceware.org:/cvs/eclipse) specify anonymous and pserver and choose to use existing module
- open autotools in viewer and select sources, then hit next button
- choose to use new project wizard and hit Finish
- select C/C++ -> C project
- from C project wizard dialog select GNU Autotools -> empty project and hit Finish
- there will be a timing issue with the build and CVS checkout
- select Project->Reconfigure project and reconfigure project
- build project after that and make sure the executable runs (hello world type project)
Libhover
- go to previous Autotools hello world project
- open sample/hello.c in editor
- hover over puts function and verify that description is returned
- create new line in C file
- type mem and then hit CTRL+space and verify choice of C mem functions appears
- go to Project->Properties and open C/C++ General tree element
- click on Documentation tree element
- in Help Books list uncheck glibc entry and click Ok button
- go back to hello.c file in editor and hover over puts again
- verify that hover only shows prototype of function and no description
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