HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2013T1 Kungfu Panda Software Testing"

From IS480
Jump to navigation Jump to search
 
(14 intermediate revisions by one other user not shown)
Line 49: Line 49:
 
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.
 
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.
 
<br />
 
<br />
[[Image:SOAPUI_Test.png|1027x768px]]
+
[[Image:SOAPUI_Test.png|600x450px]]
 
<br />
 
<br />
 
<br />
 
<br />
Line 55: Line 55:
 
<br />
 
<br />
 
We have 30 SOAPUI Test Cases.
 
We have 30 SOAPUI Test Cases.
17 of which are for the services which our team has built.
+
17 of which are for the services which our team has built, listed in alphabetical order:
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.
+
# Account_Deposit_Create
 +
# Account_Deposit_Read
 +
# Account_Deposit_Update
 +
# Account_Loan_Create
 +
# Account_Loan_CreditApproval
 +
# Account_Loan_Read
 +
# Account_Loan_Update
 +
# Party_AccountList_Read
 +
# Party_Customer_Create
 +
# Party_Customer_Read
 +
# Party_Customer_Update
 +
# Payment_CreditTransfer_Create
 +
# Transaction_Deposit_Create
 +
# Transaction_History_Read
 +
# Transaction_LoanFullRepayment_Create
 +
# Transaction_LoanPartialRepayment_Create
 +
# Transaction_Withdrawal_Create
 +
<br />
 +
<br />
 +
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, listed in alphabetical order:
 +
# Account_Status_Update
 +
# MDM_CustomerTypeList_Read
 +
# MDM_ProductList_Read
 +
# Party_BillingOrgList_Read
 +
# Party_Login_Create
 +
# Party_Login_Read
 +
# Payment_DirectDebitAuthorizationList_Read
 +
# Payment_DirectDebitAuthorization_Create
 +
# Payment_DirectDebitAuthorization_Delete
 +
# Product_LoanFullRepayment_Calculate
 +
# Product_LoanInstallment_Calculate
 +
# Product_LoanPartialRepayment_Calculate
 +
# Product_Parameters_Read
 
<br />
 
<br />
 
<br />
 
<br />
Line 66: Line 98:
  
 
== End to End Testing with HTMLUnit ==
 
== End to End Testing with HTMLUnit ==
 +
'''Objective:'''
 +
<br />
 +
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.
 +
 +
'''Method:'''
 +
<br />
 +
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
 +
<br />
 +
[[Image:htmlunit_test.jpg|800px]]
 +
<br />
 +
<br />
 +
'''Test Cases:'''
 +
<br />
 +
Our team has grouped and identified 21 test cases and our HtmlUnit Tests covers 13 out of the 21 cases. This is due to incompatibility of certain Javascript codes such as Backbone's View and Sortable JS. These 13 test cases includes :
 +
#Teller Login/Logout
 +
#Create Customer
 +
#Create Internet Banking Pin
 +
#Read and Update Customer
 +
#Create Deposit Account
 +
#Create Loan
 +
#Loan Credit Approval
 +
#Transaction Deposit
 +
#Transaction Withdrawal
 +
#Partial Loan Repayment
 +
#Full Loan Repayment
 +
#Bill Payment
 +
#Direct Debit Authorisation
 +
 +
<br />
 +
'''Follow Up Action:'''
 +
<br />
 +
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 8 cases.
 +
<br />
 +
<br />
  
 
== End to End Testing Manually ==
 
== End to End Testing Manually ==
 +
'''Objective:'''
 +
<br />
 +
Manually Tests UI for test cases that are not covered by HtmlUnit Test Cases. This is due to incompatibility that lies in JavaScript and certain JavaScript components with the HtmlUnit library.
 +
 +
'''Method:'''
 +
<br />
 +
Our Group tests the UI to verify that the UI is bug free.
 +
 +
<br />
 +
<br />
 +
'''Test Cases:'''
 +
<br />
 +
