[
https://issues.apache.org/jira/browse/SCM-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964413#comment-17964413
]
Olivier Lamy commented on SCM-160:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#448|https://github.com/apache/maven-scm/issues/448].
> Refactored tck tests, added changelog tck test and added changelog, diff test
> for the bazaar provider
> -----------------------------------------------------------------------------------------------------
>
> Key: SCM-160
> URL: https://issues.apache.org/jira/browse/SCM-160
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-bazaar
> Affects Versions: 1.0-beta-3
> Environment: Tested on WinXp and Linux for cvs, svn and bazaar
> Reporter: Torbjorn Eikli Smorgrav
> Assignee: Torbjorn Eikli Smorgrav
> Priority: Major
> Fix For: 1.0-beta-3
>
> Attachments: MNG-160-maven-scm-provider-bazaar.patch,
> MNG-160-maven-scm-test.patch, MNG-160_2-maven-scm-test.patch
>
>
> Short summary: Refactored code into a new baseclass: ScmTckTestCase. Added
> tests to Bazaar.
> Working with my bazaar tests I found out that the tck test module had some
> redundant code.
> So I took the liberty to refactor the tck package a bit before I added the
> final tests to the bazaar provider.
> I tested the refactored test module with cvs, svn and bazaar on WinXp and
> Linux.
> (Bazaar had trouble with linux and bazaar 0.6, but that turned out to be a
> Bazaar bug that was fixed in post 0.6 versions of Bazaar)
> The refactoring consist mainly of centralizing duplicated blocks of code into
> a new test base class: ScmTckTestCase. And
> using a common setUp() method for all tck tests.
> If you find this class ok - then you will most likly find the rest ok.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
