Some misc. thoughts:

AppsodyBinaryProjectTest

1. Where is the source for this tango war? Is it versioned with a maven release? Should we clone it into this project?
2. Does the dflt URL path test the JDBC connection? Seems that's a key thing to test.

• If not, we could either add that to the app source, OR another approach would be using the validation-1.0 feature (Liberty analogue to TWAS "testConnection").

appsody-projects

1. We should reflect in the README and possibly the repo name when we init'd this from like: java-openliberty-init-at-0-2-5-appsody-0-6-0 (OK maybe just the README).

other

1. Not urgent but maybe better to use the 'exit' code instead of grepping success messages to pass back success vs. failure?

Good we have options, but for your typical user it might be:

Verify setup

1. make sure you have a dev.local built: appsody stack package
2. git clone
3. cd src
4. ./stack-regression.sh

Fix stack, verify

1. changes, appsody stack package
2. cd src; ./stack-regression.sh

1. In stopDockerRun() no need to do: docker container rm $1 if we run with --rm flag like I added

2. The failure log test.log gets written to the working dir, however stack-regression.sh
   says it's in "/tmp/$1/test.log"

echo "!!!!!!!!!!!!!!!!!!!!!!!!!!"
echo "Test of $1 failed!"
echo "Log can be viewed at /tmp/$1/test.log"
echo "!!!!!!!!!!!!!!!!!!!!!!!!!"