Espuds - Ecukes step definitions

First of all. If you don't know what Ecukes is, go read up about it first. If you have, you should know that in order to test with Ecukes, you need to translate your steps so that Emacs understands them. You do that with step definitions.

Espuds is a collection of the most commonly used step definitions.

Installation

Cask

Add espuds to your Cask file:

(source melpa)

(depends-on "espuds")

Eask

💡 Eask is very similar to Cask; anything that applies to Cask will apply to Eask

Add espuds to your Eask file:

(source 'melpa)

(depends-on "espuds")

Gotchas

Spurious test passes due to cl-assert issues in emacs 25

In emacs 25.1 cl-assert (which is used interally by espuds) changed in a way that caused messy stack traces on test failures.

In emacs 25.2 cl-assert changed again in a way that causes assertion failures to completely bypass ecukes' error handling. This means that all tests will appear to pass regardless of their correctness.

This is being looked into, but a temporary workaround is to use the following snippet in your support/env.el file to restore the old behaviour:

 ;; This fixes issues in emacs 25.x where cl-assert has strange behaviours when `debug-on-error` is `t`.
 (when (and (= emacs-major-version 25))
   (require 'cl-preloaded)
   (setf (symbol-function 'cl--assertion-failed)
         (lambda (form &optional string sargs args)
           "This function has been modified by ecukes to fix problems with cl-assert in emacs 25.
           The modified version should only be used for running espuds tests."
           (if string
               (apply #'error string (append sargs args))
             (signal 'cl-assertion-failed `(,form ,@sargs))))))

Action Chain

Some actions require more than one keyboard input. For example functions that reads input via the minibuffer (not via interactive). To handle such cases, you wrap the actions in a block. For example:

Scenario: Activate linum mode
  Given I start an action chain
  And I press "M-x"
  And I type "linum-mode"
  And I execute the action chain
  Then linum-mode should be active

List of Steps

You can retrieve them by running the bin/docs script.

Otherwise you can just read this list:

• Given \(?:I am in buffer\|I switch to buffer\) "\(.+\)"
• Then I should be in buffer "\(.+\)"
• Then I should be in file "\(.+\)"
• Given the buffer is empty$\|^I clear the buffer
• When I go to line "\([0-9]+\)"
• When I go to point "\([0-9]+\)"
• When I go to word "\(.+\)"
• Then the cursor should be at point "\(.+\)"
• Then the cursor should be before "\(.+\)"
• Then the cursor should be after "\(.+\)"
• Then the cursor should be between "\(.+\)" and "\(.+\)"
• When I place the cursor between "\(.+\)" and "\(.+\)"
• When I place the cursor before "\(.+\)"
• When I place the cursor after "\(.+\)"
• When I go to beginning of buffer
• When I go to end of buffer
• When I go to beginning of line
• When I go to end of line
• When I start an action chain
• When I execute the action chain
• When I call "\(.+\)"
• When I press "\(.+\)"
• When I quit
• When I type "\(.+\)"
• When I turn on \(.+\)
• When I set \(.+\) to \(.+\)
• When I load the following:
• When I open temp file "\(.+\)"
• Then I should see message "\(.+\)"
• Given there is no region selected
• Given transient mark mode is \(active\|inactive\)
• When I set the mark
• When I pop the mark
• Then the region should be\(?: "\(.*\)"\|:\)
• Then the region should not be active
• When I insert\(?: "\(.+\)"\|:\)
• Then I should see\(?: "\(.+\)"\|:\)
• Then I should not see\(?: "\(.+\)"\|:\)
• Then I should see pattern\(?: "\(.+\)"\|:\)
• Then I should not see pattern\(?: "\(.+\)"\|:\)
• When I select "\(.+\)"
• Then I should not see anything$\|^the buffer should be empty
• Then current point should be in bold
• Then current point should be in italic
• Then current point should be in strike-through
• Then current point should be in underline
• Then current point should have the \([-[:alnum:]]+\) face
• Then current point should have no face
• When I delete other windows

Contributing

Contribution is much welcome! When adding new features, please write tests for them!

Install cask if you haven't already, then:

$ cd /path/to/espuds
$ cask

Run all tests with:

$ make