IS480 Team wiki: 2013T1 Kungfu Panda Software Testing
As part of our Usability X-Factor, we have used rigorous software testing. There are 2 types - SOAPUI Testing for Back End Services and HTMLUnit Testing for End to End Testing.
Back End Services Testing with SOAP UI
Test integrity of back end SOAP services by passing in pre-defined input and comparing it with expected output.
We have put together 2 SOAPUI Projects that contain pre-defined SOAP requests which we can use to invoke the back end services.
The image below shows a screenshot of a SOAPUI Project, and by invoking the Transaction_Deposit_Create service, the SOAP Response contains "invocation successful", indicating the back end service is up and running properly.
We have 30 SOAPUI Test Cases. 17 of which are for the services which our team has built. 13 of which are for the services which we have integrated in our Branch Teller Web Application but was built by other FYP teams or the SMU tBank ESB team.
Follow Up Action:
Any bugs or failures in the test cases will immediately be logged in our bug tracker and developers will be notified.
End to End Testing with HTMLUnit
Test functions on User Interface that runs automated test codes. This ensures existing software quality and also sustainability such that a red flag will go off if future modifications break existing features.
Our group will use the JUnit framework built within NetBeans 7.3 as a base and have imported HtmlUnit V2.13 as an external library to perform tasks in a headless browser. These tests are written in Java and can be run from NetBeans
Follow Up Action:
Any bugs or failures in the test cases will immediately be logged in our bug tracker and developers will be notified. Also, our group carried out manual testing from the UI itself to cover the remaining 9 cases.