| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Crash when using wrong arg types to assert_match().
Solution: Check for NULL pointer. (closes #12349)
|
|
Problem: Assert message is confusing with boolean result. assert_inrange()
replaces message instead of adding it.
Solution: Don't put quotes around expected boolean value. Append message
for assert_inrange(). (closes #12342, closes #12341)
|
|
Problem: Code style is not check in test scripts.
Solution: Add basic code style check for test files.
|
|
Problem: No proper test for what 9.0.0846 fixes.
Solution: Run test in a terminal so that the hit-enter prompt can show up.
(closes #11523)
|
|
Problem: Using assert_fails() may cause hit-enter prompt.
Solution: Set no_wait_return. (closes #11522)
|
|
Problem: Insufficient testing for assert and test functions.
Solution: Add a few more tests. (Yegappan Lakshmanan, closes #11190)
|
|
Problem: No good reason to build without the float feature.
Solution: Remove configure check for float and "#ifdef FEAT_FLOAT".
|
|
Problem: Crash when passing invalid arguments to assert_fails().
Solution: Check for NULL string.
|
|
Problem: Deleting files in tests is a hassle.
Solution: Use the new 'D' flag of writefile().
|
|
Problem: Error message for wrong argument type is not specific.
Solution: Include more information in the error. (Yegappan Lakshmanan,
closes #11037)
|
|
Problem: Using freed memory with error in assert argument.
Solution: Make a copy of the error.
|
|
Problem: Crash when using many composing characters in error message.
Solution: Use mb_cptr2char_adv() instead of mb_ptr2char_adv().
|
|
Problem: Vim9: runtime and compile time type checks are not the same.
Solution: Add more runtime type checks for builtin functions. (Yegappan
Lakshmanan, closes #8646)
|
|
Problem: Vim9: argument types are not checked at compile time.
Solution: Add several more type checks. (Yegappan Lakshmanan, closes #8632)
|
|
Problem: Vim9: builtin function arguments not checked at compile time.
Solution: Add more argument type specs. Check arguments to test_setmouse()
and test_gui_mouse_event(). (Yegappan Lakshmanan, closes #8425)
|
|
Problem: Vim9: extra "unknown" error after other error.
Solution: Restore did_emsg count after EXEC instruction. (closes #7254)
Improve error message from assert_fails()
|
|
Problem: Inconsistent capitalization of error messages.
Solution: Always start with a capital.
|
|
Problem: Not checking the context of test_fails().
Solution: Add the line number and context arguments. Give error if
assert_fails() argument types are wrong.
|
|
Problem: Tests do not check the error number properly.0
Solution: Add a colon after the error number. (closes #6869)
|
|
Problem: Various inconsistencies in test files.
Solution: Add modelines where they were missing. Use Check commands instead
of silently skipping over tests. Adjust indents and comments.
(Ken Takata, closes #6695)
|
|
Problem: Not all assert functions are fully tested.
Solution: Test more assert functions.
|
|
Problem: Some tests fail.
Solution: Adjust tests for different assert_fails() behavior. Remove unused
variable.
|
|
Problem: Assert_equal() output for dicts is hard to figure out.
Solution: Only show the different items.
|
|
Problem: Assert_equalfile() does not give a hint about the difference.
Solution: Display the last seen text.
|
|
Problem: Assert_equalfile() does not take a third argument.
Solution: Implement the third argument. (Gary Johnson)
|
|
Problem: Comparing two NULL list fails.
Solution: Change the order of comparing two lists.
|
|
Problem: More functions can be used as methods.
Solution: Make various functions usable as a method. Make the window
command test faster.
|
|
Problem: More functions can be used as methods.
Solution: Make a few more functions usable as a method.
|
|
Problem: Only some assert functions can be used as a method.
Solution: Allow using most assert functions as a method.
|
|
Problem: Assert_fails() does not fail inside try/catch.
Solution: Set trylevel to zero. (Ozaki Kiichi, closes #4639)
|
|
Problem: Tests are silently skipped.
Solution: Throw an exception for skipped tests in more places.
|
|
Problem: Compiling weird regexp pattern is very slow.
Solution: When reallocating post list increase size by 50%. (Kuang-che Wu,
closes #4012) Make assert_inrange() accept float values.
|
|
Problem: A failed assert with a long string is hard to read.
Solution: Shorten the assert message.
|
|
Problem: assert_fails() does not take a message argument
Solution: Add the argument.
|
|
Problem: If a test function exists Vim this may go unnoticed.
Solution: Check for a test funtion quitting Vim. Fix tests that did exit
Vim.
|
|
Problem: Assert functions don't return anything.
Solution: Return non-zero when the assertion fails.
|
|
Problem: Cannot write and read terminal screendumps.
Solution: Add term_dumpwrite(), term_dumpread() and term_dumpdiff().
Also add assert_equalfile().
|
|
Problem: Cannot test if a command causes a beep.
Solution: Add assert_beeps().
|
|
Problem: Tests use assert_true(0) and assert_false(1) to report errors.
Solution: Use assert_report().
|
|
Problem: Not enough test coverage in Insert mode.
Solution: Add lots of tests. Add test_override(). (Christian Brabandt,
closes #1521)
|
|
Problem: When using an assert function one can either specify a message or
get a message about what failed, not both.
Solution: Concatenate the error with the message.
|
|
Problem: The error message from assert_notequal() is confusing.
Solution: Only mention the expected value.
|
|
Problem: Internal error for assert_inrange(1, 1).
Solution: Adjust number of allowed arguments. (Dominique Pelle)
|
|
Problem: Man test fails when run with the GUI.
Solution: Adjust for different behavior of GUI. Add assert_inrange().
|
|
Problem: Can't assert for not equal and not matching.
Solution: Add assert_notmatch() and assert_notequal().
|
|
Problem: In tests it's often useful to check if a pattern matches.
Solution: Add assert_match().
|
|
Problem: Crash in assert_fails().
Solution: Check for NULL. (Dominique Pelle) Add a test.
|
|
Problem: Crash when assert_equal() runs into a NULL string.
Solution: Check for NULL. (Dominique) Add a test.
|
|
Problem: assert_false(v:false) reports an error. (Nikolai Pavlov)
Solution: Recognize v:true and v:false. (Closes #625)
|
|
Problem: Crash when setting v:errors to a number.
Solution: Free the typval without assuming its type. (Yasuhiro Matsumoto)
|
