Review Request: Black-box test for (D)VCS-plugins
Fabian Wiesel
fabian.wiesel at googlemail.com
Wed Mar 25 07:44:15 UTC 2009
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard.kde.org/r/384/
-----------------------------------------------------------
(Updated 2009-03-25 00:44:15.334182)
Review request for KDevelop.
Changes
-------
- Use TestCore instead of Core
- Link against testshell instead of the standard shell
- Added initialisation steps for a local CVS repository
Should the test rather be placed in a kdevplatform/tests/vcs directory instead of the newly created kdevplatform/vcs/tests?
Summary
-------
Tests the various plug-ins on consistency. Currently works with Subversion and Mercurial. CVS needs to be changed to allow local repositories.
Currently checks:
All: isVersionControlled(), status(), add(), revert(), commit()
DVCS: init()
The test also codifies a proposal of the expected behaviour of the interfaces, which would be the common denominator of Subversion and Mercurial.
Because of that, I thought, I'd rather let this be reviewed, before spending more time on implementing more test-cases, which codify an unwanted behaviour.
Diffs (updated)
-----
/trunk/KDE/kdevplatform/vcs/CMakeLists.txt 944152
/trunk/KDE/kdevplatform/vcs/tests/CMakeLists.txt PRE-CREATION
/trunk/KDE/kdevplatform/vcs/tests/vcsBlackBoxTest.h PRE-CREATION
/trunk/KDE/kdevplatform/vcs/tests/vcsBlackBoxTest.cpp PRE-CREATION
Diff: http://reviewboard.kde.org/r/384/diff
Testing
-------
Excluding CVS and Git:
1/ 1 Testing vcsBlackBoxTest Passed
100% tests passed, 0 tests failed out of 1
Thanks,
Fabian
More information about the KDevelop-devel
mailing list