view tests/automated/process-tests.el @ 5892:053ef01b71a8

Import the #'clear-string API from GNU, use it in tls.c src/ChangeLog addition: 2015-04-18 Aidan Kehoe <kehoea@parhasard.net> * sequence.c (Fclear_string): New, API from GNU. Zero a string's contents, making sure the text is not kept around even when the string's data is reallocated because of a changed character length. * sequence.c (syms_of_sequence): Make it available to Lisp. * lisp.h: Make it available to C code. * tls.c (nss_pk11_password): Use it. * tls.c (gnutls_pk11_password): Use it. * tls.c (openssl_password): Use it. tests/ChangeLog addition: 2015-04-18 Aidan Kehoe <kehoea@parhasard.net> * automated/lisp-tests.el: Test #'clear-string, just added. Unfortunately there's no way to be certain from Lisp that the old password data has been erased after realloc; it may be worth adding a test to tests.c, but *we'll be reading memory we shouldn't be*, so that gives me pause.
author Aidan Kehoe <kehoea@parhasard.net>
date Sat, 18 Apr 2015 23:00:14 +0100
parents 7addb3dbe4b4
children
line wrap: on
line source

;;; process-tests.el --- test process execution

;; Copyright (C) 2011-2013 Free Software Foundation, Inc.

;; Author: Mats Lidell <matsl@xemacs.org>
;; Maintainer: XEmacs Dev Team <xemacs-beta@xemacs.org>
;; Created: 2011
;; Keywords: tests

;; This file is part of XEmacs.

;; XEmacs is free software: you can redistribute it and/or modify it
;; under the terms of the GNU General Public License as published by the
;; Free Software Foundation, either version 3 of the License, or (at your
;; option) any later version.

;; XEmacs is distributed in the hope that it will be useful, but WITHOUT
;; ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
;; FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
;; for more details.

;; You should have received a copy of the GNU General Public License
;; along with XEmacs.  If not, see <http://www.gnu.org/licenses/>.

;;; Synched up with: Not in FSF.

;;; Commentary:

;; Test tag support.
;; See test-harness.el for instructions on how to run these tests.

(require 'test-harness)

;; Should work on all POSIX systems.
(unless (member system-type '(windows-nt))
  (setenv "LANG" "C")
  
  ;; One line output
  (Assert (= 0 (shell-command "echo hello")))
  (Assert (equal "hello" (message-displayed-p t)))
  (with-current-buffer " *Echo Area*"
    (goto-char (point-min))
    (Assert (looking-at "hello")))

  ;; Two lines. No output in echo area. (GNU resizes minibuffer but we
  ;; haven't implemented that.)
  (message "")
  (Assert (= 0 (shell-command "echo -e \"foo\nbar\n\"")))
  (with-current-buffer " *Echo Area*"
    (Assert (= 0 (buffer-size))))
  (with-current-buffer "*Shell Command Output*"
    (goto-char (point-min))
    (Assert (looking-at "foo"))):

  (Assert (= 127 (shell-command "unknown_command")))
  (Assert (= 2 (shell-command "exit 2")))
  (Assert (equal "(Shell command failed with code 2 and no output)" (message-displayed-p t)))
  
  ;; Output to stderr With error buffer
  (Assert (= 0 (shell-command "echo -e \"foo\nbar\n\" 1>&2" "Output buffer" "Error buffer")))
  (Assert (equal "(Shell command succeeded with some error output)" (message-displayed-p t)))
  (with-current-buffer "Error buffer" 
    (goto-char (point-min))
    (Assert (looking-at "foo")))
  (with-current-buffer "Output buffer" 
    (Assert (= 0 (buffer-size))))

  ;; Output to stderr but no error buffer
  (Assert (= 0 (shell-command "echo -e \"foobar\nfoobar\n\" 1>&2" "Output buffer")))
  (with-current-buffer "Output buffer" 
    (goto-char (point-min))
    (Assert (looking-at "foobar")))
  )

;; call-process-shell-command
(when (equal system-type 'linux)
  (setenv "LANG" "C")

  ;; Output one line
  (Assert (= 0 (call-process-shell-command "echo hello")))

  ;; Output to stderr but no error buffer
  (Assert (= 0 (call-process-shell-command "echo -e \"barefoot\nfoobar\n\" 1>&2" nil "Output buffer")))
  (with-current-buffer "Output buffer" 
    (goto-char (point-min))
    (Assert (looking-at "barefoot\n")))
  )