Software Testing Article

  The Levels of Testing:- 1. Unit Testing Testing individual small parts (functions or modules) Done by developers Example: Test only login function 2. Integration Testing Testing combined modules together Checks data flow between modules Example: Login module + Database connection Basic Approaches of Integration Testing 1.Top-Down Approach Testing starts from top module to lower modules Uses stubs for lower modules Main functionality tested early 2. Bottom-Up Approach Testing starts from lower modules to top modules Uses drivers to test lower modules Core logic tested first 3. Big Bang Approach All modules integrated at once No stubs or drivers used Difficult to find exact bug location 4. Critical Path Approach Test most important user flow first Focus on business-critical features Reduces major business risk Simple Comparison Approach Starts From              Uses                     ...

Test Case:- Definition A test case is a detailed step-by-step process to test a scenario. 👉 It tells “How to test?” Example (Login Test Case): Open login page Enter valid username Enter valid password Click Login Expected Result: User should see dashboard Test Scenarios:- Definition A test scenario is a high-level idea of what to test in the application. 👉 It tells “What to test?” Example: Verify Login Functionality Check Add to Cart Feature Difference Between Test Scenario & Test Case                        Test Scenario                                                                   Test Case High-level                                           ...

 Software Testing Lifecycle (STLC) Software testing is a structured process that is performed after or along with software development to ensure the application work correctly and meets user requirements. Software Testing Lifecycle (STLC) Define step by step testing activity to ensure software quality. Phases of Software testing Life Cycle SDLC 1. Requirement Analysis: This is the first phase of STLC Test Plan answer: What to test? How to test? What Happens: Study SRS document Identify testable requirements Clarify doubts with BA/Client Documents Created: RTM (Requirement Traceability Matrix) Requirement Clarification Notes Examples: Login should work with valid credentials Password must be minimum 8 characters Is OTP required?  2. Test Planning: Decide how testing will be done. Test plan is a blueprint of testing activities. It act as a contract between testing team and project team. Test plan answers: What type of testing Who will test Tools Risk and backup Timeline Importan...

 What is Playwright? =>   Playwright: Playwright is an automation testing tool used to test web applications by automatically controlling browsers. Example:   Using Playwright to automatically open a website, fill a login form, and click the login button. Key Features Works on multiple browsers at once Supports headless and headed mode Built-in auto-waiting (reduces flakiness) Supports parallel test execution Generates test reports Handles modern web apps (SPA, React, Angular, Vue) Playwright is supported by: Browsers: Chrome, Firefox, Safari (WebKit), Edge Languages: JavaScript, TypeScript, Python, Java, C# Platforms: Windows, macOS, Linux (Developed and maintained by Microsoft )

V Model 1. Verification (Static Testing) (Left arm of V model) Definition: Verification is the process of checking whether the software is being developed correctly according to the requirements without executing the code. Like: "Are we doing the job right"? What Verification Checks Requirements are clear and complete Design matches requirements Code follows design standards Documents are correct and consistent How Verification is Done Requirement reviews Design reviews Code reviews Walkthroughs & inspections Key Characteristics Static process (no code execution) Done early in SDLC Prevents defects rather than finding them later Saves time and cost Example:   If the SRS says “Password must be at least 8 characters,” verification checks whether this rule is correctly written and included in the design and code documents. Diagram: SRS (Requirements)         ↓      Design         ↓       Code    ...

 Functional & Non-Functional Software Testing What is Functional Testing? => Functional testing is a type of software testing that verifies whether each feature And functions of a software application work as per the specified requirements. It is a Black-Box testing method meaning the tester is not connected of the internal coding but only how applications work externally. Example:  website payments Gateway working as required, form submission, navigation & UI. There are six types of Functional testing 1.  Unit Testing: Testing one small part of the software to check if it works correctly. Example:  Checking if a calculator adds two numbers correctly. 2.  Integration Testing: Testing how different parts of the software work together. Example:  Checking if the login page correctly connects with the database. 3.  System Testing: Testing the complete software system as a whole. Example:  Testing the entire app to check login, dashboa...