Hi, On Thu, May 3, 2018 at 8:11 AM, Jason Franklin <[email protected]> wrote: > I'm writing two new tests for a patch that fixes a bug with the ":close" > command. There is already a file for testing the various commands that close > a buffer/window (see "src/testdir/test_winbuf_close.vim"). > > My questions are: > > Should new tests always be placed in their own file to isolate their > environment? >
No. If all the tests related to a particular feature are in the same file, It is simpler to test the feature by running a particular test. If the tests are dispersed in multiple files, it is difficult to do this. > > Are tests in the same file run in the same Vim process? Can I override this? > The test can start a new Vim instance and run the test. > > When is it okay to keep tests in the same file? When is it not okay? Is there > a general rule to follow? > See above. - Yegappan -- -- 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.
