The domains of automation testing and security testing

The domain of automation includes white-box code inspection, unit testing, acceptance testing, integration testing, API testing, and end-to-end UI testing. In terms of implementation effort, unit testing and white-box inspection usually take the least effort, while UI testing often takes the most effort, particularly in order to understand the UI business flow.

Therefore, most automated testing cases are done with unit testing or API-level testing. Automated UI testing may only cover the scenarios from a user perspective while the API testing may cover more business logic or exception handling use cases. The following diagram illustrates the different levels of automation testing and how much effort they take.

Levels of Automation Testing

On the other hand, the domain of security testing can be much broader. The following table lists the practices that come under the general umbrella of security testing. In this book, we will have some case studies to cover some of the topics in bold:

Information gathering
Vulnerability analysis
Wireless attacks
Web application exploitation tools
Forensics tools
Stress testing
Sniffing and spoofing
Password attacks
Maintaining access

Reverse engineering
Reporting tools
Hardware hacking
Authentication
Authorization
Configuration management
Cryptography
Data validation

Denial of service
Encryption
Error handling
Information disclosure
Race conditions
Session management
Secure transmission

Table of Contents for The domains of automation testing and security testing

Create new playlist

Sign In

Sign Up

Table of Contents for
The domains of automation testing and security testing