Question 1

A/B Testing

Accepted Answer

A/B testing involves creating one or more variants of a webpage to compare against the current version. The goal is to determine which version performs best based on specific metrics, such as revenue per visitor or conversion rate.

Question 2

Acceptance Test Driven Development

Accepted Answer

Acceptance Test Driven Development (ATDD) is a development approach aimed at reducing defects by integrating testing as a core component of the development process. This ensures that the application meets quality standards.

Question 3

Acceptance Testing

Accepted Answer

Acceptance testing is conducted by potential end-users or customers to determine if the software meets the required specifications and is suitable for its intended use.

Question 4

Accessibility Testing

Accepted Answer

Accessibility testing ensures mobile and web applications are usable by everyone, including individuals with disabilities such as visual or hearing impairments, and other physical or cognitive challenges.

Question 5

Actual Result

Accepted Answer

The actual result is the outcome obtained after a test is conducted. During the testing phase, the actual result is documented alongside the test case. After all tests, it's compared with the expected outcome, noting any discrepancies.

Question 6

Ad Hoc Testing

Accepted Answer

Ad hoc testing is an informal, spontaneous approach to software testing. Its main objective is to identify vulnerabilities or issues as quickly as possible. This method is unstructured, conducted without detailed planning or documentation.

Question 7

Agile Development

Accepted Answer

Agile software development is an iterative method where requirements and solutions are collaboratively developed by cross-functional teams. It emphasizes adaptability and responsiveness over rigid planning.

Question 8

Agile Testing

Accepted Answer

Agile testing aligns with the principles of Agile software development. Unlike traditional approaches, testing starts at the project's outset with development and testing occurring simultaneously. This close collaboration ensures tasks are accomplished efficiently.

Question 9

Alpha Testing

Accepted Answer

Alpha testing aims to identify bugs before the product reaches the end-users. Conducted late in the development process but before beta testing, it helps ensure that the product is free from major issues.

Question 10

Analytical Test Strategy

Accepted Answer

Analytical test strategies involve analyzing the test basis before executing the test. This strategy helps pinpoint potential problems early on, ensuring a more effective testing process.

Question 11

API

Accepted Answer

An Application Programming Interface (API) is a set of rules allowing two applications to communicate. The term "Application" in this context denotes any software with a specific function. The API defines how these applications send and receive requests and responses.

Question 12

API Testing

Accepted Answer

API testing involves verifying and validating an API's performance, functionality, reliability, and security. The process includes sending requests to the API and analyzing its responses to ensure they meet expected outcomes. This testing can be done manually or using automated tools, helping identify issues like invalid inputs, poor error handling, and unauthorized access.

Question 13

ASTQB

Accepted Answer

The American Software Testing Qualifications Board (ASTQB) is the U.S. national board for the International Software Testing Qualifications Board (ISTQB). It's responsible for the "ISTQB Certified Tester" program in the U.S. The ASTQB provides and manages certifications, accredits trainers, and approves training materials for software testing professionals. Earning an ISTQB certification through ASTQB ensures that an individual meets internationally recognized standards in software testing. Additionally, ASTQB promotes the value and importance of software testing as a profession within the U.S. software development and IT industries.

Question 14

Automated Testing

Accepted Answer

Automated testing uses scripts to conduct repetitive tasks, increasing software performance and testing efficiency. It enhances test coverage and execution speed, making the software testing process more effective.

Question 15

Availability Testing

Accepted Answer

Availability Testing, in the context of software testing, refers to evaluating a system's uptime, ensuring that the application or system remains accessible and operational to users as intended. The primary goal of this testing is to guarantee that the software meets its defined availability criteria and provides a reliable service without prolonged interruptions. This kind of testing often considers scenarios like system failures, maintenance, peak user loads, and network outages, and aims to determine the system's overall reliability and readiness for production deployment. Availability Testing is crucial for applications where continuous accessibility is paramount, such as e-commerce platforms, banking systems, and critical infrastructure services.

Question 16

Back-to-Back Testing

