Service M Forum
Воскресенье, 11.12.2016, 07:12
START-SM МИГРАЦИЯ ENGLISH INSURANCE ЗАРАБОТОК X1-MSB МАГАЗИН ФОРУМ АЗАРТ INFO-СТОК $ RUSBUX $
ФОРУМ САЙТА START-SM.AT.UA
Регистрация Новые сообщения Правила форума Участники Поиск ВХОД RSS
Страница 1 из 11
Форум » EDUCATION » QA Testing » Software QA Testing GLOSSARY (Словарь терминологии SQA Testing)
Software QA Testing GLOSSARY
start-sm Дата: Пятница, 18.01.2013, 22:59 | Сообщение # 1
Admin
Administrator
Posts: 574
Reputation: 3
Status: Offline
Software Testing Types

ACCEPTANCE TESTING
Testing to verify a product meets customer specified requirements. A customer usually does this type of testing on a product that is developed externally.

BLACK BOX TESTING
Testing without knowledge of the internal workings of the item being tested. Tests are usually functional.

COMPATIBILITY TESTING
Testing to ensure compatibility of an application or Web site with different browsers, OSs, and hardware platforms. Compatibility testing can be performed manually or can be driven by an automated functional or regression test suite.

CONFORMANCE TESTING
Verifying implementation conformance to industry standards. Producing tests for the behavior of an implementation to be sure it provides the portability, interoperability, and/or compatibility a standard defines.

FUNCTIONAL TESTING
Validating an application or Web site conforms to its specifications and correctly performs all its required functions. This entails a series of tests which perform a feature by feature validation of behavior, using a wide range of normal and erroneous input data. This can involve testing of the product's user interface, APIs, database management, security, installation, networking, etcF testing can be performed on an automated or manual basis using black box or white box methodologies.

INTEGRATION TESTING
Testing in which modules are combined and tested as a group. Modules are typically code modules, individual applications, client and server applications on a network, etc. Integration Testing follows unit testing and precedes system testing.LOAD TESTINGLoad testing is a generic term covering Performance Testing and Stress Testing.

PERFORMANCE TESTING
Performance testing can be applied to understand your application or web site's scalability, or to benchmark the performance in an environment of third party products such as servers and middleware for potential purchase. This sort of testing is particularly useful to identify performance bottlenecks in high use applications. Performance testing generally involves an automated test suite as this allows easy simulation of a variety of normal, peak, and exceptional load conditions.

REGRESSION TESTING
Similar in scope to a functional test, a regression test allows a consistent, repeatable validation of each new release of a product or Web site. Such testing ensures reported product defects have been corrected for each new release and that no new quality problems were introduced in the maintenance process. Though regression testing can be performed manually an automated test suite is often used to reduce the time and resources needed to perform the required testing.

SMOKE TESTING
A quick-and-dirty test that the major functions of a piece of software work without bothering with finer details. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

STRESS TESTING
Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. A graceful degradation under load leading to non-catastrophic failure is the desired result. Often Stress Testing is performed using the same process as Performance Testing but employing a very high level of simulated load.

SYSTEM TESTING
Testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.

UNIT TESTING
Functional and reliability testing in an Engineering environment. Producing tests for the behavior of components of a product to ensure their correct behavior prior to system integration.

WHITE BOX TESTING
Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing.

Link
 
start-sm Дата: Пятница, 18.01.2013, 23:04 | Сообщение # 2
Admin
Administrator
Posts: 574
Reputation: 3
Status: Offline
Software testing Glossary A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

A

Acceptance Testing: Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

Accessibility Testing: Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

Ad Hoc Testing: A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well. See also Monkey Testing.

Agile Testing: Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.

Application Binary Interface (ABI): A specification defining requirements for portability of applications in binary forms across defferent system platforms and environments.

Application Programming Interface (API): A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

Automated Software Quality (ASQ): The use of software tools, such as automated testing tools, to improve software quality.

Automated Testing:
• Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing.
• The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
 
start-sm Дата: Пятница, 18.01.2013, 23:05 | Сообщение # 3
Admin
Administrator
Posts: 574
Reputation: 3
Status: Offline
Bug Tracking Tools and Applications
 
start-sm Дата: Пятница, 18.01.2013, 23:12 | Сообщение # 4
Admin
Administrator
Posts: 574
Reputation: 3
Status: Offline
Other Sources:

QA Glossary

Glossary of Software Testing/QA Terms

QA/Test Glossary
There are often confusion and misunderstanding in Testing. This is the reson why a glossary might be of interest.
- All types of testing glossary
- Generic glossary
* Test components glossary
* Test documents glossary
- XQual-specific glossary


Software Testing terms complete glossary

Glossary of Software QA/Testing

Tricky Software testing Terms
 
Форум » EDUCATION » QA Testing » Software QA Testing GLOSSARY (Словарь терминологии SQA Testing)
Страница 1 из 11
Поиск:

    Copyright MyCorp © 2016 Бесплатный конструктор сайтов - uCoz