Software Testing
User Acceptance Testing - UAT
Domains: Banking Services, Financial Markets, Insurance (Life) and Insurance (Non-Life)
Software Testing is all about determining the QUALITY of the SOFTWARE UNDER TEST.
Software Testing provides an objective and an independent view of the software, and makes stakeholders understand the risks of software implementation before it is made live through production. Software Testing is NOT a process of finding bugs.
Software Testing is a process of Validation and Verification for a software program or application or a product or combinations of software products. Software Testing is done to see that the BUSINESS and TECHNICAL requirements are met, and performs as EXPECTED. To achieve all these TEST DESIGN plays a very crucial role.
What is test design?
• Planning of inputs and predicting system behavior for each input.
How do we go about?
• Plan inputs, one at a time, assuming that the input will be accepted by the system
• Sequence the inputs, taking into consideration sequence related constraints
How do we plan each input?
• Identify what drives each input (drivers are those fields, whose value alters the system behavior [functionality] in some way)
• Identify combinations of input values which force the system to reject the input
• Arrive at the set of inputs, ensuring that each driver value is used at least once in a positive input combination and each negative combination is tested
How do we crash test design time?
• 100% negative testing
• Intelligent positive testing using optimized process/algorithm
How do make the design flexible?
• Identify the open-endedness required with an easy way of tightening the definition to suit the specific system using the Questionnaire approach
• Allow for changes to the drivers, their values, rules that turn inputs negative and the sequences to be tested and ensure that the design responds to the changes appropriately
How do we plan each input?
• Identify what drives each input (drivers are those fields, whose value alters the system behavior [functionality] in some way)
• Identify combinations of input values which force the system to reject the input
• Arrive at the set of inputs, ensuring that each driver value is used at least once in a positive input combination and each negative combination is tested
How do we plan the required sequences?
• Arrive at the complete set of sequences that are possible
• Eliminate sequences that are impossible to accomplish in the system/application
• Integrate the individual input combinations into the sequences to arrive at the design
Why Us?
Domain Capability: Strong in domain across multiple geographies.
Comprehensive Coverage: Use of Algorithms to derive Test Design Ensure 100% Test Coverage.
Quality Product: By Virtue of comprehensive design, software quality is enhanced; Defect leakage would be minimal other than regression issues.
Our Team:Over 100 Man Years experience in Consulting, Project Management, Software Development and Innovations. Domain Experts with 25 Years experience