Accepted Answer

Back-to-back testing compares the results of two or more similar-functioning components to check for differences in their outputs.

Question 17

Backward Compatibility

Accepted Answer

Backward Compatibility, in the context of software testing, refers to the ability of a software application or system to effectively function with earlier versions of itself or interface correctly with older input data formats, configurations, or hardware. In essence, when a software product is backward compatible, it ensures that users employing older versions won't encounter unexpected issues or malfunctions when interfacing with the newer iteration. Testing for backward compatibility is crucial during software upgrades or releases to make certain that changes introduced do not negatively impact existing users or break established functionalities. This practice prioritizes the user experience, ensuring seamless transitions and interactions between software generations.

Question 18

Baseline Testing

Accepted Answer

Baseline Testing is a type of non-functional testing where the performance or characteristics of a system or application are measured under specific conditions. This initial measurement serves as a "baseline" or benchmark against which future performance levels can be compared. The primary goal of baseline testing is to understand the current behavior of the system and set a standard for subsequent testing phases. Any deviations in future tests from this baseline can indicate performance issues, regressions, or other anomalies that might need addressing.

Question 19

BDD

Accepted Answer

BDD (Behavior-Driven Development) is an agile software development approach that emphasizes collaboration between developers, testers, and domain experts. It focuses on understanding and defining the desired behavior of a system from the user's perspective. BDD encourages the use of simple, plain-language descriptions of software behavior, often structured as "Given-When-Then" scenarios. These descriptions serve as both requirements documentation and a basis for automated tests, ensuring that software development is aligned with user needs and expectations.

Question 20

Beta Testing

Accepted Answer

Beta testing is the final testing phase before product release, where a near-complete version is provided to a select group of end-users. It aims to gather feedback on various aspects of the software, ensuring it meets user expectations.

Question 21

Big Bang Testing

Accepted Answer

Big Bang Testing is an approach where all system units are linked simultaneously without regard for their interactions. This method can make error isolation challenging as it requires focusing on the interfaces of individual units.

Question 22

Black Box Testing

Accepted Answer

Black box testing assesses software without considering its internal workings. Typically focused on functional or acceptance testing, it can be done by anyone, regardless of their familiarity with the codebase.

Question 23

Bottom-up Integration

Accepted Answer

Bottom-up integration testing starts by testing lower-level modules first, then integrates and tests them with higher-level ones. During this process, "Drivers" may be used to assist in testing.

Question 24

Boundary Testing

Accepted Answer

Evaluates software by focusing on the boundary or edge values of the input domain.

Question 25

BrowserStack

Accepted Answer

BrowserStack is a cloud-based web and mobile testing platform that allows developers and testers to view and interact with their websites and applications across multiple browsers, operating systems, and real mobile devices without the need for an internal lab of virtual machines or devices. It provides instant access to a wide range of browser and OS combinations, ensuring that developers can test their products in real-world conditions. This helps in identifying and resolving compatibility issues that might not be evident on a single platform or browser. BrowserStack is particularly beneficial for ensuring cross-browser and cross-platform compatibility, and it integrates with many popular continuous integration tools to streamline the testing process.

Question 26

BS 7925-2

Accepted Answer

BS 7925-2 is a standard for Software Component Testing. It outlines a process for component testing using specific test designs and measurement techniques, aiming to enhance the quality of both testing and software products.

Question 27

Bug

Accepted Answer

A bug is an error or fault in a program that leads to incorrect outcomes or crashes. It arises from flawed or incomplete logic and can cause the software to deviate from its expected performance.

Question 28

Build Verification Testing

Accepted Answer

Build Verification Testing (BVT) is a set of preliminary tests performed on a newly built software product to ensure its basic functionality before it undergoes more in-depth testing. The primary goal of BVT is to quickly identify any major issues or showstoppers that might render the software unusable. If the build fails this testing phase, it's considered unstable, and detailed testing is typically postponed until the severe defects are addressed. BVT acts as a quality gate, ensuring that only builds meeting a certain quality threshold move forward in the testing lifecycle, thus saving time and resources on later-stage testing of flawed builds.

