Mercurial > vim
diff runtime/doc/testing.txt @ 21741:baccf9e06efe v8.2.1420
patch 8.2.1420: test 49 is old style
Commit: https://github.com/vim/vim/commit/f7c4d83609acdfe0e4d0fec9413697ac97c0c3f9
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Aug 11 20:42:19 2020 +0200
patch 8.2.1420: test 49 is old style
Problem: Test 49 is old style.
Solution: Convert remaining parts to new style. Remove obsolete items.
(Yegappan Lakshmanan, closes #6683)
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Tue, 11 Aug 2020 20:45:05 +0200 |
| parents | 3a1ed539ae2a |
| children | 30bdd2e4a6f9 |
line wrap: on
line diff
--- a/runtime/doc/testing.txt +++ b/runtime/doc/testing.txt @@ -20,18 +20,11 @@ 1. Testing Vim *testing* Vim can be tested after building it, usually with "make test". The tests are located in the directory "src/testdir". -There are several types of tests added over time: - test33.in oldest, don't add any of these - test_something.in old style tests - test_something.vim new style tests - *new-style-testing* -New tests should be added as new style tests. These use functions such as -|assert_equal()| to keep the test commands and the expected result in one -place. - *old-style-testing* -In some cases an old style test needs to be used. E.g. when testing Vim -without the |+eval| feature. +New tests should be added as new style tests. The test scripts are named +test_<feature>.vim (replace <feature> with the feature under test). These use +functions such as |assert_equal()| to keep the test commands and the expected +result in one place. Find more information in the file src/testdir/README.txt.