test/test_Interpolation.py | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 prefer python3 shebang in test_interpolation.py

Note, print with parentheses and single argument produce the same output in old Python.

test/vim_test_case.py | 6 2 + 4 - 0 !
1 file changed, 2 insertions(+), 4 deletions(-)

 run automated tests against installed utlisnips

test_all.py | 13 10 + 3 - 0 !
1 file changed, 10 insertions(+), 3 deletions(-)

 detect vim_flavor from call to has('nvim')

test/test_SnippetActions.py | 6 6 + 0 - 0 !
1 file changed, 6 insertions(+)

 ignore in neovim broken test
 SnippetActions_PostActionModifiesCharAfterSnippet

test/test_Autotrigger.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 invert check_required_vim_version in
 Autotrigger_WillProduceNoExceptionWithVimLowerThan214

More accurate check does not imply NeoVim. It has got working autotrigger feature.

test/vim_interface.py | 11 3 + 8 - 0 !
1 file changed, 3 insertions(+), 8 deletions(-)

 check success of "tmux send-keys"

If for any reason tmux failed, reveal the error raising a subprocess exception.
This makes debugging a lot easier. If something goes wrong, for instance tmux
session is not started, we will see stack trace, command arguments as an
array, and all output. However, the output is printed in a mess with unittest
messages, but it is okay.

Furthermore, the Python documentation cautions against using stdout=PIPE or
stderr=PIPE with the call() function.

test/vim_interface.py | 21 6 + 15 - 0 !
1 file changed, 6 insertions(+), 15 deletions(-)

 check vim version through call to vim's has() function

 * Do not parse output of the `--version` option. The format is not documented.

test/vim_test_case.py | 17 13 + 4 - 0 !
1 file changed, 13 insertions(+), 4 deletions(-)

 respect the retries option in tests with the expected_error parameter

 * Remove the `return` instruction from the loop over [0, retries) if the
   expected_error parameter is set.
 * Break the loop early when the check is successful.
 * This trick reduces chance of failure due to input/output race in tmux.

test/test_Autocommands.py | 4 2 + 2 - 0 !
test/test_Interpolation.py | 2 1 + 1 - 0 !
test/test_ParseSnippets.py | 6 3 + 3 - 0 !
test/test_SnippetOptions.py | 2 1 + 1 - 0 !
test/test_Transformation.py | 10 5 + 5 - 0 !
test/test_UltiSnipFunc.py | 2 1 + 1 - 0 !
6 files changed, 13 insertions(+), 13 deletions(-)

 fix syntax warnings about invalid escape sequences in tests

Based on upstream commit 79b063ac44eb5a9c28129bc3837fef789a3190fa.

pythonx/UltiSnips/err_to_scratch_buffer.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 fix syntax warnings about invalid escape sequences in error reports

Upstream fixed in commit 91911c71d2a396e3b651d4ba4546e02ce1b252cc.
Closes: https://bugs.debian.org/1087165

test/vim_interface.py | 6 3 + 3 - 0 !
1 file changed, 3 insertions(+), 3 deletions(-)

 respect tmpdir for neovim socket

test/vim_interface.py | 9 7 + 2 - 0 !
1 file changed, 7 insertions(+), 2 deletions(-)

 finite waiting of load and exit events in tests

test/test_ParseSnippets.py | 7 7 + 0 - 0 !
1 file changed, 7 insertions(+)

 skip test flaky with neovim

Closes: https://bugs.debian.org/1033510

test/vim_interface.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 parse version prefixed with next- when tmux is built from git
 snapshot

Closes: https://bugs.debian.org/1076965