Testing: What you Need to Know Before Your Next CIS Implementation

Before Testing

test environment

 During or “Go Live” Testing

After or “Post Release” Testing

never

 Testing Basics

 Methods

Static Vs. Dynamic Testing

• Static Testing – Static testing uses implicit tactics such as proofreading and checking source code structure and syntax. Static testing involves verification – or ensuring that all requirements are met. Verification answers the question “Are we building the right product?”
• Dynamic Testing – Dynamic testing runs code and uses tactics such as debugging. Dynamic testing involves validation – or making sure the system fulfills its intended purpose. Validation answers the question “Are we building the right product?”

The Box Approach

• White-box Testing – tests internal structures/workings of a system
• Black-box Testing – Examines how the system works without regard to its inner workings
• Grey-box Testing – Using knowledge of the internal workings to design tests aimed at the end user

Levels

• Unit Testing – Verifies functionality of a specific section of code
• Integration Testing – Verifies that components of the system work together as planned
• Component Interface Testing – Verifying data or “packet” transfer
• System Testing – Verifies the system meets all requirements
• Acceptance Testing – Testing whether the end-user accepts the delivered system

Types

here

• Beta-testing
• Usability Testing
• Security Testing
• Performance Testing
• Compatibility Testing
• A/B Testing
• Regression Testing
• And more!