Software Testing Fundamentals

Software Testing

• Software testing is the process of evaluating a software application to ensure it meets specified requirements and functions as expected.
• The purpose of testing is to detect errors, gaps, or missing requirements compared to actual requirements.
• The goal of testing is to identify and fix bugs or defects, ensuring high quality, reliability, and performance of the software.

Objectives of Software Testing

• Finding Errors: Testing is the process of executing a program to find errors.
• Ensuring Software Reliability: Verifying the software performs as expected under various conditions ensures reliability.
• Enhancing Software Quality: Improving the overall software quality by making it more stable and decreasing failures.
• Validating User Requirements: Confirming the software meets all user and functional requirements.
• Minimizing Risks: Minimizing potential risks associated with software deployment and usage.
• Ensuring Customer Satisfaction: Delivering a quality product exceeds user expectations, increasing customer satisfaction.

Failure, Error, Fault, Defect, and Bug Terminology

• Failure: The inability of a software application to perform a required function or produce expected results under specific circumstances.
• Error: A mistake or incorrect action made by a developer, which can produce unintended outcomes.
• Fault: A fault is an undesirable code deviation from the expected behavior that results from an error in the code. This fault will show itself when the program runs.
• Defect: A defect is a deviation from expected behavior in the software. A design or coding error can also cause a defect.
• Bug: An informal term for a defect, fault, or flaw in software that prevents it from working as intended.

Skills for Software Testers

• Attention to Detail: Carefully observing to catch even minor errors or bugs.
• Analytical Thinking: Breaking down complex software to understand how components interact.
• Basic Programming Knowledge: Knowing programming languages (like Java or Python) helps understand software better, which is particularly helpful with testing automation.
• Familiarity with Testing Tools: Using tools like Selenium, JIRA, or TestRail helps handle automation, bug tracking, and test management.
• Understanding SDLC and STLC: Knowing the Software Development Life Cycle (SDLC) and Software Testing Life Cycle (STLC) ensures testing aligns with development stages.
• Good Communication Skills: Clearly communicating test results, issues, and improvements to developers and other team members.
• Problem-Solving Skills: Identifying, analyzing, and solving issues that arise during testing.
• Time Management: Planning and scheduling testing tasks, and prioritizing essential tasks to meet deadlines.

What is a Test Case?

• A test case is a set of actions performed to verify a specific feature or functionality of a software application.
• Components of a test case include: Test Case ID, Test Description, Preconditions, Test Steps, Expected Result, Actual Result, and Status.
• The purpose of test cases is to ensure all aspects of the application are tested for correctness and functionality.

Entry and Exit Criteria for Software Testing

• Entry Criteria: Conditions preceding software testing, including clear and approved requirements and defined objectives, completed test plans, prepared test cases, setup of the testing environment, access to necessary testing data, and completion of preceding phases.
• Exit Criteria: Conditions that must be met before software testing concludes, encompassing completed test cases, resolved defects, prepared summary reports, meeting quality standards, and approval from stakeholders.

Verification and Validation

• Verification: Checking if the software meets specified requirements and is being built correctly.
• Validation: Testing if the final software product meets user needs and intended functionality in a real-world scenario.

V-Model in Software Testing

• The V-Model is a software development and testing approach where each development phase is linked to a testing phase, with a clear 'V' shape.
• Each phase moves from left to right and mirrors corresponding testing, ensuring software meets specifications and functions correctly.

Quality Assurance (QA)

• QA is a process-focused approach aiming to prevent defects in the software development process by setting standards, creating guidelines, and defining procedures to ensure the product is built correctly.

Quality Control (QC)

• QC is a product-focused approach to identifying and fixing defects in the software product. QC occurs after development, involving testing to confirm the product meets quality standards.

Static Testing

• Static testing is a method of testing that checks the source code, requirements, and design documents without actually running the program.
• Common methods include reviews, walkthroughs, and inspections, focusing on early detection of errors, code clarity, and consistency with requirements.

Dynamic Testing

• Dynamic testing involves executing the source code to uncover issues in functionality, performance, and behavior.
• Common types include unit testing, integration testing, system testing, and user acceptance testing.

White Box Testing

• White box testing, also known as glass box testing, involves examining the internal structure and design of a software application, with the tester having access to the code.
• This method aims at improving code efficiency, quality, and security.

Black Box Testing

• Black box testing, known as behavioral testing, focuses on evaluating software functionality from the user's perspective, without knowledge of the internal code structure.
• It ensures the software meets specified requirements and performs functions as expected, ensuring high-level quality.

Methods of White Box Testing

• Inspection: Structured reviews focused on finding issues in code, design, or documentation.
• Walkthroughs: Informal meetings where developers outline code and design to ensure functionality and correctness.
• Technical Review: Evaluations of specific technical areas, such as security or database design, to ensure the program meets standards.

Functional Testing

• Functional testing verifies that each function of the software works according to its requirements, using specific inputs and validating outputs.
• Common methods include boundary value analysis and input variation methods.

Code Coverage Testing

• Code coverage testing measures the percentage of code executed during testing.
• It helps pinpoint and address untested parts to prevent bugs in untested sections.

Code Complexity Testing

• Involves analyzing code complexity to find areas prone to errors; this ensures code is easier to read and maintain, reducing potential bugs.