view src/testdir/test_job_fails.vim @ 10940:a479b7064550 v8.0.0359

patch 8.0.0359: 'number' and 'relativenumber' are not properly tested commit https://github.com/vim/vim/commit/dc9a081712ec8c140e6d4909e9f6b03a629d32d3 Author: Bram Moolenaar <Bram@vim.org> Date: Thu Feb 23 18:46:50 2017 +0100 patch 8.0.0359: 'number' and 'relativenumber' are not properly tested Problem: 'number' and 'relativenumber' are not properly tested. Solution: Add tests, change old style to new style tests. (Ozaki Kiichi, closes #1447)
author Christian Brabandt <cb@256bit.org>
date Thu, 23 Feb 2017 19:00:05 +0100
parents e0b783389bea
children c1347c968d31
line wrap: on
line source

" This test is in a separate file, because it usually causes reports for memory
" leaks under valgrind.  That is because when fork/exec fails memory is not
" freed.  Since the process exists right away it's not a real leak.

source shared.vim

func Test_job_start_fails()
  if has('job')
    let g:job = job_start('axdfxsdf')
    if has('unix')
      call WaitFor('job_status(g:job) == "dead"')
      call assert_equal('dead', job_status(g:job))
    else
      call WaitFor('job_status(g:job) == "fail"')
      call assert_equal('fail', job_status(g:job))
    endif
    unlet g:job
  endif
endfunc