From: "Alex Bennée" <kernel-hacker@bennee.com>
To: "help-gnu-emacs\@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Writing ERT tests for asynchronous events
Date: Thu, 02 Jan 2014 10:43:51 +0000 [thread overview]
Message-ID: <87ppoaoe8o.fsf@linaro.org> (raw)
Hi,
Is there any support in ERT for things that have asynchronous behaviour?
For example I want my test to kick off something using a url fetch
(against a server running in the same emacs) and then once the
transaction has completed test things have worked as expected
using the ert operators.
If I can't do this is might be simpler to hook in bellow the network
processing bits but in that case I need create a mock process buffer to
represent the network connection process. What's the best way to do that?
Cheers,
--
Alex Bennée
http://www.bennee.com/~alex
next reply other threads:[~2014-01-02 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 10:43 Alex Bennée [this message]
2014-01-02 11:41 ` Writing ERT tests for asynchronous events Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppoaoe8o.fsf@linaro.org \
--to=kernel-hacker@bennee.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).