About Trapeze Test Procedures

Objective of the Tests

The objective of the tests performed on Floodgate Messaging is to check if it operates fully in the manner described in the Design and Specifications document.

Testing Staff

The Traveler Experience - DR QA team holds the main responsibility for software testing. They perform smoke testing, in depth feature/function, and regression testing for both the main (generic) and custom components of the software.

The developers perform testing as they create or fix the software before committing their changes to the repository while the assigned Professional Services and Delivery staff together with the customers are expected to test the application when they install/upgrade and configure it at a customer site.

Testing Environment and Resources

The QA team endeavors to perform the testing in an environment that contains all the necessary components in order to send out notifications successfully. These include the operating systems, release build and markup versions, database versions, server configuration, and integration with third party communications services.

Browser compatibility: Floodgate Messaging has been tested and determined to work with Google Chrome, Microsoft Edge, Mozilla Firefox, and Apple Safari.

Twilio account: During the development of Floodgate Messaging, a mock server was set up to test the scheduling and sending of Floodgate notifications.

To fully test the software later, the QA team set up accounts with Twilio, the third party cloud communications platform which Floodgate Messaging currently uses to send the notifications by phone.

After installation at a transit site, we performed a demo test in cooperation with the customer to more than 2,000 of their subscribers. The test ran successfully and yielded helpful information for enhancing the product. Running demo tests will be standard practice after each site installation is completed.

We recommend that customers who have Floodgate Messaging regularly perform similar demo tests at least once every quarter of the year.

Test Cases

The test cases cited in this document were developed by the QA team.

As of the publication of this document, the development team is working on automating the tests for the different Floodgate Messaging services and components.

Test Results

The tests result are either a Pass or a Fail. In general terms, a Pass is when the test case was executed and the expected result occurred under certain conditions while a Fail means that the test could not be completed or was executed but did not produce the expected result.

If Passed

If the tests are successfully passed, the candidate build that was tested is promoted to a release build, which is posted in the build repository.

If Failed

In case of failure or blockers are found during testing, tickets are created in Jira, a project management software used to track and manage development work assignments. The issue is reviewed and if confirmed as an issue, assigned to the appropriate development team member.

After the issue is fixed and committed to a candidate build, the test cases are run again. The candidate build is promoted to a release build when the testing is successfully completed.