Question 29

Canary Testing

Accepted Answer

Canary Testing is a technique used to detect issues by gradually releasing changes or updates to a subset of users. Often paired with A/B testing, it enables developers to evaluate and refine features based on feedback before a full release.

Question 30

Chai.js

Accepted Answer

Chai.js, often simply referred to as Chai, is a BDD/TDD (Behavior-Driven Development/Test-Driven Development) assertion library for Node.js and browsers. It pairs seamlessly with popular JavaScript testing frameworks, such as Mocha and Jasmine. Chai provides developers with the capability to express assertions in a readable language, mimicking natural language constructions.

Question 31

Change Control

Accepted Answer

Change Control, in the context of software testing, refers to a formal process used to ensure that modifications or updates to a software product or system are introduced in a controlled and coordinated manner. It involves documenting, evaluating, approving, and overseeing any changes made to the software, its environment, or associated documents during and after the development process.

Question 32

Change Requests

Accepted Answer

Change requests originate from stakeholders wishing to alter a product or its development method. They can range from defect reports to requests for new features or enhancements.

Question 33

Chaos Engineering

Accepted Answer

Chaos engineering tests a software's resilience by introducing random faults and disruptions. This method challenges applications in unpredictable ways, aiming to uncover unanticipated flaws and weaknesses.

Question 34

Clean slate

Accepted Answer

A clean slate refers to the practice of resetting a system, application, or environment to its original or default state before conducting a test or evaluation. In the context of software testing, a clean slate ensures that tests are performed under consistent and repeatable conditions, devoid of any prior residues or configurations that might influence the outcome. For instance, when testing a web application, using a fresh and cache-cleared web browser ensures that no previously stored data or settings interfere with the current test session. This approach minimizes variables and helps in achieving accurate and reliable test results.

Question 35

CMMI

Accepted Answer

The Capability Maturity Model Integration (CMMI) is a collection of best practices in engineering, service delivery, and management. It aids organizations in enhancing their delivery capabilities, ensuring customer satisfaction through continuous improvement.

Question 36

Code Coverage

Accepted Answer

Code coverage measures the extent of code that has been tested, assisting in evaluating the test suite's quality. It identifies areas not executed during testing and is a form of white box testing.

Question 37

Compatibility Testing

Accepted Answer

Assesses software performance in specific hardware, software, OS, or network conditions.

Question 38

Concurrency Testing

Accepted Answer

Measures the system's performance under simultaneous or multi-user loads.

Question 39

Control Flow Testing

Accepted Answer

Examines the paths that a program takes during its execution flow.

Question 40

Cross-Browser Testing

Accepted Answer

Ensures web applications function correctly across various web browsers.

Question 41

Cypress

Accepted Answer

Cypress is an end-to-end testing framework designed for modern web applications. Unlike many other testing solutions, Cypress operates directly within the web browser, ensuring more consistent and accurate real-world testing scenarios. It provides a rich set of features and tools for writing tests, debugging in real time, and capturing screenshots or video recordings of test runs. Cypress supports both unit testing and full end-to-end testing, making it a versatile choice for developers and QA professionals. One of its notable features is its interactive test runner that allows developers to see commands as they execute while also viewing the application under test. Built on top of technologies like Mocha, Chai, and Sinon, Cypress offers a comprehensive and user-friendly environment for web application testing.

Question 42

Database

Accepted Answer

A database is an organized collection of structured information or data, typically stored electronically in a computer system. It is designed to store, retrieve, and manage data efficiently and securely. Databases allow users to access data in various ways, from simple queries to complex transactions. They can be classified based on their data model, such as relational, document-based, key-value, and graph databases. A relational database, one of the most common types, organizes data into tables with rows and columns. Databases are integral to numerous applications and systems, from websites to banking software, ensuring data integrity, availability, and consistency. They are managed using database management systems (DBMS), which provide tools and interfaces for interacting with the stored data.

