[Cyberduck-trac] [Cyberduck] #9929: Running the Test Suite

[Cyberduck]

#9929: Running the Test Suite
-------------------------------------------------+-------------------------
 Reporter:  tjcelaya                             |         Owner:
     Type:  enhancement                          |        Status:  new
 Priority:  normal                               |     Milestone:
Component:  documentation                        |       Version:  Nightly
                                                 |  Build
 Severity:  normal                               |    Resolution:
 Keywords:  readme documentation build building  |  Architecture:
  test suite                                     |
 Platform:  macOS 10.12                          |
-------------------------------------------------+-------------------------
Description changed by tjcelaya:

Old description:

> Hey there, been using Cyberduck for a long time and am preparing to
> contribute. Unfortunately I've had some trouble running the test suite.
> After going over the readme and looking into MDEP-187 I realized this
> wasn't a problem with Cyberduck but stems from the way Maven organizes
> modules. It would probably help other developers getting started if this
> were addressed in the readme.
>
> I was able to get the suite running by invoking `mvn package` in each
> project that threw the error and then rerunning `mvn test -DskipITs`
> until the build was successful, on OS X this list emerged:
>
> * `core`
> * `core/dylib`
> * `bonjour`
> * `importer`
> * `protocols`
> * `osx`
> * `cli/osx`
>

> Additionally, there are a handful of tests seem to be failing as a result
> of a missing IntegrationTest annotation. Most of these have been
> corrected as of this morning, but these last two that are still unmarked
> as of submitting this ticket:
>
> * S3SearchFeatureTest.search:52 » LoginFailure Listing directory /
> failed.
> * OneDriveSharingLinkUrlProviderTest>AbstractOneDriveTest.setup

New description:

 Hey there, been using Cyberduck for a long time and am preparing to
 contribute. Unfortunately I've had some trouble running the test suite.
 After going over the readme and looking into MDEP-187 I realized this
 wasn't a problem with Cyberduck but stems from the way Maven organizes
 modules. It would probably help other developers getting started if this
 were addressed in the readme.

 I was able to get the suite running by invoking `mvn package` in each
 project that threw the error and then rerunning `mvn test -DskipITs` until
 the build was successful, on OS X this list emerged:

 * `core`
 * `core/dylib`
 * `bonjour`
 * `importer`
 * `protocols`
 * `osx`
 * `cli/osx`


 Additionally, there are a handful of tests which seem to be failing as a
 result of a missing IntegrationTest annotation. Most of these have been
 corrected as of this morning, but these last two that are still unmarked
 as of submitting this ticket:

 * S3SearchFeatureTest.search:52 » LoginFailure Listing directory / failed.
 * OneDriveSharingLinkUrlProviderTest>AbstractOneDriveTest.setup

--

--
Ticket URL: <https://trac.cyberduck.io/ticket/9929#comment:2>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows