Recommended Free Tools
Software testing is easiest to understand across three dimensions: level (what scope is tested), objective (what behavior or quality is evaluated), and approach (how the test is performed). These dimensions are not competing lists. A single activity can be, for example, an automated functional test at system level.
Why “types of software testing” needs more than one list
Teams use the word “type” for different things: the size of the test object, the question being asked, or the method used to run the test. Mixing those categories can make a test plan confusing. The framework below follows the introductory taxonomy in the ISTQB Certified Tester Foundation Level Syllabus v4.0.1, dated 2024-09-15; terminology can vary across organizations and standards.
As an Amazon Associate I earn from qualifying purchases.
| Dimension | Question it answers | Examples |
|---|---|---|
| Level | What scope or test object is being tested? | Component, integration, system, acceptance |
| Objective or type | What behavior or quality characteristic is being evaluated? | Functional, non-functional |
| Approach | How is testing designed or executed? | Manual or automated; scripted or unscripted |
Keep the dimensions separate when planning: state the level, the objective, and the approach where each is relevant. For instance, “automated functional testing at system level” is more informative than simply “automation testing.”
Free tools Windows power users keep installed
One-click scans. No signup required.
Test levels: what scope is being checked?
ISTQB v4.0.1 describes component (also called unit), component integration, system, system integration, and acceptance testing. The usual sequence moves from smaller test objects toward the complete product and its intended use, but it is not a requirement that every product use every level in the same way. ISO/IEC/IEEE 29119’s overview says organizations can tailor testing to the test object and objectives.
| Level | Typical test object | Main question | Example |
|---|---|---|---|
| Component (unit) | An individual component or unit | Does this piece work as specified on its own? | Check a tax-calculation function with valid, boundary, and invalid inputs. |
| Component integration | Interactions among components within a system | Do connected components exchange data and behave correctly together? | Check that an order component passes the right amount and currency to a payment component. |
| System | The integrated system | Does the system meet its specified requirements as a whole? | Place an order through the application and verify the resulting confirmation and stored order. |
| System integration | Interfaces between the system and other systems or services | Does the system work correctly with external systems? | Verify the application’s interaction with a payment provider or an identity service. |
| Acceptance | The solution in relation to business needs and readiness | Is it suitable for its intended use and acceptable to relevant stakeholders? | Have business users check a release against agreed acceptance criteria. |
Component versus component integration
Component testing focuses on an individual unit. Component integration testing focuses on the connections among components. A defect in an isolated calculation may appear at component level; a mismatch in the data passed between two components belongs to their interaction.
System versus system integration
System testing evaluates the integrated product. System integration testing examines interfaces between that system and other systems or services. A working application can still fail at an external boundary—for example, if it sends a request in a format an external service does not accept.
Acceptance testing and its forms
Acceptance testing is about validation against business needs and readiness, not merely another name for system testing. ISTQB identifies user, operational, contractual, and regulatory acceptance testing, as well as alpha and beta testing, among its forms. The appropriate form depends on who needs assurance and what conditions or obligations must be met.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Functional and non-functional testing: what is being evaluated?
Functional and non-functional testing describe objectives, not scope. Either can be performed at an appropriate level: for example, a functional test may check one component or the complete system.
| Objective | What it evaluates | Example question |
|---|---|---|
| Functional | Whether specified functions or behaviors work | Does submitting a valid order create an order with the correct items? |
| Non-functional | How well the system behaves against quality characteristics | Does the service respond within the performance target under the defined conditions? |
ISTQB points to ISO/IEC 25010 for a classification of non-functional characteristics. Choose the quality characteristic and conditions that matter to the product; “non-functional” is not a single test or one universal checklist.
Testing approaches: how are tests performed?
Approach labels describe how testing is conducted or designed. They can coexist with levels and objectives; choosing automation, for example, does not determine whether a test is functional or what scope it covers.
Static and dynamic testing
Static testing evaluates work products without executing the software, such as reviewing requirements or code. Dynamic testing executes the software and evaluates its behavior. They provide different kinds of evidence and can both contribute to quality assurance.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Manual and automated testing
Manual testing is performed by a person carrying out or evaluating test activities. Automated testing uses tools or scripts to perform test steps or checks. ISO/IEC/IEEE 29119-2 recognizes both approaches. Automation can make repeatable checks easier to run, while the effort to build and maintain it depends on the product and test design; it is not automatically the best choice for every test.
Scripted and unscripted testing
Scripted testing follows predesigned test procedures or steps. Unscripted testing gives the tester more freedom to explore and adapt based on observations. These are not opposites to manual and automated execution: a test can be manual and scripted, or automated from a defined procedure.
White-box and black-box perspectives
White-box testing designs or evaluates tests with knowledge of internal structure, such as code or architecture. Black-box testing focuses on inputs and observable outputs without relying on internal implementation details. These perspectives can guide test design at different levels; they do not replace the level or objective labels.
Change-related testing: regression and retesting
Changes can require checks at more than one level. Regression testing is a strategy activity used to look for unintended effects of a change; the suitable scope depends on what changed and what could be affected. Retesting is also used in test strategy, but the term is not defined here as interchangeable with regression testing. Specify what a team means in its own plan rather than treating the labels as universal synonyms.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteHow to choose a useful combination
Choose tests by describing the risk and evidence you need, then assign a level, objective, and approach. Consider:
Rank #4
- Test object and scope: Is the concern one component, interactions inside the product, the whole system, an external interface, or readiness for use?
- Objective: Which function or quality characteristic needs evidence?
- Risk and consequence: What could go wrong, and how serious would the outcome be?
- Dependencies and environment: Does the test need realistic external services, data, devices, or operating conditions?
- Feedback and maintenance: How quickly is feedback needed, and what effort will it take to create and keep the checks useful?
Practical example: for a checkout change, test a changed calculation at component level, verify the handoff between checkout and payment components at component-integration level, exercise a complete order at system level, and check the payment-provider interface at system-integration level. If release readiness depends on business acceptance, add acceptance checks against agreed needs. Classify each test separately by objective and execution approach.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Standards and terminology
The ISTQB syllabus is a structured introductory source for testing terminology. The ISO/IEC/IEEE 29119 series provides a standards framework for software testing. The ISO/IEC JTC 1/SC 7 overview describes its purpose as defining “an internationally agreed set of standards for software testing that can be used by any organization when performing any form of software testing.” Its parts address concepts, processes, documentation, and test design techniques.
- ISTQB Certified Tester Foundation Level Syllabus v4.0.1
- ISO/IEC/IEEE 29119 series overview
- IEC catalog: ISO/IEC/IEEE 29119-1:2022
- IEC catalog: ISO/IEC/IEEE 29119-2:2021
The IEC catalog entries identify Part 1:2022 and Part 2:2021; older pages may show the 2013 editions. Check the relevant part’s current edition when citing or purchasing a standard.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Or skip the browser setup
For a website screenshot test, capture a page with one GET request instead of configuring a browser. ScreenshotNeo is a website screenshot API and MCP server. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. See the API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSign up for 1,000 free screenshots a month, with no card required.
Best Value
Frequently Asked Questions
Is unit testing different from component testing?
In the ISTQB syllabus, component testing is also called unit testing.
Is automation testing a test level?
No. Automation describes an execution approach; level describes the scope or test object.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchDoes every software project need all five test levels?
No. Select and tailor levels to the test object, objectives, risks, and environment.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