Question 43

Data Flow Testing

Accepted Answer

Centers on the variables and their values during computations and storage.

Question 44

Decision Table Testing

Accepted Answer

Decision Table Testing is a black-box software testing technique used to determine the test scenarios for complex business logic. It involves representing conditions and their respective outcomes in a tabular form, simplifying the logic by highlighting every possible combination. Each row in the decision table represents a unique combination of conditions, leading to specific actions or outcomes, ensuring that all possible scenarios are considered. This method is especially useful when dealing with systems that have various input combinations and corresponding outputs, as it helps in systematically identifying and covering all possible test cases, reducing the risk of missed scenarios.

Question 45

Defect Management

Accepted Answer

Defect Management, in software testing, refers to the systematic process of identifying, recording, tracking, and resolving defects or bugs detected in a software application. It encompasses the entire lifecycle of a defect, from its discovery to closure, ensuring that issues are appropriately addressed and resolved before the software's release.

Question 46

Dependency Testing

Accepted Answer

Dependency Testing in software testing refers to the process of examining the interactions and dependencies between different software modules or components to ensure they interact correctly. This type of testing focuses on identifying issues that might arise when one component relies on another to function properly.

Question 47

Documentation Testing

Accepted Answer

Documentation Testing in software testing refers to the process of evaluating and verifying the quality, completeness, and accuracy of documentation associated with software products. This can include user manuals, help guides, installation instructions, API documentation, and more. The primary goal is to ensure that the documentation provides clear, consistent, and correct information to its intended audience, be it end-users, administrators, or developers. Inaccuracies or ambiguities in documentation can lead to user frustration, incorrect usage of the software, or even system failures. By conducting documentation testing, organizations aim to provide a seamless user experience, reduce support costs, and enhance the overall usability and understanding of the software product.

Question 48

Dynamic Testing

Accepted Answer

Dynamic Testing, in the context of software testing, refers to the process of evaluating a software application or system through its execution. Unlike static testing, where code is analyzed without being executed, dynamic testing involves running the software to observe its behavior and identify potential defects. This form of testing checks the software's actual functionality and performance under various conditions. Common types of dynamic testing include unit testing, integration testing, system testing, and acceptance testing. The primary objective is to ensure that the software behaves as expected and meets its requirements when it is in operation.

Question 49

Edge Testing

Accepted Answer

Edge Testing, often confused with "boundary testing," is a testing technique used to identify problems that might occur at the extreme operating parameters, often referred to as the "edges" of the software's capability or limits. It focuses on testing the system's performance or behavior at or near its capacity limits or operational extremes. For instance, if a software claims to support up to 1,000 concurrent users, edge testing would involve testing the system with close to, if not exactly, 1,000 users to observe its behavior. The goal is to ensure the system operates reliably at its boundaries and to uncover potential issues that arise only under extreme conditions.

Question 50

End-to-End Testing

Accepted Answer

Tests the complete functionality of an application process from start to finish.

Question 51

Endurance Testing

Accepted Answer

Endurance Testing, in the context of software, is a type of performance testing where the system is subjected to a consistent workload or stress for an extended period. The primary goal of endurance testing is to identify how the system behaves under sustained use and to uncover potential issues like memory leaks, resource depletion, or performance degradation that might manifest only after prolonged operation. By simulating a real-world long-running environment, endurance testing helps ensure that the software remains stable, reliable, and efficient over time, free from slowdowns or crashes that could result from extended usage.

Question 52

Entry Criteria

Accepted Answer

In software testing, Entry Criteria refer to the set of predefined conditions or requirements that must be met before a particular test phase can begin. These conditions ensure that testing is conducted in a structured manner and that the process is initiated only when the prerequisites are in place. Entry Criteria can encompass various aspects, such as the availability of the test environment, the readiness of test tools and test data, the completion of previous phases, or the sign-off of certain documents. Establishing clear Entry Criteria helps in avoiding premature testing, ensuring that resources are utilized efficiently, and maintaining the quality and effectiveness of the testing process.

