Cyberduck Mountain Duck CLI

#9929 closed enhancement (fixed)

Running the Test Suite

Reported by: tjcelaya Owned by:
Priority: normal Milestone:
Component: documentation Version: Nightly Build
Severity: normal Keywords: readme documentation build building test suite
Cc: Architecture:
Platform: macOS 10.12

Description (last modified by tjcelaya)

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:

  • » LoginFailure Listing directory / failed.
  • OneDriveSharingLinkUrlProviderTest>AbstractOneDriveTest.setup

Change History (5)

comment:1 Changed on May 8, 2017 at 8:52:33 PM by tjcelaya

  • Description modified (diff)

comment:2 Changed on May 8, 2017 at 8:52:59 PM by tjcelaya

  • Description modified (diff)

comment:3 Changed on May 9, 2017 at 6:27:19 AM by dkocher

I will see that we can add better documentation and I must have hit MDEP-187 myself, as the link is marked as visited in my browser (…).

comment:4 Changed on May 9, 2017 at 6:30:54 AM by dkocher

  • Resolution set to fixed
  • Status changed from new to closed

Added missing integration test annotation in r39331 and r39332.

comment:5 Changed on May 9, 2017 at 7:06:48 AM by dkocher

Clarify documentation in r39333.

Note: See TracTickets for help on using tickets.