all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Samer Masterson <samer@samertm.com>
Cc: stephen_leake@stephe-leake.org, emacs-devel@gnu.org
Subject: Re: Adding testing information to CONTRIBUTE
Date: Thu, 05 Mar 2015 18:41:54 +0200	[thread overview]
Message-ID: <83zj7ro0q5.fsf@gnu.org> (raw)
In-Reply-To: <1425553346.2108.2@mail.samertm.com>

> Date: Thu, 05 Mar 2015 03:02:26 -0800
> From: Samer Masterson <samer@samertm.com>
> Cc: stephen_leake@stephe-leake.org
> 
> As a new contributor, I have no idea how to run or write tests for Emacs, which
> means I end up testing my patches manually and miss bugs. I could try to learn
> how Emacs uses tests on my own, but it would benefit future new contributors if
> we added a section on testing to CONTRIBUTE.
> 
> Here is what I would want to see:
> - How to write tests, with a pointer to an internal Emacs package that has
> idiomatic and comprehensive tests.
> - How to run tests on the entire tree and on individual files.
> - A pointer to an info page on the testing framework/pattern that most internal
> Emacs packages use.

Most of this is described in ert.info, which I presume you've read.

I agree that CONTRIBUTE should mention that manual (right near the
place that it mentions "Tips" and "GNU Emacs Internals").



  parent reply	other threads:[~2015-03-05 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 11:02 Adding testing information to CONTRIBUTE Samer Masterson
2015-03-05 14:14 ` Samer Masterson
2015-03-05 16:47   ` Eli Zaretskii
2015-03-05 19:31     ` Samer Masterson
2015-03-15  7:49       ` [PATCH] " Samer Masterson
2015-03-15 17:39         ` Eli Zaretskii
2015-03-05 16:41 ` Eli Zaretskii [this message]
2015-03-05 19:25   ` Samer Masterson

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zj7ro0q5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=samer@samertm.com \
    --cc=stephen_leake@stephe-leake.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.