From: Michal Nazarewicz <mina86@mina86.com>
To: 22632@debbugs.gnu.org
Subject: bug#22632: [PATCH 0/4] `ert-with-function-mocked' and refactoring `message-strip-subject-trailing-was'
Date: Thu, 11 Feb 2016 15:50:58 +0100 [thread overview]
Message-ID: <1455202258-23963-1-git-send-email-mina86@mina86.com> (raw)
I started with refactoring `message-strip-subject-trailing-was'
function but ended up also including `ert-with-function-mocked' macro
which lead to two changes in existing unit-tests.
Michal Nazarewicz (4):
Introduce `ert-with-function-mocked' macro
Make use of the `ert-with-function-mocked' macro
Add test for `message-strip-subject-trailing-was'
Refactor `message-strip-subject-trailing-was' function
etc/NEWS | 3 +++
lisp/emacs-lisp/ert-x.el | 40 +++++++++++++++++++++++++++++
lisp/gnus/message.el | 47 +++++++++++++++--------------------
test/lisp/calendar/icalendar-tests.el | 20 ++++++---------
test/lisp/emacs-lisp/ert-x-tests.el | 43 ++++++++++++++++++++++++++++++++
test/lisp/gnus/message-tests.el | 43 ++++++++++++++++++++++++++++++++
test/lisp/vc/vc-bzr-tests.el | 9 +++----
7 files changed, 159 insertions(+), 46 deletions(-)
--
2.7.0.rc3.207.g0ac5344
next reply other threads:[~2016-02-11 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 14:50 Michal Nazarewicz [this message]
2016-02-11 15:02 ` bug#22632: [PATCH 1/4] Introduce `ert-with-function-mocked' macro Michal Nazarewicz
2016-02-11 15:02 ` bug#22632: [PATCH 2/4] Make use of the " Michal Nazarewicz
2016-02-11 15:02 ` bug#22632: [PATCH 3/4] Add test for `message-strip-subject-trailing-was' Michal Nazarewicz
2016-02-11 15:02 ` bug#22632: [PATCH 4/4] Refactor `message-strip-subject-trailing-was' function Michal Nazarewicz
2016-02-23 3:49 ` bug#22632: [PATCH 0/4] `ert-with-function-mocked' and refactoring `message-strip-subject-trailing-was' Lars Ingebrigtsen
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=1455202258-23963-1-git-send-email-mina86@mina86.com \
--to=mina86@mina86.com \
--cc=22632@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).