Age | Commit message (Collapse) | Author |
|
Problem: Some test failures don't give a clear error.
Solution: Use assert_match() and assert_fails() instead of assert_true().
(Ken Takata, closes #7368)
|
|
Problem: Tests do not check the error number properly.0
Solution: Add a colon after the error number. (closes #6869)
|
|
Problem: Using \{xxx} for encoding a modifier is not nice.
Solution: Use \<*xxx> instead, since it's the same as \<xxx> but producing a
different code.
|
|
Problem: GUI tests fail because the test doesn't use a modifier.
Solution: Add "\{xxx}" to be able to encode a modifier.
|
|
Problem: No 'backspace' value allows ignoring the insertion point.
Solution: Add the "nostop" and 3 values. (Christian Brabandt, closes #5940)
|
|
Problem: Regexp and other code not tested.
Solution: Add more tests. (Yegappan Lakshmanan, closes #5904)
|
|
Problem: Test 29 is old style.
Solution: Turn it into a new style test. (Yegappan Lakshmanan, closes #4370)
|
|
Problem: Test files have inconsistant modelines.
Solution: Don't set 'tabstop' to 2, use 'sts' and 'sw'.
|
|
Problem: When running tests $HOME/.viminfo is written. (James McCoy)
Solution: Add 'nviminfo' to the 'viminfo' option. (closes #722)
|
|
Problem: Setting 'compatible' in test influences following tests.
Solution: Turn 'compatible' off again.
|
|
|