© Manual Testing e Automation Testing ¢ Manual Testing : Human Interaction Manual testing is a process in software testing where testers manually execute test cases without the use of automation tools. In manual testing, testers carefully review and interact with the software application to identify defects, verify functionality, and ensure that it meets specified requirements. * Automation Testing Automation testing is a software testing technique where automated tools and scripts are used to execute test cases and verify the behaviour of a software application. Instead of manually executing test cases, automation testing involves writing scripts or using specialised tools to automate the repetitive and time-consuming aspects of testing. Software bidding refers to the process of submitting proposals and competing for contracts to develop or maintain software applications. It's similar to traditional bidding processes where companies compete for projects, but with a focus on software development expertise and capabilities.S/W BIDDING, Akick-off meeting, sometimes referred to as a project launch meeting, is the first official meeting held between a project team and stakeholders (often including the client) to mark the beginning of a project. It serves several key purposes: PROJECT INITIATION NOTE - - PROJECT MANAGER REQUIREMENT GATHERING - - BUSINESS ANALYST/SYSTEM ANALYST BRS: Business Requirements Specification (BRS): A high-level document outlining business needs and functionalities, guiding test design, prioritization, and evaluation. SRS: Software Requirement Specification (SRS): A detalled document outlining all software functionalities, performance expectations,and constraints, used by testers to ensure comprehensive coverage and alignment with business needs. DESIGN - - ARTISTIC/TECHNICAL HLD (High-Level Design): * Relevance in Testing: Helps testers understand the overall system architecture, functionalities, and expected behavior. This knowledge informs test planning, prioritization, and ensures comprehensive coverage. © Information for Testers: System components and their interactions. High-level functionalities and their purpose. Acceptance criteria and success metrics. System interfaces and data flow. High-level security and performance requirements. LLD (Low-Level Design): * Relevance in Testing: Provides detailed information about specific modules, data structures, and algorithms. This helps testers design more granular test cases and identify potential implementation issues. © Information for Testers: ° ° ° Detailed functionalities of each module. Data structures and algorithms used. Internal interfaces and communication protocols. Specific error handling mechanisms. Low-level performance and resource usage expectations. Key Differences for Testing:¢ HLD: Broad understanding of the system and its behaviour. LLD: Deep dive into specific implementation details. Benefits of Utilising HLD & LLD in Testing: « Improved Test Coverage: Ensures all parts of the system are tested based on their design and functionality. « Efficient Test Design: Guides the creation of relevant and effective test cases. « Early Defect Detection: identifies potential issues based on design inconsistencies or flaws. « Better Communication: Promotes collaboration between testers and developers. e UNIT TESTING: Unit testing is a fundamental software testing technique where individual units of code, often functions or classes, are tested in isolation to verify their correct functionality. It acts as the first line of defence in software quality assurance, ensuring each building block of the larger application works as intended before integration. ¢ INTEGRATION TESTING: Integration Testing: Connecting the Dots ® Integration testing bridges the gap between unit testing, which focuses on individual units of code, and system testing, which examines the entire system's functionality. It verifies how different software components or modules interact and function together as intended. . TESTING - - BLACKBOX TESTING -CODING e SYSTEM TESTING: System testing is a crucial stage in software development where the entire system is tested as a whole to ensure itmeets its intended functionality, performance, and security requirements. It acts as the final gatekeeper before deployment, verifying the system works as expected in a real-world environment. U.A TESTING: This refers to testing the usage patterns of a software application to ensure it's being used as intended and meeting user needs.