jEdit Community home jEdit Community Wiki > Main > Wish List > EditModeTestingFramework jEdit Community Wiki webs:
Main | Plugins | Know | TWiki | Sandbox
Main . { Whats New | Users | Groups | Changes | Index | Search | Go }
Writing a totally accurate Edit Mode? isn't easy (not through any fault of jEdit's). It takes many revisions, and each change has the potential to cause another error. Having a JUnit-esque unit testing framework for Edit Mode? highlighting would be a huge help to make sure that Edit Modes? keep improving. Clever users could even submit test cases with their bug reports.

I realize this isn't like to happen but I thought I'd throw this out there in case someone decides to jump on it.

My initial thoughts on implementation would be a plugin that opens a test file and probes the jEdit Text Area?, using test cases written in Bean Shell.

Another idea is to write a plugin which is like Code2HTML but outputs XML (, tags, etc). Then you can just compare the edit mode's current output for some input with "known good" output.

Feature Form
Status: Requested
Implementation: Undecided

Topic EditModeTestingFramework . { Edit | Attach | Ref-By | Printable | Diffs | r1.2 | > | r1.1 | More }
Revision r1.2 - 23 Dec 2003 - 19:49 GMT - Slava Pestov
Parents: Wish List
Copyright © 1999-2011 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding jEdit Community Wiki? Send feedback.
Get jEdit at ! Fast, secure and Free Open Source software downloads