Image CAPTCHA
Enter the characters shown in the image.

You are here

Testing Terms: A

Testing Terms
TERMS
A
TERMS
B
TERMS
 C
TERMS
D
TERMS
E
TERMS
F
TERMS
G
TERMS
H
TERMS
I
TERMS
J
TERMS
K
TERMS
L
TERMS
M
TERMS
N
TERMS
O
TERMS
P
TERMS
Q
TERMS
R
TERMS
S
TERMS
T
TERMS
U
TERMS
V
TERMS
W
TERMS
X
TERMS
Y
TERMS
Z

 

  1. A/B testing
    1.  (sometimes called split testing) is comparing two versions of a web page to see which one performs better. You compare two web pages by showing the two variants (let's call them A and B) to similar visitors at the same time. The one that gives abetter conversion rate, wins!
  2. Acceptance Criteria 
    1. The exit criteria that a component or system must satisfy in order to be accepted by a user, customer, or other entity
  3. Acceptance Testing
    1. Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.
  4. Actual Result
    1. The behavior produced/observed when a component or system is tested.
  5. Ad hoc testing:
    1. Testing carried out informally; no formal test preparation takes place, no recognized test design technique is used, there are no expectations for results and arbitrariness guides the test execution activity.
  6. Agile testing 
    1. A software testing practice that follows the principles of agile software development. Agile testing does not emphasize testing procedures and focuses on ongoing testing against newly developed code until quality software from an end customer's perspective results. Agile testing is built upon the philosophy that testers need to adapt to rapid deployment cycles and changes in testing patterns.
  7. ALM
    1. Application Lifecycle Management (ALM) is a continuous process of managing the life of an application through governance, development and maintenance. ALM is the marriage of business management to software engineering made possible by tools that facilitate and integrate requirements management, architecture, coding, testing, tracking, and release management.
  8. Alpha testing
    1. Simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site, but outside the development organization. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing.
  9. API Testing
    1. An Application Programming Interface (API) is essentially a collection of functions and procedures that can be executed by external applications. A vital part of using APIs is making sure that their behind-the-scenes calls are seamless to the end-user. Additionally, security is a high concern since you either allowing your own API to be used by others, or you are using an API developed by someone else. Testing API functionality, integration, and security is very important and often requires specialized automated tools to make the process more efficient. 
  10. Application Store Compliance testing
    1. An application store (sometimes also referred to as an app store, app marketplace, or variations) is a type of digital distribution platform for application software, often provided as a component of an operating system on a personal computer, smartphone, or tablet. Application stores typically take the form of an online store, where users can browse through different categories and genres of applications (such as for example, productivity , multimedia, and games), view information and reviews of then, purchase it (if necessary), and then automatically download and install the application on their device.
    2. Many application stores are curated and regulated by their owners, requiring that submissions go through an approval process where applications are inspected for compliance with certain guidelines (such as those for quality and content), and also require that a commission be collected on each sale of a paid application.
  11. ATDD
    1. Acceptance test-driven development (acceptance TDD) is what helps developers build high-quality software that fulfills the business’s needs as reliably as TDD helps ensure the software’s technical quality.
  12. ATM
    1. Asynchronous Transfer Mode (ATM) is, according to the ATM Forum, "a telecommunications concept defined by ANSI and ITU (formerly CCITT) standards for carriage of a complete range of user traffic, including voicedata, and video signals". ATM was developed to meet the needs of the Broadband Integrated Services Digital Network, as defined in the late 1980s, and designed to unify telecommunication and computer networks. It was designed for a network that must handle both traditional high-throughput data traffic (e.g., file transfers), and real-timelow-latency content such as voice and video. The reference model for ATM approximately maps to the three lowest layers of the ISO-OSI reference modelnetwork layerdata link layer, and physical layer. ATM is a core protocol used over the SONET/SDH backbone of the public switched telephone network (PSTN) andIntegrated Services Digital Network (ISDN), but its use is declining in favor of all IP.
  13. Automated Testware
    1. Testware used in automated testing, such as tool scripts.

 

Theme by Danetsoft and Danang Probo Sayekti