On 28/07/10 17:07, Bram Moolenaar wrote:
Marc Weber wrote:
I also wonder if a shared document is the best way to do these things.
At least this allows multiple people at the same time making changes.
Most wiki's are not good at that.
If it is versioned then why not ? It can be accessed easily by everyone.
If its not versioned I'd prefer git or mercurial ..
There is a history. Using a versioning system doesn't allow easy
editing, tables, etc.
Comments?
Given that there are tons of different compile configuration of Vim and
tons of operating systems Vim runs on .. calling for some human testers
is nice but will not bring any benefits in the future.
What about setting up a test suite (driven by git or mercurial?)?
There already is a "make test". Extending this is also a good idea.
And perhaps moving slower tests to a separate target, so that one can do
a quick check after building and a more comprehensive test.
I could setup a cron-job which pulls latest tests patches once a day and
runs it on Linux.
I run the tests quite often, this won't catch much more.
If we used Ruby test suites it can be run easily on all major OS
systems.
I can't do so today - but within some days.
Comments?
I prefer a Vim-script solution. One problem with this is that one
cannot check what is actually on the display. E.g., to check for the
conceal bugs that have been fixed recently.
I think the problem is severalfold:
- There are the existing tests, which are run automatically by "make
test". Maybe they could be divided in several sets, or maybe not.
- Some of the new feature haven't yet got automated tests. They shouldbe
identified, and tests written if possible.
- Some features might not be amenable to automated tests. Maybe a
standardized set of "manual tets" could be set up (with unambiguous
instructions, and "do you see this" questions at critical points).
- Then there is always live-testing, just using the new version
day-to-day with no specific guidelines. This is less systematic, and may
miss some bugs, but it may also sometimes find bugs nobody had thought
to test.
All these cases can be further divided depending on whether you use
- the latest stable version (currently 7.2.446 b619655b31db 2010-07-12
23:38 +0200)
- the latest beta milestone (currently IIUC 7.3c f766a1c87f69
2010-07-25 20:53 +0200)
- the latest bleeding-edge development build (currently 7.3c
33148c37f3c9 2010-07-28 19:38 +0200, but I don't know if the next push
will arrive within minutes, hours, or days).
Best regards,
Tony.
--
"I'm not under the alkafluence of inkahol that some thinkle peep I am.
It's just the drunker I sit here the longer I get."
--
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
