From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Sebastian Wiesner <swiesner@lunaryorn.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Cask for testing
Date: Fri, 15 Aug 2014 11:43:57 +0100 [thread overview]
Message-ID: <87sikyav82.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <01403B62-6752-42F3-9CEA-AFCE18674BA3@lunaryorn.com> (Sebastian Wiesner's message of "Thu, 14 Aug 2014 16:09:32 +0200")
Sebastian Wiesner <swiesner@lunaryorn.com> writes:
>> I have been investigating Cask for use with testing my Emacs packages,
>> but have been struggling with it. The documentation is not very rich as
>> it stands. I was wondering if anyone has a good workflow?
>>
>> I thought I would start of with m-buffer.el which has few dependencies.
>>
>> https://github.com/phillord/m-buffer-el
>>
>> Currently, I have this testing in batch with a shell script. The
>> dependencies have been included and downloaded into the test directory
>> (which is obviously not ideal). I am using travis for CI. Testing also
>> works interactively from within Emacs. My hope was to use Cask for batch
>> dependency resolution.
>>
>> My Cask file looks like this:
>>
>> (source gnu)
>> (source melpa)
>>
>> (package-file "m-buffer.el")
>> (depends-on "dash")
>>
>> (development
>> (depends-on "ert-runner"))
>>
>> Cask correctly downloads the dependencies. But it doesn't put
>> m-buffer.el onto the load path. So any attempt to use ert-runner fails.
>> What am I doing wrong?
>
>
> Nothing, Cask simply doesn’t do that. It doesn’t make assumption about
> the local layout of the source code tree, since that’d be too flaky for
> more complex packages, e.g. consisting of different files in different
> directories.
(package-file "m-buffer.el") -- I mean, I've already told Cask about this.
> However, you can tell erg-runner to additional files, e.g.
>
> cask exec ert-runner -l ./m-buffer.el
>
> To make this permanent, add an „.ert-runner“ file to the root of your
> source code tree, with the following contents:
>
> -l ./m-buffer.el
Hmmm, okay. So cask then is setting my load-path to dependencies,
ert-runner is adding in files in the ./test directory? I guess this
helps in some way.
> Please note that Cask is not part of GNU Emacs, nor in any way affiliated
> with it. As such, this list is not the best place to ask questions about
> Cask, since it’s not regularly monitored by us. Please refer to the Github
> issue tracker or to Cask’s own mailing list for questions.
I didn't want to use an issue tracker to ask for help, and the only
mailing list that is mentioned in the documentation is cask-dev;
normally, I'd not send request for help to a -dev mailing list,
especially one with private archives.
Phil
prev parent reply other threads:[~2014-08-15 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 10:31 Cask for testing Phillip Lord
2014-08-14 14:09 ` Sebastian Wiesner
2014-08-14 15:06 ` Stefan Monnier
2014-08-15 10:43 ` Phillip Lord [this message]
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=87sikyav82.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--cc=help-gnu-emacs@gnu.org \
--cc=swiesner@lunaryorn.com \
/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.