Selenium WebDriver Java Framework Course Limited Time Offer for $20

Selenium WebDriver Java Framework Course Limited Time Offer for $20

 

Print

Why Domain knowledge is Important for Software Test Automation Engineers

Software test automation has already become an important part of software development. No matter the software application is for a small business or for a big enterprise,  when an application grows in functional units and modules, manual testing cannot completely cover all modules in a short period of testing cycle. In addition, in manual testing, human error always exist, so we cannot guarantee that manual testing result is accurate.

When we complete automation testing framework for any software application, the framework can run on any environment repeatedly. In addition, we can integrate automation framework with some monitoring system like Grafana , so that we can display test results directly on a dashboard without logging into the test execution servers. Therefore, any software applications should have robust test automation framework.

Software Domain knowledge is important for Software Test Automation Engineers for the following reasons. 

  • Domain knowledge help engineers break big test automation projects into smaller modules for organizing packages in programming. 
  • Domain knowledge help engineers develop complete test plan for applications. 
  • Domain knowledge help engineer use subject matter expertise for test case development. 
  • Domain knowledge help engineers plan test data for positive and negative test scenarios. 
  • Domain knowledge help engineers understand business logic and workflows easily for any new application that is related to the domain expertise of the engineers. 
  • Domain knowledge help engineers create use case scenarios and diagrams using UML. 
  • Experienced professional certainly have the advantage of a domain and testing experience and they have better understandings of different issues and can deliver the application better and faster.

 

Print

Banking Application Test Cases

Based on the Banking Application Data Model, you can create following test cases. 

As a System Administrator, the user

  • can create a new bank information 
  • can update an existing bank information
  • can activate a new bank
  • can deactivate an existing bank
  • can setup a Bank system administrator
  • can assign a user as a bank administrator
  • can delete a user from the bank administrator user group

 As a Bank Administrator, the user

  • can update bank information
  • can update bank administrator user information
  • can create a new branch information in the system
  • can update an existing branch information
  • can activate a new branch in the system
  • can create branch manager information
  • can delete an existing branch manager

As a Branch Manager, the user

  • can update a branch profile in the system
  • can update branch employee information
  • can create new customer in the system
  • can update existing customer information
  • can approve customer account request
  • can approve customer credit card request

 As a Customer, the user

Print

Banking Application Data Structure

Below is  a banking application data model structure. 

Banks
  • Bank_ID
  • Bank_Name
  • Other_Details
Branches
  • Branch_ID
  • Bank_ID
  • Branch_Details
Customers
  • Cusomer_ID
  • Branch_ID
  • Personal_Details
  • Contact_Details
Accounts
  • Account_Number
  • Account_Type_Code
  • Customer_ID
  • Current_Balance
  • Other_Details
Transactions
  • Transaction_ID
  • Account_Number
  • Transaction_Type_Code
  • Transaction_Date_Time
  • Transaction_Amount
  • Other_Details

Reference: http://www.databaseanswers.org/data_models/retail_banking_in_the_clouds/index.htM

Print

Banking Application Modules

In general, Banking Applications should have following modules: 

  • Banks
  • Branches
  • Customers
  • Accounts
  • Transactions
Print

Health Care Insurance Claim Application Test Cases

Based on the Health Care Insurance Claim Application Data Model, you can create following test cases. 

As a System Administrator, the user

  • can create a new hospital information 
  • can update an existing hospital information
  • can delete an existing hospital information
  • can create a new insurance company information
  • can update an existing insurance company information
  • can setup a new insurance claim processor staff
  • can update an insurance claim processor staff information
  • can delete a staff
  • can assign a claim to staff for processing

 As a Claim Processor Staff, the user

  • can update claim status
  • can request more information about the claim

As a Patient, the user

  • can setup patient profile online
  • can submit health care claims online
  • can request claim documentations
  • can upload requested documentations to the claim
  • can submit dispute to the claim resolution status

 As a Insurance Company admin, the user

Print

Health Insurance Claims Application Data Structure

Below is  a Health Care Claims Application data model structure. 

Hospitals
  • Hospital_ID
  • Hospital_Name
  • Other_Hospital_Details
Claims
  • Claim_ID
  • Claim_Status_Code
  • Hospital_ID
  • Insurance_Company_ID
  • Patient_ID
  • Updated_Date
  • Amount_Claimed
  • Amount_Paid
  • Other_Claim_Details
Claim Status
  • Claim_Status_Code
  • Claim_Status_Description(In Dispute, Settled)
Claim Dispute Management
  • Dispute_Area_Code
  • Dispute_Area_Description(None,Consultation,Medication,Treatment)
Patients
  • Patient_ID
  • Gender
  • Date_Of_Birth
  • Patient_Name
  • Patient_Address
  • Other_Patient_Details
Insurance Companies
  • Insurance_Company_ID
  • Insurance_Company_Name
  • Insurance_Company_Other_Details
Staff
  • Staff_ID
  • Staff_Category_Code
  • Gender
  • Staff_Firstname
  • Staff_Lastname
  • Staff_Qualifications
  • Staff_Birth_Date
  • Staff_Other_Details
Claim Processing Module
  • Claim_ID
  • Process_Date
  • Dispute_Area_Code
  • Processor_Staff_ID
  • End_Date
  • Step_Descriptions

Reference: http://www.databaseanswers.org/data_models/health_insurance_claims/index.htm