| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
Previously, prune("wiki/srcdir/sandbox/test.mdwn") could delete srcdir
or even wiki, if they happened to be empty. This is rarely what you
want: there's usually some base directory (destdir, srcdir, transientdir
or another subdirectory of wikistatedir) beyond which you do not want to
delete.
|
|
|
|
|
| |
This does not change the number of failing tests I see, but it does
make it show the expected result, which makes analysis easier.
|
|
|
|
|
|
| |
This ensures that when we do the second phase of the test (edit some
files and refresh), the changes get a different mtime and are picked up,
even if the entire test happened between two 1-second "clock ticks".
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
for writing more thorough tests, in order to safely extract the
cvsps output-parsing routine for reuse by an upcoming rcs_revert().
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Extract cvs_keyword_subst_args() and ensure it runs in $config{srcdir}.
Using Perl's -T operator appears to work equally well, perhaps switch?
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
a bunch more tests (that wind up exercising rcs_commit(),
rcs_commit_staged(), and rcs_recentchanges()). Extract some support
routines for brevity. Most is_in_keyword_substitution_mode() tests
are commented out because there's a bug -- non-binary files are
being added with "cvs add -kb".
Move tests that inspect recentchanges after direct CVS operations
into test_rcs_recentchanges().
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the code:
* general plugin API calls (in plugins/write order),
* VCS plugin API calls (in plugins/write order), then
* internal support routines (in alphabetical order).
In the tests:
* general meta-behavior (in no particular order, yet),
* general plugin API calls (in plugins/write order),
* VCS plugin API calls (in plugins/write order), then
* internal support routines (in semi-logical order).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Add setup and teardown methods, called before and after every test sub.
* In setup, make a fresh repo; in teardown, throw it out.
* Extract runtests method and define default test methods at top.
* Move reflection routines near the xUnit-style subs they support.
Adapt existing test subs to run independently:
* In test_manual_add_and_commit(), assume a fresh repo.
While here, plan a bit better:
* Check for all modules used by cvs.pm.
* Check for program existence more generally.
* Check that we can rmdir after mkdir.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Run all subs matching /^test_*/ (for which we can plan)...
* Unless TEST_METHOD is set, in which case run matching subs (sans plan).
* Define total number of tests very near 'use Test::More', where expected.
* Define test tempdir where it's declared, no longer any reason why not.
* Move most comments from TODO.cvs into t/cvs.t.
* Add a whole bunch more comments describing the needed test cases.
XXX existing tests are order-dependent, but currently happen to pass
|
| |
| |
| |
| | |
While here, nitpick style and wrap long lines.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Call readfile() directly from writefile().
* Parameterize commit message for the web-commit case.
* Describe intent of test cases.
* Rename test subs to match what they actually do.
* To prove extra path slashes don't cause trouble, instead of running
the same tests a second time, just assert that checkconfig()
strips the slashes.
|
| | |
|
| |
| |
| |
| |
| |
| | |
the test plan at runtime. Use IkiWiki unconditionally too (as that's
not what I'm testing here) to avoid the TAP error of printing a
test result before having printed the plan.
|
| |
| |
| |
| | |
No functional change intended.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the first test, discount returns the html attributes in a different
order, which broke the test. Test only for the important text, not the
exact html output.
In the second test, discount does some encoding of its own of the partially
encoded url, again resulting in different output.
|
| |
| |
| |
| |
| |
| | |
These correspond to title and title_natural, but compare the entire
path: a < a/b < a/z < ab < b.
(cherry picked from commit 903a5a314f1f5d833dbc208ce128f24195b40e4b)
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
These correspond to title and title_natural, but compare the entire
path: a < a/b < a/z < ab < b.
|
|/ |
|
|
|
|
| |
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
|
|
|
|
|
|
|
| |
date Columbus discovered America. Closes: #640350
This is such a pity. smcv had these great dates, but squeeze's Date::Parse
cannot parse them.
Oh well, at least it makes for a great bug closure title.
|
| |
|
|\ |
|
| |
| |
| |
| | |
... additionally to the previously supported two-letters codes.
|
|/
|
|
|
|
|
| |
been fixed
hurrah! Thanks especially to Niko Tyni for tracking it down in the perl
internals.
|
| |
|
| |
|
| |
|
|
|
|
| |
Want to avoid debug messages during tests
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
t/tag.t
|
| | |
|
| |
| |
| |
| | |
For the moment, have the tag test keep the old behaviour.
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | | |
As with the tag plugin, for the moment keep the old behaviour in the test.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Migrate the set of deletions to the {autofile} set, since it has
more or less the same effect. This affects the "deleted" case in the
test.
- If a page has just been deleted, add it as an autofile anyway: by
the time gen_autofile is called, it'll be in the list of deleted files,
so it'll just be added to {autofile}. This affects the "gone" case
in the test.
- Behaviour change: we don't forget that a page with no reason to be
re-created was deleted. This affects the 'expunged' and 'reinstated'
cases in the test.
|
| | |
| | |
| | |
| | | |
autofiles
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This does cause a minor regression: index pages are now committed
individually rather than being a single commit per rebuild.
This also means the autoindex regression test needs to trigger the
autofile generation pass.
|
| | | |
|
| | | |
|