Our team has grouped and identified 21 test cases and our Manual Tests covers 8 out of the 21 cases. These 8 test cases includes :
 +
#Admin Tool
 +
#Verify Customer Dashboard
 +
#Manage Customer Deposits
 +
#Update Customer Deposit Account
 +
#Manage Loan Accounts
 +
#View Customer Loan Account
 +
#Read Transaction History
 +
#Credit Approval Simulation
 +
 +
 +
<br />
 +
'''Follow Up Action:'''
 +
<br />
 +
Any bugs or failures in the test cases will immediately be logged in our bug tracker and developers will be notified.
 +
<br />
 +
<br />

Latest revision as of 09:44, 25 November 2013

KP-NewHeader.PNG
Home About Us Project Overview Project Management Testing Project Documents


Informal Testing Deployment Exercise UT 1 UT 2 External UT UAT 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

Objective:
Test integrity of back end SOAP services by passing in pre-defined input and comparing it with expected output.

Method:
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.
SOAPUI Test.png

Test Cases:
We have 30 SOAPUI Test Cases. 17 of which are for the services which our team has built, listed in alphabetical order:

  1. Account_Deposit_Create
  2. Account_Deposit_Read
  3. Account_Deposit_Update
  4. Account_Loan_Create
  5. Account_Loan_CreditApproval
  6. Account_Loan_Read
  7. Account_Loan_Update
  8. Party_AccountList_Read
  9. Party_Customer_Create
  10. Party_Customer_Read
  11. Party_Customer_Update
  12. Payment_CreditTransfer_Create
  13. Transaction_Deposit_Create
  14. Transaction_History_Read
  15. Transaction_LoanFullRepayment_Create
  16. Transaction_LoanPartialRepayment_Create
  17. Transaction_Withdrawal_Create



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, listed in alphabetical order:

  1. Account_Status_Update
  2. MDM_CustomerTypeList_Read
  3. MDM_ProductList_Read
  4. Party_BillingOrgList_Read
  5. Party_Login_Create
  6. Party_Login_Read
  7. Payment_DirectDebitAuthorizationList_Read
  8. Payment_DirectDebitAuthorization_Create
  9. Payment_DirectDebitAuthorization_Delete
  10. Product_LoanFullRepayment_Calculate
  11. Product_LoanInstallment_Calculate
  12. Product_LoanPartialRepayment_Calculate
  13. Product_Parameters_Read



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

Objective:
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.

Method:
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
Htmlunit test.jpg

Test Cases:
Our team has grouped and identified 21 test cases and our HtmlUnit Tests covers 13 out of the 21 cases. This is due to incompatibility of certain Javascript codes such as Backbone's View and Sortable JS. These 13 test cases includes :

  1. Teller Login/Logout
  2. Create Customer
  3. Create Internet Banking Pin
  4. Read and Update Customer
  5. Create Deposit Account
  6. Create Loan
  7. Loan Credit Approval
  8. Transaction Deposit
  9. Transaction Withdrawal
  10. Partial Loan Repayment
  11. Full Loan Repayment
  12. Bill Payment
  13. Direct Debit Authorisation


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 8 cases.

End to End Testing Manually

Objective:
Manually Tests UI for test cases that are not covered by HtmlUnit Test Cases. This is due to incompatibility that lies in JavaScript and certain JavaScript components with the HtmlUnit library.

Method:
Our Group tests the UI to verify that the UI is bug free.



Test Cases:
Our team has grouped and identified 21 test cases and our Manual Tests covers 8 out of the 21 cases. These 8 test cases includes :

  1. Admin Tool
  2. Verify Customer Dashboard
  3. Manage Customer Deposits
  4. Update Customer Deposit Account
  5. Manage Loan Accounts
  6. View Customer Loan Account
  7. Read Transaction History
  8. Credit Approval Simulation



Follow Up Action:
Any bugs or failures in the test cases will immediately be logged in our bug tracker and developers will be notified.