Review Request: Black-box test for (D)VCS-plugins
Robert Gruber
R.Gruber at gmx.net
Mon Mar 23 14:49:59 UTC 2009
Hi,
I coincidentally came across this post and was wondering what the problem with CVS was?
During development of the CVS plugin I used a local CVS repository by my self and never had any problems. When I last used my CVS plugin a few month ago KDevelop still worked fine with the local CVS repo. I guess not much has changed since then ;)
Maybe I can help you out on how to call the CVS plugin so it works for the test? What exactly was the problem?
I took a glimpse at the testcase and was wondering that no call to import() is in there? How do you set up the repository?
There is a small testcase for cvs-plugin's internal classes at:
http://websvn.kde.org/trunk/KDE/kdevplatform/plugins/cvs/tests/cvstest.cpp?view=markup
Although it tests the internal CvsProxy class and not the interface it might give you a hint on how to setup a local repo.
If you have any further questions I'll be happy to help.
Greets, Robert
-------- Original-Nachricht --------
> Datum: Sun, 22 Mar 2009 10:00:43 -0000
> Von: "Fabian Wiesel" <fabian.wiesel at googlemail.com>
> An: "Fabian Wiesel" <fabian.wiesel at googlemail.com>, "KDevelop" <kdevelop-devel at kdevelop.org>
> Betreff: Review Request: Black-box test for (D)VCS-plugins
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://reviewboard.kde.org/r/384/
> -----------------------------------------------------------
>
> Review request for KDevelop.
>
>
> 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
> -----
>
> trunk/KDE/kdevelop/vcs/CMakeLists.txt 942616
> trunk/KDE/kdevelop/vcs/tests/CMakeLists.txt PRE-CREATION
> trunk/KDE/kdevelop/vcs/tests/vcsBlackBoxTest.h PRE-CREATION
> trunk/KDE/kdevelop/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
>
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
--
______________________________
Robert Gruber -=- r.gruber at gmx.net
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01
More information about the KDevelop-devel
mailing list