Introduction

The ParaBank demo web application and associated web services (SOAP and REST) from Parasoft.

Build and Install

1. Build the ParaBank application using Maven (mvn clean install). After a successful build, deploy the parabank.war (located in /target) into an Apache Tomcat 8.5.11 container.

NOTE: if using the coverage agent when running the functional/manual tests (see below), execute the build using "mvn -Dmaven.test.skip=true clean install jtest:monitor"

1. ParaBank uses a built-in HyperSQL database. You must shut down all running instances of ParaBank and HyperSQL for the build to succeed Otherwise several tests may fail, since there are a number of ports that are shared between the test instances and the real thing.

Apache Tomcat notes

1. The minimum Java JDK version is 1.8.0. Oracle JDK is preferred.

2. The minimum Apache Tomcat version is now 8.5.11.

3. The version was validated against both Apache Tomcat 8.5.11 and 9.0.M10.

4. At the time of this writing the version of 9.0 tested was M10 (emphasis on M meaning milestone and therefore unstable).

5. To prevent verbose cache warnings in the tomcat log::

Oct 06, 2016 3:53:33 PM org.apache.catalina.webresources.Cache getResource
WARNING: Unable to add the resource at [/WEB-INF/lib/wss4j-ws-security-stax-2.1.3.jar] to the cache because there was insufficient free space available after evicting expired cache entries - consider increasing the maximum size of the cache

Add the following to the <tomcat install>/config/context.xml make sure to place this block before </Context> tag. This setting will provide 100 MB for caching

<Resources cachingAllowed="true" cacheMaxSize="102400" />

1. To support clean re-deployments of ParaBank please add the following to the <Context> tag of the <tomcat install>/config/context.xml

<Context antiResourceLocking="true">

Test scripts

• All scripts exist in two flavors (.bat and .sh) for Windows and Linux respectively.
• All scripts should be executed from project directory and require the following Parasoft products (and versions) ** Parasoft DTP 5.3.2 ** Parasoft Jtest 10.3.2 ** Parasoft SOAtest 9.10.1

Script	Description
deploy-jtest-monitor(.sh|.bat)	Deploys the Jtest Monitor package (created using mvn goal jtest:monitor) into directory specified by APP_COVERAGE_DIR in `set-vars(.sh
jtest-ft-cov(.sh|.bat)	Executes Parasoft Jtest DTP Engine for processing monitored coverage during functional testing with SOAtest
jtest-mt-cov(.sh|.bat)	Uploads results from manual testing efforts (managed using the Parasoft Coverage Agent Manager) and processing coverage data captured during manual testing
jtest-sa-ut(.sh|.bat)	Executes Parasoft Jtest DTP Engine for Static Analysis and Unit Testing results/coverage
jtest-sa-ut-delta(.sh|.bat)	Same operation as `jtest-sa-ut(.sh
set-vars(.sh|.bat)	Utility script called by other scripts to consistently set BUILD_ID and the Project name sent to DTP
soatest(.sh|.bat)	Executes Parasoft SOAtest API and Web functional tests (including integration with Jtest DTP Engine for monitoring code coverage)

Setup

set-vars.(.sh|.bat): setup JTEST_HOME and SOATEST_HOME environment variable before running any script. all reports will be stored under target/report/ directory. on Windows, 7zip must be installed (default to C:\Program Files\7-zip) to run deploy-jtest-monitor.bat script.