suneet-s commented on a change in pull request #9560: Instructions to run 
integration tests against quickstart
URL: https://github.com/apache/druid/pull/9560#discussion_r398082242
 
 

 ##########
 File path: integration-tests/README.md
 ##########
 @@ -66,7 +66,40 @@ Integration tests can also be run with either Java 8 or 
Java 11 by adding -Djvm.
 can either be 8 or 11.
 
 Druid's configuration (using Docker) can be overrided by providing 
-Doverride.config.path=<PATH_TO_FILE>. 
-The file must contain one property per line, the key must start with druid_ 
and the format should be snake case. 
+The file must contain one property per line, the key must start with `druid_` 
and the format should be snake case. 
+
+Running Tests Using A Quickstart Cluster
+-------------------
+
+When writing integration tests, it can be helpful to test against a quickstart
+cluster so that you can set up remote debugging with in your developer
+environment. This section walks you through setting up the integration tests
+so that it can run against a quickstart cluster running on your development
+machine.
+
+Note that not all features run by default on a quickstart cluster, so it may
 
 Review comment:
   @maytasm3 I was worried about what you mentioned as a top level comment on 
this PR too. I tried to talk about it here, but maybe the warning is not big 
and scary enough. Any suggestions on how to make it more prominent? Also I 
wonder if I should point to the docker setup scripts for the next person who 
might find a test that fails when run against quickstart.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

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

Reply via email to