Testing Tools & Techniques Definitions

Search Definitions
  • A

    alpha testing

    Alpha testing is the initial phase of validating whether a new product will perform as expected.

  • Apache JMeter

    Apache JMeter is an open source, Java-based load testing tool that can analyze the functional behavior of a system and measure the performance of a system under a load test.

  • automated testing

    Automated testing is a software testing technique that automates the process of validating the functionality of software and ensures it meets requirements before being released into production.

  • B

    black box (black box testing)

    Black box testing assesses a system solely from the outside, without the operator or tester knowing what is happening within the system to generate responses to test actions.

  • C

    citizen development

    Citizen development is a business process that encourages non-IT-trained employees to become software developers, using IT-sanctioned low-code/no-code (LCNC) platforms to create business applications.

  • continuous integration (CI)

    Continuous integration (CI) is a software development practice in which frequent, isolated changes are immediately tested and reported on when they're added to a larger codebase.

  • D

    debugging

    Debugging, in computer programming and engineering, is a multistep process that involves identifying a problem, isolating the source of the problem and then either correcting the problem or determining a way to work around it.

  • dynamic application security testing (DAST)

    A dynamic application security test (DAST) is a program used by developers to analyze a web application (web app), while in runtime, and identify any security vulnerabilities or weaknesses.

  • E

    end-to-end testing

    End-to-end (E2E) testing is a software testing methodology that verifies the working order of a software product in a start-to-finish process.

  • exception handling

    Exception handling is the process of responding to unwanted or unexpected events when a computer program runs.

  • F

    fault injection testing

    Fault injection is a testing process which deliberately introduces errors to a system to ensure the system can withstand the error and recover.

  • finite element analysis (FEA)

    Finite element analysis (FEA) is the use of calculations, models and simulations to predict and understand how an object might behave under various physical conditions.

  • functional testing

    Functional testing is a process used to evaluate software during development to ensure that it meets the application's intended requirements and specifications.

  • G

    garbage in, garbage out (GIGO)

    Garbage in, garbage out, or GIGO, refers to the idea that in any system, the quality of output is determined by the quality of the input.

  • H

    happy path testing

    Happy-path testing is a type of software testing that uses known input and produces an expected output. Also referred to as golden-path or sunny-day testing, the happy-path approach is tightly scripted. The happy path does not duplicate real-world conditions and verifies only that the required functionality is in place and functions correctly.

  • Hypertext Transfer Protocol Secure (HTTPS)

    Hypertext Transfer Protocol Secure (HTTPS) is a protocol that secures communication and data transfer between a user's web browser and a website.

  • I

    integration testing or integration and testing (I&T)

    Integration testing -- also known as integration and testing (I&T) -- is a type of software testing in which the different units, modules or components of a software application are tested as a combined entity.

  • M

    model-based testing

    Model-based testing (MBT) requires a test team to create a second, lightweight implementation of a software build- typically only the business logic - called the model.

  • N

    NIST (National Institute of Standards and Technology)

    NIST (National Institute of Standards and Technology) is a nonregulatory government agency located in Gaithersburg, Md.

  • O

    offshore software testing

    Offshore software testing is a software development model where an organization outsources the software testing process to a service partner team located in a different country with a different time zone.

  • Open Web Application Security Project (OWASP)

    The Open Web Application Security Project (OWASP) is a nonprofit foundation that provides guidance on how to develop, purchase and maintain trustworthy and secure software applications.

  • P

    performance testing

    Performance testing is a testing measure that evaluates the speed, responsiveness and stability of a computer, network, software program or device under a workload.

  • Q

    quality assurance (QA)

    Quality assurance (QA) is any systematic process of determining whether a product or service meets specified requirements.

  • R

    reverse-engineering

    Reverse-engineering is the act of dismantling an object to see how it works.

  • S

    staging environment

    A staging environment, or staging, provides a nearly exact replica of a production environment for software testing.

  • static application security testing (SAST)

    Static application security testing (SAST) is a program designed to analyze application (app) source code in order to find security vulnerabilities or weaknesses that may open an app up to a malicious attack.

  • synthetic monitoring

    Synthetic monitoring is the use of software to simulate user interactions with a system.

  • system testing

    System testing, also referred to as system-level testing or system integration testing, is the process in which a quality assurance (QA) team evaluates how the various components of an application interact together in the full, integrated system or application.

  • T

    test case

    A test case is a set of actions performed on a system to determine if it satisfies software requirements and functions correctly.

  • test harness

    In software development, a test harness is a collection of software and test data used by developers to unit test software models during development.

  • test-driven development (TDD)

    Test-driven development (TDD), also called test-driven design, is a method of implementing software programming that interlaces unit testing, programming and refactoring on source code.

  • U

    unit testing

    Unit testing is a software development process in which the smallest testable parts of an application, called units, are individually scrutinized for proper operation.

  • user acceptance testing (UAT)

    User acceptance testing (UAT), also called application testing or end-user testing, is a phase of software development in which the software is tested in the real world by its intended audience.

  • W

    white box testing

    White box testing is a software testing methodology in which the code structure is known and understood by the tester.

Cloud Computing
App Architecture
ITOperations
TheServerSide.com
SearchAWS
Close