Home
Articles
Interview Questions
.Net
.Net Design Pattern
.Net Windows Service
ADO.NET
Android
Architecture
ASP.NET Ajax
ASP.NET Core
ASP.NET Gridview
ASP.NET MVC
ASP.NET Web API
Automation Anywhere
AWS
AWS SDK and C#
AWS SDK and Node.js
Azure DevOps
Blockchain
Bootstrap
C#
CSS
Django
Docker
Environment
Excel
Excel Formula
Firebase
Flutter and dart
Git
HTML
HTML 5
IIS
Java
JavaScript
JMeter
JQuery
JSON
Light Switch 2011
Linux
Matplotlib
Microsoft Bot Framework
Microsoft Azure
MongoDB
MSWord
Node.js
NumPy
Pandas
Photoshop
PHP
PHP Codeigniter
PostGreSQL
Powerpoint
PowerShell
Project Management
Python
React.js
Seaborn
Selenium
Silverlight
Software Testing
Sonarqube
Spacy
SQL Server
Togaf
UiPath
VBA For Excel
VBA For Outlook
WCF
WPF
XML
XSD
Articles
→
SOFTWARE TESTING
→
Terms Used In Software Testing Part IV
Terms Used In Software Testing Part IV
Smoke test:
A subset of all defined/planned test cases that cover the main functionality of a component or system, to ascertaining that the most crucial functions of a program work, but not bothering with finer details. A daily build and smoke test is among industry best practices.
Software:
Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system.
Software quality:
The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs.
Software Usability Measurement Inventory (SUMI):
A questionnaire based usability test technique to evaluate the usability, e.g. user-satisfaction, of a component or system.
Specification:
A document that specifies, ideally in a complete, precise and verifiable manner, the requirements, design, behavior, or other characteristics of a component or system, and, often, the procedures for determining whether these provisions have been satisfied.
Specified input:
An input for which the specification predicts a result.
Stability:
The capability of the software product to avoid unexpected effects from modifications in the software.
State diagram:
A diagram that depicts the states that a component or system can assume, and shows the events or circumstances that cause and/or result from a change from one state to another.
State table:
A grid showing the resulting transitions for each state combined with each possible event, showing both valid and invalid transitions.
State transition:
A transition between two states of a component or system.
State transition testing:
A black box test design technique in which test cases are designed to execute valid and invalid state transitions. See also N-switch testing.
Statement:
An entity in a programming language, which is typically the smallest indivisible unit of execution.
Statement coverage:
The percentage of executable statements that have been exercised by a test suite.
Statement testing:
A white box test design technique in which test cases are designed to execute statements.
Static analysis:
Analysis of software artifacts, e.g. requirements or code, carried out without execution of these software artifacts.
Static analyzer:
A tool that carries out static analysis.
Static code analysis:
Analysis of source code carried out without execution of that software.
Static code analyzer:
A tool that carries out static code analysis. The tool checks source code, for certain properties such as conformance to coding standards, quality metrics or data flow anomalies.
Static testing:
Testing of a component or system at specification or implementation level without execution of that software, e.g. reviews or static code analysis.
Statistical testing:
A test design technique in which a model of the statistical distribution of the input is used to construct representative test cases. See also operational profile testing.
Posted By -
Amandeep Dhanjal
Posted On -
Monday, November 28, 2011
Query/Feedback
Your Email Id
*
*
Subject
*
Query/Feedback
Characters remaining 250
*
*