> > Christian Brabandt wrote: > > > On Do, 21 Jul 2016, Bram Moolenaar wrote: > > > > > Patch 7.4.2088 > > > Problem: Keymap test fails with normal features. > > > Solution: Bail out if the keymap feature is not supported. > > > Files: src/testdir/test_digraph.vim > > > > Thanks. Coverage for digraph.c went up to 93%. I would say, this is > > okay, although disappointing, that overall coverage hasn't grown much, > > only to some 65% > > Vim has many lines of source code, so that is to be expected. > > On coverals you can click on the "not covered" column to sort files by > the largest number of missed lines. Then you know where you can make > most impact. > > Although another approach is to stick with one feature and find lines > that are still missed. This may not make much impact on the percentage, > but it's easier to write a test for a feature you were already working > on. E.g., for digraph.c there are some errors that are not encountered. > Writing a test, using assert_fails() to check that the error condition is > detected, is useful.
Is there an easy way to detect, on which lines coverage has been added, if I compare two builds? I suspect testing gui features won't work easily, so coverage for the gui_ files will stay low. Hm, arabic could need a test. Unfortunately, I don't know arabic... I'll see, if I can add some more tests. I wanted to add a test for the different completions and using the keys . I think, that is missing as well. Best, Christian -- Windows98: 98 Fehlermeldungen pro Minute. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
