Software Testing logopeterindia.net
Knowledge Hub

Software Testing

A curated directory of software testing tools and resources — security testing, test automation, performance and resilience testing, and code quality — for modern software delivery.

29 topics•6 categories•Updated November 2026

Security Testing

5 entries

Finding vulnerabilities in applications, code and dependencies.

Functional & Test Automation

4 entries

Automating functional, regression and integration tests.

Performance, Kubernetes & Resilience Testing

5 entries

Load, performance, cluster and failure testing.

Code Quality & Defect Management

3 entries

Reviewing code and tracking defects.

Testing Foundations, Standards & Communities

8 entries

Core references behind every kind of software testing.

Related Pages

4 entries

Related directories on this site.

Frequently Asked Questions

What is software testing?

Software testing checks that applications are functionally correct, secure, performant and reliable before and after release, using manual and automated techniques.

What is the difference between SAST and DAST?

SAST analyses source code, byte code or binaries without running the program, while DAST tests a running application from the outside by simulating attacks. Many teams use both.

Where does AI fit into testing?

AI-augmented tools generate test cases, prioritise runs and self-heal brittle tests when the user interface changes. The AI-Augmented Software Testing Tools page lists them.

Why are some older pages not listed?

Automated UI Testing Tools, Load Testing Tools and Microservices Performance Testing Tools were merged into Software Test Automation Tools and Performance Testing Tools, so they are not listed separately.

What are the main types of software testing?

Functional testing checks features against requirements, automated testing repeats checks in CI, performance testing measures speed and capacity, and security testing finds vulnerabilities through SAST, DAST and penetration tests. Resilience, accessibility and usability testing complement them.

How should I structure a software testing strategy?

Use a test pyramid: many fast unit tests, fewer integration and API tests, and a small set of end-to-end tests. Add security and performance tests in the pipeline, track defects, and measure coverage and escaped bugs.

How is chaos engineering related to testing?

Chaos engineering injects faults into running systems to test how well they stay resilient, so it complements functional and performance testing.