view src/testdir/test_vim9_fails.vim @ 29216:32f3b86352e6 v8.2.5127

patch 8.2.5127: using assert_true() does not show value on failure Commit: https://github.com/vim/vim/commit/cdc6a43559d5b880f81efceb849f40c20af1ada1 Author: zeertzjq <zeertzjq@outlook.com> Date: Sun Jun 19 11:45:46 2022 +0100 patch 8.2.5127: using assert_true() does not show value on failure Problem: Using assert_true() does not show value on failure. Solution: Use assert_inrange(). (closes https://github.com/vim/vim/issues/10593)
author Bram Moolenaar <Bram@vim.org>
date Sun, 19 Jun 2022 13:00:05 +0200
parents b94ef0b282f1
children 54e36d01847b
line wrap: on
line source

" Test for Vim9 script with failures, causing memory leaks to be reported.
" The leaks happen after a fork() and can be ignored.

source check.vim

def Test_assignment()
  if !has('channel')
    CheckFeature channel
  else
    var chan1: channel
    var job1: job
    var job2: job = job_start('willfail')
  endif
enddef

" Unclear why this test causes valgrind to report problems.
def Test_job_info_return_type()
  if !has('job')
    CheckFeature job
  else
    var job: job = job_start(&shell)
    var jobs = job_info()
    assert_equal('list<job>', typename(jobs))
    assert_equal('dict<any>', typename(job_info(jobs[0])))
    job_stop(job)
  endif
enddef