This is an automated email from the ASF dual-hosted git repository.

fanningpj pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-pekko-connectors.git


The following commit(s) were added to refs/heads/main by this push:
     new e6f427819 add advice on how to run tests (#322)
e6f427819 is described below

commit e6f427819ab2f08f6f36bdbeb0abfe87b79cf324
Author: PJ Fanning <[email protected]>
AuthorDate: Tue Jan 23 10:20:09 2024 +0100

    add advice on how to run tests (#322)
    
    * add advice on how to run tests
    
    * Update README.md
    
    * Update README.md
    
    * Update CONTRIBUTING.md
    
    * Update README.md
---
 CONTRIBUTING.md | 27 ++++++++++++++++++++++-----
 README.md       | 14 +++++++++++++-
 2 files changed, 35 insertions(+), 6 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index c572ea51b..54ea4fa68 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -6,11 +6,7 @@ You're always welcome to submit your PR straight away and 
start the discussion (
 
 # The Pekko Community
 
-If you have questions about the contribution process or discuss specific 
issues, please interact with the community using the following resources.
-
-- [GitHub discussions](https://github.com/apache/incubator-pekko/discussions): 
for questions and general discussion.
-- [Pekko dev mailing 
list](https://lists.apache.org/[email protected]): for Pekko 
development discussions.
-- [GitHub issues](https://github.com/apache/incubator-pekko/issues): for bug 
reports and feature requests. Please search the existing issues before creating 
new ones. If you are unsure whether you have found a bug, consider asking in 
GitHub discussions or the mailing list first.
+If you have questions about the contribution process or to discuss specific 
issues, we will be happy to try to help via the usual [communication 
channels](https://github.com/apache/incubator-pekko-connectors?tab=readme-ov-file#community).
 
 
 # Contributing to Pekko Connectors
 
@@ -31,6 +27,27 @@ This is the process for committing code into main.
 
 1. If the branch merge conflicts with its target, rebase your branch onto the 
target branch.
 
+## Running tests
+
+| :exclamation:  Take care when running the shell scripts in this repo. |
+|-----------------------------------------------------------------------|
+
+You can run tests using [sbt](https://www.scala-sbt.org/). With this repo, you 
will typically be working on one connector at a time. For instance, the FTP 
connector is in the `ftp` folder and you can run its tests with `sbt ftp/test`. 
You should read the rest of this section before running these tests.
+
+This repo is for connectors that integrate with 3rd party services (e.g. AWS 
S3, FTP, Hive). For many connectors, you will need to use [Docker 
Compose](https://docs.docker.com/compose/) to start servers that the Pekko 
Connector tests will need to interact with. The tests don't expect to interact 
with live resources but instead expect to work with local services that provide 
the right functionality.
+
+You can get an idea of what Docker commands that you need to run tests for 
specific connectors by looking at the GitHub Actions workflow 
[check-build-test.yml](https://github.com/apache/incubator-pekko-connectors/blob/75e9a4867eec3e1c2b971eb7e13a0f0b9dbddab3/.github/workflows/check-build-test.yml#L78-L125).
+
+The Docker setup in many cases requires the use of shell scripts that are 
designed to run inside Docker containers and are not designed for users to be 
running on their own machines. Please take care when running any shell scripts 
in this repo.
+
+To continue with the FTP connector as an example, you will need to run this 
[script](https://github.com/apache/incubator-pekko-connectors/blob/main/scripts/ftp-servers.sh)
 (that runs Docker Compose commands) before running the tests.
+
+```
+./scripts/ftp-servers.sh
+```
+
+This FTP setup does not work well on Apple Macs. There is a workaround 
described by Sebastien Alfers in this [write 
up](https://github.com/sebastian-alfers/commons-net/blob/1cd10e1da577d5f900c5e33af2a041de1361eb25/README_REPRODUCE.md#squid--ftp-on-mac).
+
 ## Pekko Connectors specific advice
 
 We've collected a few notes on how we would like Pekko Connectors modules to 
be designed based on what has evolved so far.
diff --git a/README.md b/README.md
index 2d8febb0b..8a17c563a 100644
--- a/README.md
+++ b/README.md
@@ -13,10 +13,22 @@ Pekko Connectors is a fork of 
[Alpakka](https://github.com/akka/alpakka) 4.0.0,
 
 ## Documentation
 
-Pekko Connectors are documented at 
https://pekko.apache.org/docs/pekko-connectors/current/.
+Apache Pekko Connectors are documented at 
https://pekko.apache.org/docs/pekko-connectors/current/.
 
 To keep up with the latest releases check out [Pekko Connectors 
releases](https://github.com/apache/incubator-pekko-connectors/releases) and 
[Pekko Connectors Kafka 
releases](https://github.com/apache/incubator-pekko-connectors-kafka/releases).
 
+## Building From Source
+
+The build commands in the 
[incubator-pekko](https://github.com/apache/incubator-pekko?tab=readme-ov-file#building-from-source)
 repo are also useful here. Java 8 should work well for building from source 
with this repo. Building the Paradox docs is significatntly harder if you use 
Java 17 or above. You will need to specify a large number of `--add-opens` 
settings.
+
+This repo contains shell scripts. These scripts are designed to help with the 
testing of Apache Pekko Connectors. Please avoid running the scripts without 
checking if you need to and try to understand what the script does first.
+
+There is also a `nested-sample.tar` file that is used in tests. This tar file 
does not contain compiled artifacts.
+
+## Running Tests
+
+There are details in the [Contributing 
page](https://github.com/apache/incubator-pekko-connectors/blob/main/CONTRIBUTING.md).
 That page also has guidelines about how to prepare Pull Requests.
+
 ## Community
 
 You can join these forums and chats to discuss and ask Pekko and Pekko 
connector related questions:


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to