Pre-Deployment Testing

Overview

This testing outline should be followed step-by-step before any changes are made to the Gateway production deployment. The purpose is simply to prevent bugs from surfacing in production that may cause undesired function and possible loss/corruption of production data. Testing should be conducted by following the steps listed here in sequence using the latest to-be-deployed code.

Building

  • To make sure that all the latest code will be compiled to produce the most current version of the Gateway the following steps must be taken: (A more detailed guide is available here )
    Delete the local Maven repository in your home directory. For Windows users the path to the repository is
    C:\Documents and Settings\(username)\.m2\repository , for Linux users it will be /home/(username)/.m2/repository .
    For Eclipse, with the Maven plugin, right click on the project's top-level pom.xml and select Run As and then
    Maven clean . Once the clean is finished, select Maven install from the same menu as Maven clean . In Linux simply run
    mvn clean install in the base project directory.
    While the build is running JUnit tests will be run for each module. If the build fails due to a test failure the test in
    the failed module must be examined to determine the cause for failure and fixed before deployment.
    If the build completes without error the .ear file in (basedir)/packaging/gateway-ear-jboss/target/ should be ready
    to be deployed

Setup

  • In order to test the Gateway it must be deployed on either the localhost or a test server. The guide for JBoss in Eclipse located here should be sufficient for information on deploying the Gateway if a test server has not been setup elsewhere. It is important that wherever the test server is setup, someone has run the configuration script to load in the test user accounts we will be dealing with. This script is located at http://(test server address)/test/configure-users.jsp .

Selenium

  • Selenium is a Firefox Addon that allows a file to be loaded in that describes actions to navigate through a web site. Many tests have an additional Selenium test file you may download and run to automate the browser based testing and verification of results. Selenium setup and usage are described on this page .

Tests

  • The following table contains a link to each test page and a description of the type of test.
    Type Test Description
    Portal Administrator Role Log in as administrator and add a new transmitter.
    Portal Transmitter Role Log in as transmitter and test authentication and transmitter actions.
    Portal Tax Staff Role Log in as tax staff and test tax staff operations.
    Portal Security Use the client to validate transmissions, acknowledgements, and receipts.
    Client Communication Use the client to conduct test sends, acknowledgements, and last acknowledgements.
    Client Validation Use the client to validate transmissions, acknowledgements, and receipts.