"Software testing is the act of examining the artifacts and the behavior of the software under test by validation and verification."
The process of ensuring that the system meets its requirements and performs its intended function through testing and evaluation.
Systems Engineering: The systematic approach to designing, analyzing, and managing complex systems.
Verification and Validation (V&V): The process of evaluating whether a system meets its specified requirements and intended purpose.
Requirement Analysis: The process of identifying, defining, and documenting the requirements for a system.
Test Planning: The process of creating a plan for testing a system to ensure that it meets its specified requirements.
Test Execution: The process of executing tests to verify that a system meets its specified requirements.
Test Reporting: The process of documenting the results of tests conducted to verify a system's compliance with its specified requirements.
Test Automation: The use of software tools and scripts to automate the execution of tests.
Model-based testing: The use of models to generate test cases and verify system behavior.
Quality Assurance: The process of ensuring that a system meets its specified quality standards.
Configuration Management: The process of managing system configurations throughout the development lifecycle.
Traceability: The ability to trace system requirements throughout the development and testing process.
Risk Management: The process of assessing and managing risks associated with a system.
Metrics and Measurements: The use of metrics and measurements to evaluate system performance, reliability, and quality.
Test-driven Development: The process of developing software code by writing automated tests before writing the code.
Continuous Integration/Continuous Delivery (CI/CD): The process of continuously integrating code changes into a system and delivering updates to end-users.
Requirements Verification: Ensuring that the system requirements have been adequately defined and implemented.
Design Verification: Making sure the system design meets all specification requirements and can be created within the allocated resources and timeframe.
Coding Verification: Checking the code construction against design and requirements specifications to ensure that the code is semantically correct, critical algorithms are optimized for accuracy and speed, and the code is error-free.
Software Integration Verification: Ensuring that main core code sections are linked and interact properly through a single system to avoid any flaws while performing logical and behavioral testing.
Component & Module Verification: Ensuring that the individual modules work correctly and also combine in the system with the appropriate parallelism to provide the best results efficiently.
System Integration Verification: Ensuring all parts of the system integrate together seamlessly and work in harmony.
Configuration Verification: Ensuring all configurations and implementations are functioning properly as they are intended.
Regression Testing: Ensuring new changes or implants in the system do not modify currently functioning features.
Acceptance Testing: Checking the system to ensure that it fulfills all given requirements.
Alpha Testing: Performed by the client in the project environment while functional testing is simulated and mocked along the real environment.
Beta Testing: Conducted in the actual application place, running test scripts and simulating actual user scenarios to test the system.
Security Testing: Ensuring that the system is secure from hacks and cyber attacks in design, coding and live environment performance.
Load/ Performance Testing: Ensuring that the system can handle the anticipated load and that the speed of an application in user interaction is stable and consistent.
Usability Testing: Assessing how user-friendly the system is and if it meets the user's expectations and requirements for solving a business problem.
Accessibility Testing: Ensuring the system is designed and implemented to meet specific accessibility requirements for visually-impaired, hearing-impaired or people with other disabilities.
Compatibility Testing: Testing how different devices and platforms interact with the system, ensuring all supported devices work with the system as intended.
Compliance Testing: Ensuring the system follows external norms like legal guidelines or industry-specific regulations.
Disaster Recovery and Business Continuity Testing: Ensuring the system has backup solutions to prevent data loss and resuming system back to normal after unexpected situations or natural calamities.
Maintenance Testing: Ensuring that the system is easily maintainable and updating the system with the latest technology advancements when necessary.
Smoke Testing: A basic stage of an automated testing strategy to catch basic defects and errors in the system quickly.
"A primary purpose of testing is to detect software failures so that defects may be discovered and corrected."
"Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation."
"Test techniques include, but are not necessarily limited to: analyzing the product requirements for completeness and correctness, reviewing the product architecture and overall design, working with product developers on improvement in coding techniques, executing a program or application with the intent of examining behavior, reviewing the deployment infrastructure and associated scripts and automation."
"The scope of software testing may include the examination of code as well as the execution of that code in various environments and conditions."
"Testing cannot identify all the failures within the software."
"Testing furnishes a criticism or comparison that compares the state and behavior of the product against test oracles - principles or mechanisms by which someone might recognize a problem."
"Analyzing the product requirements for completeness and correctness in various contexts like industry perspective, business perspective, feasibility and viability of implementation, usability, performance, security, infrastructure considerations, etc."
"Examining the aspects of code: does it do what it is supposed to do and do what it needs to do."
"Information derived from software testing may be used to correct the process by which software is developed."
"In the current culture of software development, a testing organization may be separate from the development team."
"When an organization develops or invests in a software product, it can assess whether the software product will be acceptable to its end users, its target audience, its purchasers, and other stakeholders. Software testing assists in making this assessment."