Software Testing Overview

Dynamic testing involves executing the software to observe its behavior, while static testing analyzes the code and documentation without running the software.

Quality control focuses on detecting defects after development, while quality assurance aims to prevent defects throughout the entire development process.

A test plan typically includes the test scope, testing environment, entry and exit criteria, and testing objectives.

<p>Retesting is focused on verifying a specific defect fix, while regression testing checks if recently fixed defects or added features haven't caused issues in other parts of the application.</p> Signup and view all the answers

<p>Smoke testing checks the core functionalities of a new build to ensure it's stable enough to proceed with further testing. It's typically performed after a build is deployed.</p> Signup and view all the answers

<p>Severity refers to the impact a defect has on the application's functionality, while priority indicates how urgently the defect needs to be fixed from a business perspective.</p> Signup and view all the answers

<p>A spelling mistake in the company name on the website is a high priority but low severity defect because it doesn't affect the website's functionality, but it is important to fix it for brand consistency and user perception.</p> Signup and view all the answers

<p>A low priority and high severity defect occurs when a defect has a significant impact on the software's functionality but isn't urgent to fix immediately. For example, a crash that occurs when a user tries to order an extremely large quantity of a product would be low priority (because it's unlikely to be frequent) but high severity (because it causes a crash).</p> Signup and view all the answers

<p>The Tester is responsible for determining the severity of a bug.</p> Signup and view all the answers

<p>The requirements should be reviewed to confirm if the issue aligns with the specified requirements.</p> Signup and view all the answers

<p>Automation is preferred for tests that take a long time to execute, repetitive tests, and complex scenarios that are hard to test manually.</p> Signup and view all the answers

<p>A defect report should include a descriptive title, steps to reproduce, environment details, severity, priority, and attachments or screenshots.</p> Signup and view all the answers

<p>Positive testing verifies what the system should do, while negative testing determines what the system should not do.</p> Signup and view all the answers

<p>A test suite is a collection of related test cases.</p> Signup and view all the answers

<p>A test scenario represents what is to be tested, such as the registration process.</p> Signup and view all the answers

<p>A test environment is a combination of hardware and software, including the OS, web browser, and application under test.</p> Signup and view all the answers

<p>Release Notes summarize what occurred during the sprint including testing details, build number, issues status, and next steps.</p> Signup and view all the answers

<p>Exit criteria are conditions that must be verified to determine when testing can be stopped or deemed complete.</p> Signup and view all the answers

<p>Defect Age refers to the time difference between when a defect is detected and when it is fixed.</p> Signup and view all the answers

<p>Entry criteria are prerequisites that must be met, such as having test data and environment prepared, before starting testing.</p> Signup and view all the answers

<p>SDLC refers to Software Development Life Cycle while STLC pertains to Software Testing Life Cycle, each focusing on their respective phases.</p> Signup and view all the answers

<p>Common roles in a Scrum team include the Product Owner, Scrum Master, and Development Team members.</p> Signup and view all the answers

<p>Agile meeting types include Sprint Planning, Daily Standup, Sprint Review, and Sprint Retrospective, facilitating collaboration and progress tracking.</p> Signup and view all the answers

<p>A bug marked as 'deferred' indicates that it will be fixed but not until a future sprint.</p> Signup and view all the answers

<p>Performance testing aims to assess the responsiveness, stability, and overall performance of a system under varying workloads. It evaluates how the application behaves under pressure, ensuring it can handle expected user traffic and maintain desired levels of response time.</p> Signup and view all the answers

<p>Alpha testing is conducted internally by developers or testers within the development team, typically in a controlled environment. It focuses on identifying bugs and issues before releasing the product to external users. Beta testing, on the other hand, involves real users outside the development team who provide feedback on usability and functionality in a real-world setting.</p> Signup and view all the answers

<p>Verification checks if the product is built according to specifications and requirements, ensuring it complies with design documents. For example, verifying if a login form accurately validates input fields and user data. Validation, on the other hand, ensures the finished product meets user needs and expectations. An example could be validating if the login form design is user-friendly and intuitive for intended users.</p> Signup and view all the answers

<p>Black box testing focuses on the functional behavior of a system without examining its internal code structure. For example, testing a login feature by providing valid and invalid usernames and passwords to verify successful logins and error messages. White box testing, however, analyzes the internal code structure and logic to ensure proper functionality. This could involve reviewing the code to ensure secure password encryption and proper user authentication implementation.</p> Signup and view all the answers

<p>Gray box testing combines aspects of both black box and white box testing by leveraging partial knowledge of the system's internal structure. Testers might use knowledge of the system's architecture or design to guide their testing, while still evaluating the system's behavior as a black box. For instance, a tester might know that a login feature uses a specific database to store user credentials. They could then test the login functionality, considering potential SQL injection vulnerabilities, while also evaluating the interface's usability.</p> Signup and view all the answers

<p>Unit testing is a crucial stage in software development that focuses on testing individual components or modules of the application in isolation. The primary goal is to ensure that each unit functions correctly and meets its intended purpose. This helps identify and rectify bugs early in the development process, leading to more robust and reliable software. Typically, developers are responsible for conducting unit tests.</p> Signup and view all the answers

<p>System integration testing (SIT) primarily aims to verify how different modules or components of a system interact with each other when integrated together. Its objective is to ensure seamless communication and data flow between these modules, preventing potential integration-related issues. SIT is crucial before deploying an application to production because it helps identify and address interoperability problems early on, reducing the risk of system failures and ensuring a smooth transition to the live environment.</p> Signup and view all the answers

<p>Non-functional testing focuses on evaluating aspects of the software system that are not directly related to its specific features or functions. It assesses attributes like performance, security, usability, and reliability, rather than simply verifying if the software works as intended. Some common types of non-functional tests include:</p> <ul> <li><strong>Performance testing:</strong> Evaluates the system's responsiveness, stability, and resource utilization under varying workloads.</li> <li><strong>Usability testing:</strong> Assesses how easy and intuitive the system is to use for intended users.</li> <li><strong>Security testing:</strong> Verifies the system's ability to protect sensitive data and prevent unauthorized access.</li> </ul> Signup and view all the answers

Testing individual components by developers to ensure correctness.

Testing the interaction between integrated units, typically done by testers.

Testing the system as a whole to validate system-to-system interactions.

Testing to validate if the product meets user requirements, often done by clients.

Reviewing code and requirements documentation without executing the code.

Testing the application by executing code and verifying outputs.

Testing behavior of the application with no regard to internal code structure.

Verification checks if the product is built right; Validation checks if it is the right product for the user.

Impact of a defect on the application assessed by the tester.

Determination of defect's urgency, decided by the Product Owner.

Process of checking if a defect aligns with initial requirements.

Using scripts to run tests that are time-consuming or repetitive.

Key components include title, steps to reproduce, and severity.

Verifying that the system behaves as expected based on requirements.

Determining what the system should not do to uncover defects.

A set of steps designed to test a specific scenario, both positive and negative.

Processes to ensure products meet quality standards.

Processes to improve and ensure quality in development.

Verifying if a defect has been fixed in the software.

Testing related functions after changes to ensure no new defects.

Initial testing to check core functionalities after a new build.

Severity: impact of a defect; Priority: urgency to fix it.

Stages of a bug from creation to closure, including new, assigned, opened, closed, reopened, deferred, duplicated, or not a bug.

Prerequisites that must be met before starting testing, such as test data and environment readiness.

Conditions that must be met to conclude testing or declare a specific condition verified.

A document that links requirements to tests to verify fulfillment.

A document summarizing the sprint activities, including coverage, issues, and future actions.

The time difference between when a defect is detected and when it is fixed.

Factors that determine when to stop testing, such as coverage, deadlines, and management decisions.

Different meetings in Agile, including Sprint Planning, Daily Standup, Sprint Review, Retrospective, and Backlog Refinement.

Testing to assess system responsiveness and stability under load.

Testing to verify that the software performs its functions as specified in requirements.

Testing aspects like performance, usability, and scalability, rather than specific functions.

A mix of black and white box testing, focusing on both outputs and internal structure understanding.

The process to ensure the product is built correctly and meets specified requirements.

The process to ensure the product meets user needs and requirements post-development.

Testing based on the tester's experience and intuition when time or specifications are limited.