Falco created VFS-740:
-------------------------
Summary: WebdavVersioningTests are not executed regularly and
failing
Key: VFS-740
URL: https://issues.apache.org/jira/browse/VFS-740
Project: Commons VFS
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Falco
Tests which are named {{*Tests.java}} are not executed by the Surefire version
in use:
https://maven.apache.org/surefire-archives/surefire-2.19.1/maven-surefire-plugin/examples/inclusion-exclusion.html
This is not a problem as long as these classes are contained in test suites.
However, there are instances of {{*Tests}} classes which are not in suites, and
which subsequently are _not_ executed during {{mvn test}}.
* {{DefaultFileMonitorTests}}, which I will mention / fix during VFS-299
* The test class {{WebdavVersioningTests}} is not executed and has two failing
test methods after adding it to a suite, e.g., in
{{WebdavProviderTestCase#suite}}. The {{WebdavProviderTestSuite}} is currently
not used and looks like a duplicate of {{ProviderTestSuite}}.
These are my findings after finding out that I could arbitrarily mutate
{{DefaultFileMonitorTests}} without making {{mvn test}} report errors. I think
my analysis is exhaustive.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