Question 53

Equivalence Partitioning

Accepted Answer

Equivalence Partitioning is a software testing technique used to reduce the number of test cases by dividing the input data of a software unit into partitions of equivalent data. Instead of testing every possible input, equivalence partitioning proposes that test cases can be designed for representative values from each partition. The underlying principle is that if the software behaves correctly for one value in a partition, it will behave correctly for all other values in the same partition, and vice versa.

Question 54

Error Guessing

Accepted Answer

Error Guessing is a software testing technique where the tester, relying on their experience, intuition, and knowledge of the system, tries to predict where defects might occur. Instead of following a systematic testing approach or predefined test cases, testers make educated guesses to identify potential problem areas or scenarios where the software might fail. The technique is based on the tester's familiarity with common errors, past defects, or specific system behavior. Error guessing is often used as a supplementary testing method, complementing more structured techniques, and is particularly effective in identifying unique or unanticipated issues.

Question 55

Expected Result

Accepted Answer

The anticipated outcome when a specific test case runs.

Question 56

Exploratory Testing

Accepted Answer

Exploratory testing is a dynamic process where test design and test execution happen simultaneously. It leverages the tester's experience and is especially useful under tight time constraints.

Question 57

Extreme Programming

Accepted Answer

Extreme Programming (XP) is an agile software development method. Unlike Scrum which targets project management, XP emphasizes software development best practices.

Question 58

Failover Testing

Accepted Answer

Failover Testing is a specific type of testing that evaluates a system's ability to automatically transfer control to a backup system or component when a failure occurs. The primary objective of failover testing is to ensure that, in the event of system or component malfunction, the failover process happens seamlessly without data loss or significant downtime. This test helps in validating the system's high availability and fault tolerance capabilities, ensuring that mission-critical applications remain operational even under unplanned adverse conditions. Failover testing is crucial for systems that require high availability, such as financial transaction systems, healthcare applications, and data centers.

Question 59

False Negative

Accepted Answer

In software testing, a False Negative refers to a situation where a test fails to identify a defect or issue that is actually present in the system. In other words, the test incorrectly indicates that the software is functioning correctly when, in reality, there's a fault or bug. False negatives can give a false sense of security, leading teams to believe the software is of higher quality than it actually is. This type of error is particularly concerning because it might allow critical defects to go unnoticed and reach the production environment, potentially resulting in undesired consequences for users or businesses.

Question 60

False Positive

Accepted Answer

In software testing, a False Positive refers to a situation where a test incorrectly identifies a defect or issue in the software when, in reality, there isn't one. Essentially, it's a test indicating a problem where none exists. False positives can arise due to various reasons, such as incorrect test data, flawed test conditions, or misconfigurations in the testing environment. While they might seem harmless, false positives can be detrimental as they can lead to wasted effort, resources, and time for development teams, potentially diverting attention away from genuine issues. Thus, it's essential to validate and rectify such occurrences to maintain the efficiency and accuracy of the testing process.

Question 61

FAT

Accepted Answer

Factory Acceptance Testing (FAT) confirms that newly manufactured equipment operates as intended and fulfills the customer's requirements.

Question 62

Fault Injection Testing

Accepted Answer

Introducing faults deliberately to test the system's robustness.

Question 63

Flaky Test

Accepted Answer

A flaky test in software testing refers to a test that produces inconsistent results: it might pass on one run and fail on another without any changes to the code, configuration, or environment. The unpredictability of flaky tests can undermine the reliability of a testing suite, making it challenging to determine whether a failure is due to a genuine issue in the software or merely the test's inconsistency. Flaky tests can arise from a range of factors, including timing issues, external dependencies, and non-deterministic factors. Addressing and eliminating flakiness is crucial to maintain trust in a testing process and to ensure that genuine defects are promptly identified and addressed.

Question 64

Front-end Testing

Accepted Answer

Front-end testing focuses on the user interface (UI) and its interactions within an application.

QA Wiki