[
https://issues.apache.org/jira/browse/SCM-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959932#comment-17959932
]
ASF GitHub Bot commented on SCM-17:
-----------------------------------
jira-importer commented on issue #280:
URL: https://github.com/apache/maven-scm/issues/280#issuecomment-2964582921
**[Mike
Perham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mperham)**
commented
I've found that when you enter a broad, open-ended type of issue like this,
it tends to be pushed off version after version. I suggest closing this issue
and in the future, open specific issues per provider.
> test structure needs further clean up
> -------------------------------------
>
> Key: SCM-17
> URL: https://issues.apache.org/jira/browse/SCM-17
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Test
> Components: maven-scm-provider-clearcase, maven-scm-provider-cvs,
> maven-scm-provider-local, maven-scm-provider-perforce,
> maven-scm-provider-starteam, maven-scm-provider-svn
> Reporter: Brett Porter
> Priority: Major
>
> The following is needed:
> - all providers need to utilise the TCK where possible.
> - any tests in providers that can be generalised should be moved to the TCK
> - other tests in the providers should just test provider specific functions,
> and probably not be integration tests like the TCK is
> - need further tests for other commands, including those yet to be added
> - review coverage for each provider
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
