Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347678 - Document non-automated test plan
Summary: Document non-automated test plan
Status: CLOSED WONTFIX
Alias: None
Product: Linux Tools
Classification: Tools
Component: Libhover (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 1.0   Edit
Assignee: Jeff Johnston CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 349817
  Show dependency tree
 
Reported: 2011-05-30 12:05 EDT by Andrew Overholt CLA
Modified: 2014-04-14 08:44 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Overholt CLA 2011-05-30 12:05:37 EDT 
I often find myself searching through user guides and old workspaces trying to find manual testing instructions and test case projects for exercising our plugins.  It would be very beneficial if we could document such manual testing on the wiki.  I've created a page for this sub-project here:

http://wiki.eclipse.org/index.php?title=Linux_Tools_Project/Manual_Tests/libhover&action=edit

Please put instructions as well as links to (attached to wiki or elsewhere) archived projects that can be used for testing.  Regular libhover as well as devhelp integration should be documented.  Thanks!
Comment 1 Alexander Kurtakov CLA 2014-04-14 08:44:10 EDT 
Closing as nothing is going to happen and we should aim at automated testing as much as possible.