Testing in CI / CD Pipeline
- 1. TestinginCI/CDPipeline User Acceptance Ad Hoc Smoke Tests Production Acceptance Disaster Recovery Tests Development Unit Tests Local UI Tests Q / A Functional Tests Integration Tests Independent UI Tests Release A / B Tests Penetration Tests System & Performance Monitoring Staging System Testing Performance & Load Testing Unit Testing Testing specific functionality at the source code level Local UI Testing Testing UI on a local machine Functional Tests Testing what a system does by testing the specific artifacts available Integration Tests Tests to ensure that application as well as associated components and services function correctly together Independent UI Tests UI testing done on central webserver or non-local machine A / B Tests Testing two variants of the same functionality for customer reaction Penetration Tests Testing an application for vulnerabilities an attacker could exploit System & Performance Monitoring Testing how an application and core components are performing in a production environment Performance & Load Testing Testing simulated user behavior and load to make sure a system works as expected at scale System Testing Testing to insure each component and service within a system are working together Disaster Recovery Tests Tests to insure the application operates gracefully when large scale system failures occur Smoke Testing Ad hoc tests typically done manually to insure basic functionality of an application works mabl uses machine learning to help simplify and improve your CI/CD testing pipeline. Findouthowat mabl.com