Skip to content

Commit fb3322d

Browse files
authored
Merge pull request #1043 from yeweidaniel/integration-doc2
Update docs
2 parents 02d8989 + 32745ce commit fb3322d

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

README.rst

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,12 @@ instantiated in a similar manner::
2626
ApplicationClient appClient = new ApplicationClient(getClientConfig(), getRestClient());
2727
appClient.list(new NamespaceId("myns"));
2828

29-
If the artifacts being tested are under development, they should be loaded into the target CDAP instance prior to starting the test.
29+
If the artifacts being tested are under development, they should be loaded into the target CDAP instance prior to starting the test. If these artifacts are loaded into CDAP through the UI, they will exist under ``USER`` scope, so in the tests they should be referred to accordingly.
30+
31+
Debugging in IntelliJ
32+
-------------
33+
34+
Go to Run -> Edit Configurations -> JUnit Test, in VM Options add the options from the section below. For example ``-DinstanceUri=http://localhost:11015 -DprogramTimeout=120``
3035

3136
Running Tests
3237
-------------
@@ -65,6 +70,12 @@ If the test has dependencies on GCP components, add the following property::
6570

6671
-Dgoogle.application.credentials.path=<PathToCredentialFile>
6772

73+
Note that if you get a Timeout from ETLTestBase.setup, its likely that the plugins you are testing have not been loaded into the CDAP instance. To load the standard set of plugins, clone the Hydrator Plugins repo at https://github.com/cdapio/hydrator-plugins, then run::
74+
75+
git submodule update --init --recursive --remote
76+
mvn clean package -DskipTests
77+
78+
Once done, build the CDAP instance by adding ``-Dadditional.artifacts.dir=</path/to/plugins/dir>`` when packaging CDAP.
6879

6980
CDAP Upgrade Tests
7081
------------------

0 commit comments

Comments
 (0)