Software Testing Goals and Policies

Software Testing Goals and Policies

• Debugging aims to identify and fix errors in software, focusing on fixing the problem.
• Testing aims to assess the quality of software by finding defects, focusing on evaluating the software's performance.
• They are intertwined, as debugging helps improve the quality assessed during testing.

Test Case, Test Suite, and Test Oracle

• Test Case: A set of instructions for testing a specific feature or function, includes inputs, expected outputs, and execution steps to test a particular aspect.
  • Example: For a login function, a test case might include:
    • Input: Valid username and password
    • Expected Output: Successful login
    • Execution Steps: Enter username and password, click login button
• Test Suite: A collection of test cases designed to cover all aspects of a software product.
  • Example: A test suite for a shopping cart application might include test cases for adding items, removing items, checkout, payment, and order confirmation.
• Test Oracle: A source of information used to determine whether a test case has passed or failed.
  • Example: For a test case that checks if a website displays the correct price, the test oracle would be the actual price listed on the website.
  • Examples: Requirements document, previous versions of the software, expert knowledge, or a pre-defined set of expected values.

Software Testing: Verification and Validation

• Verification: Ensuring that the software fulfills its specified requirements. This involves checking if the software is built right.
• Validation: Ensuring that the software meets the user's needs and expectations. This involves checking if the right software is built.
• Software testing is a combination of both, aiming to ensure that the software is both correctly developed and meets user needs.

Software Testing as an Incremental Process

• Software testing is typically performed in multiple iterations, starting with basic functionalities and moving towards more complex features.
• **Each iteration focuses on a specific aspect of the software, building upon the previous testing phase. **
• This iterative approach helps to identify and fix defects early in the development process.

User Interface Testing and Database Testing

• User Interface (UI) Testing: Focuses on the usability and functionality of the user interface, ensuring that it meets user expectations.
  • Examples:
    • Testing navigation menus, buttons, input fields, and error messages
    • Checking for consistency in layout, color scheme, and fonts.
    • Evaluating the ease of use, responsiveness, and overall user experience.
• Database Testing: Ensures the integrity, accuracy, and performance of the database used by the software.
  • Examples:
    • Testing data storage and retrieval, validation rules, and data backup and recovery.
    • Evaluating database performance under load, scalability, and security.

Goals of Software Testing

• Find defects.
• Prevent defects.
• Improve software quality.
• Ensure user satisfaction.
• Reduce development costs.
• Meet business requirements.

Error, Fault, and Failure

• Error: A mistake made by a developer, which leads to a fault in the software.
• Fault: A flaw in the software code, which may lead to a failure.
• Failure: A deviation from the expected behaviour of the software, caused by a fault.

Test Planning and Test Plan Structure

• Test planning: The process of defining the scope, objectives, and resources for testing a software product.
• Test plan structure:
  • Introduction: Provides an overview of the test plan, the software under test, and the testing objectives.
  • Test items: Lists the specific components or features that will be tested.
  • Test environment: Describes the hardware, software, and network infrastructure used for testing.
  • Test schedule: Defines the timeframe for each testing phase and the overall testing duration.
  • Test deliverables: Specifies the documents and reports that will be produced during testing.
  • Risk assessment: Identifies potential risks and mitigation strategies.
  • Test exit criteria: Defines the conditions under which testing will be stopped.

Validation and Verification

• Verification assesses if the software conforms to its specifications.
  • Example: Checking if the software correctly implements a specific algorithm.
• Validation assesses if the software meets the users' needs and expectations.
  • Example: Ensuring that the software is user-friendly and provides the desired functionality.

Software Quality

• Software quality: The degree to which a software product meets the needs and expectations of its users.
• Quality attributes: Measurable characteristics that describe the quality of software, including:
  • Functionality: Whether the software performs its intended functions correctly.
  • Reliability: The consistency and dependability of the software.
  • Performance: How efficiently the software operates in terms of speed, response time, and resource consumption.
  • Usability: The ease with which users can learn, use, and interact with the software.
  • Maintainability: How easily the software can be modified and updated.
  • Portability: The ability of the software to run on different platforms and environments.
  • Security: The ability of the software to protect sensitive data and prevent unauthorised access.

Explore the concepts of debugging and testing within software development. Understand the definitions of test cases, test suites, and test oracles, including their roles and examples. This quiz covers essential testing goals and policies to assess software quality effectively.