[LRUG] Testing Editors

[Aleksandar Simic]

Hello Stephen,

have you had a look at:

Ecukes: https://github.com/rejeep/ecukes
Espuds: https://github.com/rejeep/espuds

Think of it as Cucumber for Emacs, where you write the steps with Espuds
and Ecukes runs them. Here is a sample use:
https://github.com/rejeep/ruby-end/blob/master/features/ruby-end.feature#L1

I supposed you could test the interaction with the tool if you ran it in
Emacs' eshell...

Hope it helps,
Aleksandar


On Mon, Nov 5, 2012 at 7:38 AM, Stephen Nelson-Smith <sanelson at gmail.com>wrote:

> Suppose one wanted to write a test which verified how a piece of
> interactive software behaved - ie how it responded to keyboard input.
> Pretty trivial, right?  I've used PTY and also greenletters before for
> basic 'expect'-like tests.
>
> However, I'm thinking more along the lines of testing customisations
> or minor/major modes for Emacs or Vimscripts, or indeed custom config
> for any interactive tool.  They don't need to be hugely sophisticated
> tests, but something that at least verifies that the code under test
> doesn't generate an error, or that it does one simple, indicative
> feature would be handy.
>
> Has anyone been mad enough to try this before?  Any ideas?
>
> S.
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20121105/4f8da85c/attachment.html>