Bug 140363 - UnitTestCase for StyledTextContent based on StyledTextContentSpec from Article "Into the deep end of the swt text widget"
Summary: UnitTestCase for StyledTextContent based on StyledTextContentSpec from Articl...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-05 10:28 EDT by Stefan Langer CLA
Modified: 2021-11-12 11:44 EST (History)
2 users (show)

See Also:

Attachments
UnitTest based on JUnit for the org.eclipse.swt.custom.StyledTextContent interface (37.99 KB, text/plain)
2006-05-05 10:29 EDT, Stefan Langer CLA 		no flags Details
View All 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 Stefan Langer CLA 2006-05-05 10:28:02 EDT 
I converted the StyledTextContentSpec class into a Junit TestCase for testing implementations of the StyledTextContent interface in the org.eclipse.swt.custom package. 
Code is added as an attachment see below.

The class was only tested on WinXP Pro on Eclipse 3.2RC2 but should work on any Eclipse where the StyledTextContent interface is available (Javadoc doesn't say which version the intereface was introduced). 
It relies on JUnit 3.8.
Comment 1 Stefan Langer CLA 2006-05-05 10:29:45 EDT 
Created attachment 40480 [details]
UnitTest based on JUnit for the org.eclipse.swt.custom.StyledTextContent interface

See bug description for details
Comment 2 Steve Northover CLA 2006-05-05 13:40:29 EDT 
Wow.  Good work.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:31:50 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.