Digivante Quiz Flashcards
Acceptance Testing
Acceptance testing is software testing that evaluates whether a system meets its business and user requirements. It is the final testing stage before a system is released to production. The main purpose of acceptance testing is to verify that a system: Meets all of its functional and non-functional requirements.
Difference between integration testing and regression testing
Integration Testing is performed to check the effective functionality of the units between each other. Regression Testing is done to check if old bugs have been reintroduced to the system after code modifications take place. Integration Testing is normally done before the initial deployment of the application.
Integration testing
Integration testing, also known as I&T, is a software testing method that verifies that multiple parts of a software system work together as intended.
Regression testing
Regression Testing is a type of testing in the software development cycle that runs after every change to ensure that the change introduces no unintended breaks. Regression testing addresses a common issue that developers face — the emergence of old bugs with the introduction of new changes.
Performance testing
Performance testing is the practice of evaluating how a system performs in terms of responsiveness and stability under a particular workload. Performance tests are typically executed to examine speed, robustness, reliability, and application size.
Accessibility testing
The goal of accessibility testing is to ensure websites and web-based applications can be used by people with disabilities.
Functional testing
Functional testing is a type of testing that seeks to establish whether each application feature works as per the software requirements. Each function is compared to the corresponding requirement to ascertain whether its output is consistent with the end user’s expectations.
Load testing
Load testing is the process of putting simulated demand on software, an application or website in a way that tests or demonstrates it’s behavior under various conditions.
Test case
A test case is a set of instructions that outlines how to test a specific feature of a software application. The components typically include:
A unique Id
Description
Pre-conditions
Steps to reproduce
Test data
Expected/actual results
Pass/fail status
Test plan
A “test plan” is a comprehensive document that outlines the objectives, scope, approach, resources, schedule, and overall strategy for testing a software application
Automation testing
Automation Testing refers to developing automation scripts to run tests on the software using automation tools. It uses automation scripts that can be executed repeatedly. Basically, QA automation tools perform repetitive testing tasks that were previously performed by testers manually.
Black-box testing
Focuses on the software’s functionality from the end user’s perspective, without looking at the internal code. This method is ideal for functional testing and end-user-driven scenarios. Black box testing is often used later in the development process, as the product approaches launch.
White-box testing
Involves examining the software’s internal code, architecture, and integration to identify potential issues. This method provides the most detailed view of the software and is best suited for complex situations where understanding the code’s behavior is important. White box testing is more transparent and responsive, and is beneficial for earlier development stages.
Smoke testing
“Smoke testing” refers to the broad but shallow functional testing for the main functionality of a product. It is a software testing method designed to assess the proper functioning of a software application’s fundamental features.
Testing compatibility
Testing compatibility is a technique to check the functionality of software applications across different web browsers and versions, mobile devices, databases, operating systems, hardware, and networks.
