Testing / Quality Assurance

The purpose of software testing is to validate and verify that a software product meets the business and technical requirements, and that it works as expected.

Cistel testing resources are well-versed in many different techniques and best-practices to assure clients that a software product functions as intended.  Some examples include:

• Usability testing checks if the user interface is easy to use and understand;
• Static testing refers to reviews, walkthroughs, or inspections;
• Functional testing refers to tests that verify a specific action or function of the code;
• Non-functional testing refers to aspects of the software that may not be related to a specific function or user action;
• Box testing refers to testing methods to describe the point of view that a test engineer takes when designing test cases, (White-box, Black-box and Grey-box);
• Destructive testing attempts to cause the software or a sub-system to fail, in order to test its robustness;
• Integration testing verifies that a system is integrated to any external or third party systems defined in the system requirements; and,
• Regression testing focuses on finding defects after a major code change has occurred.

For more information, please click here.