1
edit
Changes
Created page with '== Activity 2: Perform manual testing on the Valgrind Tool. == == Resources == * the Getting Involved page on the Eclipse Linux Tools wiki [http://wiki.eclipse.org/Linux_Tools_P...'
== Activity 2: Perform manual testing on the Valgrind Tool. ==
== Resources ==
* the Getting Involved page on the Eclipse Linux Tools wiki [http://wiki.eclipse.org/Linux_Tools_Project/Getting_Involved]
* User Guide for Valgrind on the Eclipse Linux Tools wiki
** especially the section on Memcheck
* Andrew Overholt's presentation (videos)
* Eclipse Community Forum - Linux Tools
== Guidelines ==
*Install Valgrind on the Fedora machine
*Use the Valgrind to create a C/C++ example.
*Create different manual test scenarios (i.e. C/C++ projects and expected results).
** Use the C/C++ programs that you have done at Seneca.
** Create some C/C++ programs that have memory leaks.
*Document (i.e. write) the test scenarios.
== Feedback from the Eclipse Linux Tools Developers ==
== Resources ==
* the Getting Involved page on the Eclipse Linux Tools wiki [http://wiki.eclipse.org/Linux_Tools_Project/Getting_Involved]
* User Guide for Valgrind on the Eclipse Linux Tools wiki
** especially the section on Memcheck
* Andrew Overholt's presentation (videos)
* Eclipse Community Forum - Linux Tools
== Guidelines ==
*Install Valgrind on the Fedora machine
*Use the Valgrind to create a C/C++ example.
*Create different manual test scenarios (i.e. C/C++ projects and expected results).
** Use the C/C++ programs that you have done at Seneca.
** Create some C/C++ programs that have memory leaks.
*Document (i.e. write) the test scenarios.
== Feedback from the Eclipse Linux Tools Developers ==