<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Q-A's]]></title><description><![CDATA[Q-A's]]></description><link>https://bugdiary.pratiks-desk.in</link><image><url>https://cdn.hashnode.com/res/hashnode/image/upload/v1741774421122/77f0e020-fa28-47ca-ab91-774a7b148cd0.webp</url><title>Q-A&apos;s</title><link>https://bugdiary.pratiks-desk.in</link></image><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 03:00:51 GMT</lastBuildDate><atom:link href="https://bugdiary.pratiks-desk.in/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Types of Software Testing]]></title><description><![CDATA[🧪Types of Software Testing – Categorized by Aspects
✅ By Execution Approach
🔹 Manual Testing

Testing performed manually without automation tools.

Testers execute test cases, observe behavior, and report bugs.

Best suited for exploratory, usabili...]]></description><link>https://bugdiary.pratiks-desk.in/types-of-software-testing</link><guid isPermaLink="true">https://bugdiary.pratiks-desk.in/types-of-software-testing</guid><category><![CDATA[Software Testing]]></category><category><![CDATA[Testing]]></category><category><![CDATA[types of testing]]></category><category><![CDATA[Testing types]]></category><dc:creator><![CDATA[Pratik J]]></dc:creator><pubDate>Tue, 03 Jun 2025 06:20:08 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1750142347160/ec746581-3b50-47a5-af12-afceddf41549.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h1 id="heading-types-of-software-testing-categorized-by-aspects">🧪Types of Software Testing – Categorized by Aspects</h1>
<h2 id="heading-by-execution-approach">✅ By Execution Approach</h2>
<h3 id="heading-manual-testing">🔹 Manual Testing</h3>
<ul>
<li><p>Testing performed manually without automation tools.</p>
</li>
<li><p>Testers execute test cases, observe behavior, and report bugs.</p>
</li>
<li><p>Best suited for exploratory, usability, and ad-hoc testing.</p>
</li>
</ul>
<h3 id="heading-automation-testing">🔹 Automation Testing</h3>
<ul>
<li><p>Testing done using tools/scripts (e.g., Selenium, TestNG).</p>
</li>
<li><p>Ideal for repetitive and regression tests.</p>
</li>
<li><p>Saves time in the long run but requires initial scripting effort.</p>
</li>
</ul>
<hr />
<h2 id="heading-by-visibility-code-access">🧱 By Visibility (Code Access)</h2>
<h3 id="heading-black-box-testing">🔹 Black Box Testing</h3>
<ul>
<li><p>No access to source code.</p>
</li>
<li><p>Focus is on input-output behavior of the application.</p>
</li>
<li><p>Example: Validating login functionality via UI.</p>
</li>
</ul>
<h3 id="heading-white-box-testing">🔹 White Box Testing</h3>
<ul>
<li><p>Full access to internal code logic.</p>
</li>
<li><p>Performed mostly by developers (e.g., unit testing).</p>
</li>
<li><p>Example: Validating loops and code paths.</p>
</li>
</ul>
<h3 id="heading-gray-box-testing">🔹 Gray Box Testing</h3>
<ul>
<li><p>Partial knowledge of the codebase.</p>
</li>
<li><p>Combines black box and white box approaches.</p>
</li>
<li><p>Example: Testing UI with knowledge of database schema.</p>
</li>
</ul>
<hr />
<h2 id="heading-by-objective">🎯 By Objective</h2>
<h3 id="heading-functional-testing">🔹 Functional Testing</h3>
<ul>
<li><p>Ensures features work as per business requirements.</p>
</li>
<li><p>Includes unit, integration, system, smoke, sanity, and UAT testing.</p>
</li>
</ul>
<h3 id="heading-non-functional-testing">🔹 Non-Functional Testing</h3>
<ul>
<li><p>Evaluates performance, usability, security, and reliability.</p>
</li>
<li><p>Examples: Load Testing, Security Testing, Compatibility Testing.</p>
</li>
</ul>
<hr />
<h2 id="heading-by-timing-stage">⏱️ By Timing / Stage</h2>
<h3 id="heading-alpha-testing">🔹 Alpha Testing</h3>
<ul>
<li><p>Done by internal teams before release.</p>
</li>
<li><p>Simulates real usage in a controlled environment.</p>
</li>
</ul>
<h3 id="heading-beta-testing">🔹 Beta Testing</h3>
<ul>
<li><p>Performed by actual users in real environments.</p>
</li>
<li><p>Helps uncover issues before official release.</p>
</li>
</ul>
<h3 id="heading-user-acceptance-testing-uat">🔹 User Acceptance Testing (UAT)</h3>
<ul>
<li><p>Conducted by clients/business users.</p>
</li>
<li><p>Validates the system meets business needs and is ready for production.</p>
</li>
</ul>
<hr />
<h2 id="heading-by-scope">📦 By Scope</h2>
<h3 id="heading-static-testing">🔹 Static Testing</h3>
<ul>
<li><p>Testing without executing code.</p>
</li>
<li><p>Involves document reviews, walkthroughs, and inspections.</p>
</li>
</ul>
<h3 id="heading-dynamic-testing">🔹 Dynamic Testing</h3>
<ul>
<li><p>Testing with code execution.</p>
</li>
<li><p>Validates actual system behavior and logic.</p>
</li>
</ul>
<hr />
<h2 id="heading-other-types">🧠 Other Types</h2>
<h3 id="heading-exploratory-testing">🔹 Exploratory Testing</h3>
<ul>
<li><p>No predefined test cases.</p>
</li>
<li><p>Tester learns and tests simultaneously.</p>
</li>
<li><p>Great for early-stage or unstructured testing.</p>
</li>
</ul>
<h3 id="heading-ad-hoc-testing">🔹 Ad-hoc Testing</h3>
<ul>
<li><p>Informal, unplanned testing.</p>
</li>
<li><p>Relies on tester's experience and intuition.</p>
</li>
</ul>
<h3 id="heading-end-to-end-e2e-testing">🔹 End-to-End (E2E) Testing</h3>
<ul>
<li><p>Validates complete user workflows from start to finish.</p>
</li>
<li><p>Example: Login → Add to Cart → Checkout → Payment → Logout.</p>
</li>
</ul>
<hr />
<blockquote>
<p>✅ This structured categorization helps in understanding the breadth of testing types used across various stages and scopes in software development.</p>
</blockquote>
]]></content:encoded></item><item><title><![CDATA[Why Testing is a Crucial Step in Software Development]]></title><description><![CDATA[In the fast-paced world of software development, delivering a product quickly is important—but delivering a reliable, functional, and bug-free product is even more critical. That’s where software testing comes in.
Testing is not just an optional step...]]></description><link>https://bugdiary.pratiks-desk.in/why-testing-is-a-crucial-step-in-software-development</link><guid isPermaLink="true">https://bugdiary.pratiks-desk.in/why-testing-is-a-crucial-step-in-software-development</guid><category><![CDATA[Software Testing]]></category><dc:creator><![CDATA[Pratik J]]></dc:creator><pubDate>Fri, 18 Apr 2025 13:05:19 GMT</pubDate><content:encoded><![CDATA[<p>In the fast-paced world of software development, delivering a product quickly is important—but delivering a <strong>reliable, functional, and bug-free</strong> product is even more critical. That’s where <strong>software testing</strong> comes in.</p>
<p>Testing is not just an optional step. It is a <strong>crucial phase</strong> in the software development life cycle (SDLC), ensuring that the software meets both functional and business expectations.</p>
<hr />
<h3 id="heading-1-ensures-software-quality"><strong>1. Ensures Software Quality</strong></h3>
<p>Testing helps verify that the software performs as expected. It checks the system against defined requirements and standards, ensuring <strong>quality and consistency</strong> before the software reaches the end-users.</p>
<hr />
<h3 id="heading-2-detects-bugs-early"><strong>2. Detects Bugs Early</strong></h3>
<p>One of the primary goals of testing is to <strong>identify defects early</strong> in the development process. The earlier a bug is found, the cheaper and easier it is to fix.</p>
<blockquote>
<p><strong>Example:</strong> Fixing a bug found during development may take hours, but fixing it after deployment may take days and affect users.</p>
</blockquote>
<hr />
<h3 id="heading-3-enhances-user-experience"><strong>3. Enhances User Experience</strong></h3>
<p>Good testing ensures that the application is <strong>user-friendly, intuitive, and error-free</strong>, which leads to higher customer satisfaction and retention.</p>
<hr />
<h3 id="heading-4-supports-continuous-improvement"><strong>4. Supports Continuous Improvement</strong></h3>
<p>With practices like <strong>regression testing</strong> and <strong>automated testing</strong>, developers can continuously improve and update their software without breaking existing features.</p>
<hr />
<h3 id="heading-5-reduces-development-costs"><strong>5. Reduces Development Costs</strong></h3>
<p>While testing requires time and resources, it ultimately helps avoid <strong>costly failures</strong> in production. A well-tested product reduces the chances of post-release issues that can damage a company’s reputation and budget.</p>
<hr />
<h3 id="heading-6-validates-functionality-and-performance"><strong>6. Validates Functionality and Performance</strong></h3>
<p>Testing checks not only if the application works but also if it works <strong>correctly, efficiently, and securely</strong>. Functional, performance, and security testing all play a role in building robust applications.</p>
<hr />
<h3 id="heading-7-builds-trust-with-stakeholders"><strong>7. Builds Trust with Stakeholders</strong></h3>
<p>When a product is tested and proven stable, it builds <strong>confidence</strong> among developers, project managers, clients, and end-users. It shows professionalism and a commitment to quality.</p>
<hr />
<h3 id="heading-conclusion"><strong>Conclusion</strong></h3>
<p>Skipping testing may save time in the short term, but it creates greater risks in the long run. Whether you're developing a mobile app, a web platform, or enterprise software, testing is an <strong>essential investment</strong> that ensures your product is reliable, scalable, and successful in the market.</p>
<hr />
]]></content:encoded></item><item><title><![CDATA[Top 10 Software Testing Terms Every Beginner Should Know]]></title><description><![CDATA[Starting your journey in software testing? The world of QA (Quality Assurance) can seem overwhelming at first, but learning the common terminology is a great first step. Here are the top 10 must-know terms for every beginner:

1. Test Case
A test cas...]]></description><link>https://bugdiary.pratiks-desk.in/top-10-software-testing-terms-every-beginner-should-know</link><guid isPermaLink="true">https://bugdiary.pratiks-desk.in/top-10-software-testing-terms-every-beginner-should-know</guid><category><![CDATA[Software Testing]]></category><category><![CDATA[Manual Testing]]></category><category><![CDATA[automation testing ]]></category><dc:creator><![CDATA[Pratik J]]></dc:creator><pubDate>Fri, 18 Apr 2025 13:00:08 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1750142507787/5ed84017-ea11-46b5-8ab5-1ff732a9b647.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Starting your journey in software testing? The world of QA (Quality Assurance) can seem overwhelming at first, but learning the common terminology is a great first step. Here are the top 10 must-know terms for every beginner:</p>
<hr />
<h3 id="heading-1-test-case"><strong>1. Test Case</strong></h3>
<p>A <strong>test case</strong> is a set of actions or steps designed to verify a specific feature or functionality of an application.<br /><strong>Example:</strong> <em>Check if the login works with valid credentials.</em></p>
<hr />
<h3 id="heading-2-bug-defect"><strong>2. Bug / Defect</strong></h3>
<p>A <strong>bug</strong> (or defect) is an error or flaw in the software that causes it to produce incorrect or unexpected results.<br /><strong>Example:</strong> <em>A “Submit” button doesn’t respond when clicked.</em></p>
<hr />
<h3 id="heading-3-test-plan"><strong>3. Test Plan</strong></h3>
<p>A <strong>test plan</strong> is a document that outlines the testing strategy, objectives, schedule, required resources, and deliverables. It guides the entire testing process.</p>
<hr />
<h3 id="heading-4-test-scenario"><strong>4. Test Scenario</strong></h3>
<p>A <strong>test scenario</strong> describes a high-level situation or functionality to be tested. It can lead to multiple test cases.<br /><strong>Example:</strong> <em>Test the checkout process on an e-commerce site.</em></p>
<hr />
<h3 id="heading-5-regression-testing"><strong>5. Regression Testing</strong></h3>
<p><strong>Regression testing</strong> ensures that new code changes haven’t broken existing features. It's done after updates or bug fixes.</p>
<hr />
<h3 id="heading-6-smoke-testing"><strong>6. Smoke Testing</strong></h3>
<p><strong>Smoke testing</strong> is a quick round of basic tests to check if the major functions of an application work after a build. It’s often called a “build verification test.”</p>
<hr />
<h3 id="heading-7-functional-testing"><strong>7. Functional Testing</strong></h3>
<p><strong>Functional testing</strong> verifies that each feature works as expected according to the requirements.<br /><strong>Example:</strong> <em>Ensuring the password reset feature sends an email.</em></p>
<hr />
<h3 id="heading-8-automation-testing"><strong>8. Automation Testing</strong></h3>
<p><strong>Automation testing</strong> uses tools and scripts to execute test cases automatically, making it faster and more reliable for repetitive tests.</p>
<hr />
<h3 id="heading-9-manual-testing"><strong>9. Manual Testing</strong></h3>
<p><strong>Manual testing</strong> involves human testers executing test cases without tools. It’s useful for UI, usability, and exploratory testing.</p>
<hr />
<h3 id="heading-10-test-data"><strong>10. Test Data</strong></h3>
<p><strong>Test data</strong> is the input used during testing to simulate real-world user actions. It includes usernames, passwords, IDs, etc.</p>
<hr />
<h3 id="heading-conclusion"><strong>Conclusion</strong></h3>
<p>These basic terms form the foundation of software testing. As you grow your skills, understanding these concepts will help you communicate clearly, write better test cases, and become more confident in real-world QA projects.</p>
<hr />
]]></content:encoded></item><item><title><![CDATA[TestNG Q/A]]></title><description><![CDATA[its all about TestNG]]></description><link>https://bugdiary.pratiks-desk.in/testng-qa</link><guid isPermaLink="true">https://bugdiary.pratiks-desk.in/testng-qa</guid><dc:creator><![CDATA[Pratik J]]></dc:creator><pubDate>Tue, 18 Mar 2025 08:01:27 GMT</pubDate><content:encoded><![CDATA[<p>its all about TestNG</p>
]]></content:encoded></item><item><title><![CDATA[Jira Project Management Tool Q/A]]></title><description><![CDATA[What is JIRA?  JIRA is a project management and issue-tracking tool developed by Atlassian. It is widely used for bug tracking, Agile project management, and workflow automation.

What are the key features of JIRA?  JIRA offers issue tracking, custom...]]></description><link>https://bugdiary.pratiks-desk.in/jira-project-management-tool-qa</link><guid isPermaLink="true">https://bugdiary.pratiks-desk.in/jira-project-management-tool-qa</guid><category><![CDATA[JIRA]]></category><category><![CDATA[project management tool]]></category><category><![CDATA[Project Management Tools]]></category><category><![CDATA[Q&A]]></category><dc:creator><![CDATA[Pratik J]]></dc:creator><pubDate>Wed, 12 Mar 2025 09:57:13 GMT</pubDate><content:encoded><![CDATA[<ul>
<li><p><strong>What is JIRA?</strong><br />  JIRA is a project management and issue-tracking tool developed by Atlassian. It is widely used for bug tracking, Agile project management, and workflow automation.</p>
</li>
<li><p><strong>What are the key features of JIRA?</strong><br />  JIRA offers issue tracking, customizable workflows, Agile boards (Scrum and Kanban), dashboards, reports, automation, and integrations with other tools like Confluence, Bitbucket, and Jenkins.</p>
</li>
<li><p><strong>What are issues in JIRA?</strong><br />  Issues are tasks, bugs, or feature requests that need to be tracked and managed in a project. Each issue has a unique ID and follows a defined workflow from creation to completion.</p>
</li>
<li><p><strong>What are the different issue types in JIRA?</strong><br />  Common issue types include Epics (large features), Stories (user requirements), Tasks (work items), Subtasks (smaller parts of tasks), and Bugs (defects in software).</p>
</li>
<li><p><strong>What is a workflow in JIRA?</strong><br />  A workflow defines the lifecycle of an issue, including statuses like To Do, In Progress, and Done. It ensures tasks follow a structured path from creation to resolution.</p>
</li>
<li><p><strong>What are Agile boards in JIRA?</strong><br />  Agile boards (Scrum and Kanban) help teams visualize work progress. Scrum boards are used for sprint-based development, while Kanban boards support continuous workflow without fixed iterations.</p>
</li>
<li><p><strong>What is JIRA Query Language (JQL)?</strong><br />  JQL is a flexible search language that helps users filter and find issues using custom queries. It allows complex searches like finding all issues assigned to a specific user or issues closed in the last week.</p>
</li>
<li><p><strong>What are components in JIRA?</strong><br />  Components are subcategories within a project that help organize and group related issues. They allow better tracking of tasks related to specific features or modules.</p>
</li>
<li><p><strong>What are labels in JIRA?</strong><br />  Labels are custom tags used to categorize issues. They help in quickly searching and grouping issues across multiple projects based on common themes.</p>
</li>
<li><p><strong>What is a backlog in JIRA?</strong><br />  A backlog is a prioritized list of work items that need to be completed. It is commonly used in Agile projects to store upcoming tasks before they are assigned to sprints.</p>
</li>
<li><p><strong>What is the difference between Scrum and Kanban boards in JIRA?</strong><br />  Scrum boards follow sprint-based planning with fixed timelines, while Kanban boards focus on continuous delivery by limiting work in progress and visualizing workflow.</p>
</li>
<li><p><strong>How does JIRA handle permissions?</strong><br />  JIRA provides role-based access control, where administrators can define user roles and permissions. This ensures only authorized users can create, edit, or transition issues.</p>
</li>
<li><p><strong>What are versions and releases in JIRA?</strong><br />  Versions help track software releases by grouping related issues. They allow teams to monitor progress and ensure that all necessary tasks are completed before a product update.</p>
</li>
<li><p><strong>What is an Epic in JIRA?</strong><br />  An Epic is a large user story or feature that spans multiple sprints. It is broken down into smaller Stories and Tasks for better tracking and management.</p>
</li>
<li><p><strong>How can you automate tasks in JIRA?</strong><br />  JIRA allows users to set up automation rules to perform actions like assigning issues, updating statuses, and sending notifications based on specific triggers.</p>
</li>
<li><p><strong>What are subtasks in JIRA?</strong><br />  Subtasks divide a parent task into smaller, manageable parts. They help teams work on different aspects of the same task efficiently.</p>
</li>
<li><p><strong>How does JIRA integrate with other tools?</strong><br />  JIRA integrates with various tools like Confluence (documentation), Bitbucket/GitHub (code management), Slack (communication), and Jenkins (CI/CD pipelines).</p>
</li>
<li><p><strong>What is a filter in JIRA?</strong><br />  Filters save custom JQL queries for quick access to frequently searched issues. Users can also share filters with team members for consistency.</p>
</li>
<li><p><strong>How do you clone an issue in JIRA?</strong><br />  Cloning creates a duplicate of an issue while allowing modifications. It is useful when similar tasks need to be repeated with minor changes.</p>
</li>
<li><p><strong>What is bulk editing in JIRA?</strong><br />  Bulk editing enables users to update multiple issues simultaneously, such as changing status, reassigning tasks, or updating priority.</p>
</li>
<li><p><strong>What is the difference between a team-managed and company-managed project in JIRA?</strong><br />  Team-managed projects allow teams to configure workflows and settings independently, while company-managed projects provide standardized settings controlled by administrators.</p>
</li>
<li><p><strong>How do you track time in JIRA?</strong><br />  JIRA allows users to log work hours, estimate effort, and generate time-tracking reports to monitor team productivity.</p>
</li>
<li><p><strong>What is the purpose of dashboards in JIRA?</strong><br />  Dashboards provide a visual overview of project progress, team workload, and key metrics using customizable widgets and charts.</p>
</li>
<li><p><strong>What is JIRA Service Management (JSM)?</strong><br />  JIRA Service Management is an ITSM tool used for handling customer support, incident management, and service requests with SLAs.</p>
</li>
<li><p><strong>How can you create a custom workflow in JIRA?</strong><br />  Custom workflows can be designed by defining statuses, transitions, conditions, validators, and post functions in the workflow editor.</p>
</li>
<li><p><strong>What are post functions in JIRA workflows?</strong><br />  Post functions are automated actions that execute after an issue transition, such as updating fields, sending notifications, or creating subtasks.</p>
</li>
<li><p><strong>What is the Release Hub in JIRA?</strong><br />  The Release Hub helps track the progress of software releases by ensuring that all required issues are completed before deployment.</p>
</li>
<li><p><strong>How does JIRA support CI/CD pipelines?</strong><br />  JIRA integrates with CI/CD tools like Jenkins, Bitbucket, and Bamboo to track builds, automate deployments, and link issues to code commits.</p>
</li>
<li><p><strong>What are SLAs in JIRA Service Management?</strong><br />  Service Level Agreements (SLAs) define response and resolution time targets for handling customer requests and support tickets.</p>
</li>
<li><p><strong>How can you migrate data in JIRA?</strong><br />  JIRA allows data migration through CSV import/export, JSON, and API-based integrations, making it easy to move projects between different instances.</p>
</li>
<li><p><strong>How do you create a project in JIRA?</strong><br />  You can create a project in JIRA by selecting "Create Project," choosing a project type (Scrum, Kanban, or Team-managed), and configuring settings like workflows, issue types, and permissions.</p>
</li>
<li><p><strong>What is the difference between Bug, Task, and Story in JIRA?</strong><br />  A <strong>Bug</strong> represents a defect or issue in the system, a <strong>Task</strong> is a work item that needs to be completed, and a <strong>Story</strong> describes a user requirement or feature that contributes to a larger goal.</p>
</li>
<li><p><strong>How do you transition an issue in JIRA?</strong><br />  An issue can be transitioned by clicking on its status and selecting the next stage in the workflow (e.g., from "To Do" to "In Progress"). The workflow determines the allowed transitions.</p>
</li>
<li><p><strong>What are project roles in JIRA?</strong><br />  Project roles define user permissions within a project. Common roles include <strong>Administrator</strong> (full control), <strong>Developer</strong> (can edit and transition issues), and <strong>Viewer</strong> (can only view issues).</p>
</li>
<li><p><strong>How do you create a custom field in JIRA?</strong><br />  Custom fields can be added from JIRA’s admin settings. They allow users to collect additional information beyond the default fields (e.g., adding a "Severity" field for bugs).</p>
</li>
<li><p><strong>What are issue priorities in JIRA?</strong><br />  JIRA provides default priorities like Low, Medium, High, and Critical. These help teams decide which tasks or bugs should be addressed first.</p>
</li>
<li><p><strong>What is a Sprint in JIRA?</strong><br />  A Sprint is a fixed-length time period (usually 1-4 weeks) in which teams work on completing tasks and stories. It is used in Scrum projects to deliver incremental progress.</p>
</li>
<li><p><strong>How do you start and end a Sprint in JIRA?</strong><br />  A Sprint is started by selecting issues from the backlog and clicking "Start Sprint." It ends when all issues are completed, or the time expires, after which a Sprint retrospective is conducted.</p>
</li>
<li><p><strong>What is a Resolution in JIRA?</strong><br />  The Resolution field indicates how an issue was closed (e.g., Fixed, Won't Fix, Duplicate). It must be set before an issue moves to the "Done" status.</p>
</li>
<li><p><strong>How do you set up notifications in JIRA?</strong><br />  JIRA allows you to configure notification schemes that alert users via email when specific actions occur, such as issue assignment or status changes.</p>
</li>
<li><p><strong>What are watchers in JIRA?</strong><br />  Watchers are users who get notifications about changes to an issue, even if they are not assigned to it. Anyone can add themselves or others as watchers.</p>
</li>
<li><p><strong>What is the difference between Clone and Move in JIRA?</strong><br />  <strong>Cloning</strong> creates a duplicate of an issue in the same project, while <strong>Moving</strong> transfers an issue to another project or changes its issue type.</p>
</li>
<li><p><strong>How do you manage dependencies in JIRA?</strong><br />  JIRA allows you to link issues using relationships like "Blocks," "Is Blocked By," "Relates To," and "Duplicate" to indicate dependencies between tasks.</p>
</li>
<li><p><strong>What is a Board in JIRA?</strong><br />  A Board (Scrum or Kanban) visually represents project tasks and their progress. It helps teams manage workflows and track work items efficiently.</p>
</li>
<li><p><strong>How do you create reports in JIRA?</strong><br />  JIRA provides built-in reports like Burndown Charts, Velocity Charts, and Sprint Reports to analyze progress, team performance, and issue resolution trends.</p>
</li>
<li><p><strong>What is a Burndown Chart in JIRA?</strong><br />  A Burndown Chart shows the amount of work remaining in a Sprint, helping teams monitor progress and adjust their workload if needed.</p>
</li>
<li><p><strong>What is an Issue Type Scheme in JIRA?</strong><br />  An Issue Type Scheme defines which issue types are available in a project. It helps standardize issue tracking across multiple projects.</p>
</li>
<li><p><strong>How do you track progress in JIRA?</strong><br />  Progress can be tracked using status updates, reports, dashboards, and visual tools like Agile boards and Burndown Charts.</p>
</li>
<li><p><strong>What is the Epic Link in JIRA?</strong><br />  The Epic Link connects a Story, Task, or Bug to a larger Epic, allowing teams to track progress on major features.</p>
</li>
<li><p><strong>How do you reopen a closed issue in JIRA?</strong><br />  If an issue was incorrectly marked as resolved, it can be reopened by transitioning it back to an active status like "To Do" or "In Progress."</p>
</li>
<li><p><strong>What is a Fix Version in JIRA?</strong><br />  A Fix Version represents a product release or milestone in which a bug or feature is scheduled to be included.</p>
</li>
<li><p><strong>What is an Assignee in JIRA?</strong><br />  The Assignee is the person responsible for completing a task or resolving an issue. Assignments can be done manually or automatically using rules.</p>
</li>
<li><p><strong>What is the difference between a Public and Private Dashboard in JIRA?</strong><br />  A <strong>Public Dashboard</strong> can be shared with multiple users or teams, while a <strong>Private Dashboard</strong> is only visible to the creator.</p>
</li>
<li><p><strong>How do you delete an issue in JIRA?</strong><br />  Issues can be deleted by users with the necessary permissions, but deletion is usually discouraged as it removes all history and data permanently.</p>
</li>
<li><p><strong>How do you archive issues in JIRA?</strong><br />  Instead of deleting, JIRA allows issues to be archived by setting their status to "Closed" or moving them to a hidden project for record-keeping.</p>
</li>
<li><p><strong>What is the use of the Audit Log in JIRA?</strong><br />  The Audit Log records all significant changes made in JIRA, such as workflow updates, user modifications, and permission changes.</p>
</li>
<li><p><strong>What is the difference between Issue Security and Project Permissions in JIRA?</strong><br />  <strong>Issue Security</strong> controls access to individual issues within a project, while <strong>Project Permissions</strong> define what users can do across the entire project.</p>
</li>
<li><p><strong>What is a Kanban WIP Limit in JIRA?</strong><br />  Work-In-Progress (WIP) Limits restrict the number of tasks that can be worked on simultaneously to maintain focus and efficiency.</p>
</li>
<li><p><strong>How do you link Confluence with JIRA?</strong><br />  JIRA integrates with Confluence to display project reports, link documentation, and automatically update issue status based on project updates.</p>
</li>
<li><p><strong>What is JIRA Align?</strong><br />  JIRA Align is an enterprise solution that connects JIRA teams with business strategy, helping organizations scale Agile practices across multiple teams.</p>
</li>
<li><p><strong>How do you create an SLA in JIRA Service Management?</strong><br />  SLAs are configured by defining response and resolution time goals based on issue priority and customer agreements.</p>
</li>
<li><p><strong>What is Insight in JIRA Service Management?</strong><br />  Insight is an asset and configuration management tool within JIRA that helps teams track hardware, software, and IT resources.</p>
</li>
<li><p><strong>What is the difference between Cloud and Server versions of JIRA?</strong><br />  JIRA Cloud is a hosted solution managed by Atlassian, while JIRA Server is self-hosted and gives organizations full control over their instance.</p>
</li>
<li><p><strong>How do you export issues from JIRA?</strong><br />  Issues can be exported in CSV, Excel, or JSON format for reporting, analysis, or migration to another JIRA instance.</p>
</li>
<li><p><strong>What is JIRA Portfolio?</strong><br />  JIRA Portfolio (now Advanced Roadmaps) helps teams plan, track, and manage multiple projects, aligning them with business goals.</p>
</li>
<li><p><strong>What is the importance of Roadmaps in JIRA?</strong><br />  Roadmaps provide a high-level view of project goals, Epics, and planned releases, helping teams align their work with business objectives.</p>
</li>
<li><p><strong>How do you handle performance issues in JIRA?</strong><br />  Performance can be optimized by archiving old issues, limiting the number of active workflows, using indexing, and ensuring proper database management.</p>
</li>
<li><p><strong>What is a Global Permission in JIRA?</strong><br />  Global Permissions apply across all JIRA projects and control actions like creating new projects, managing users, and accessing JIRA settings.</p>
</li>
</ul>
<div data-node-type="callout">
<div data-node-type="callout-emoji">💡</div>
<div data-node-type="callout-text"><a target="_self" href="https://techbrary.hashnode.dev/jira-project-management-tool">Steps to sign up Jira</a></div>
</div>]]></content:encoded></item><item><title><![CDATA[Automation Testing Q/A]]></title><description><![CDATA[What is Automation Testing?

Automation testing is the process of using software tools to execute test cases automatically, reducing manual effort and improving efficiency.


What are the benefits of Automation Testing?

Faster test execution

Reduce...]]></description><link>https://bugdiary.pratiks-desk.in/automation-testing-qa</link><guid isPermaLink="true">https://bugdiary.pratiks-desk.in/automation-testing-qa</guid><category><![CDATA[Testing]]></category><category><![CDATA[automation testing ]]></category><category><![CDATA[#softwaretesting #testing #qa #softwaredevelopment #software #automationtesting #softwaredeveloper #softwareengineer #qualityassurance #manualtesting #testautomation #softwaretester #softwareengineering #qaengineer #testers #programming #selenium #jobs #softwarecompany #agiletesting #technology #developer #career #softwaresolutions #softwareengineers #java #jobsearch #softwaredevelopers #devops #qajobs]]></category><category><![CDATA[Software Testing]]></category><category><![CDATA[Mastering Software Testing Interviews]]></category><dc:creator><![CDATA[Pratik J]]></dc:creator><pubDate>Mon, 10 Mar 2025 16:47:05 GMT</pubDate><content:encoded><![CDATA[<ol>
<li><p>What is Automation Testing?</p>
<ul>
<li>Automation testing is the process of using software tools to execute test cases automatically, reducing manual effort and improving efficiency.</li>
</ul>
</li>
<li><p>What are the benefits of Automation Testing?</p>
<ul>
<li><p>Faster test execution</p>
</li>
<li><p>Reduces human errors</p>
</li>
<li><p>Supports regression testing</p>
</li>
<li><p>Saves time and cost</p>
</li>
<li><p>Increases test coverage</p>
</li>
</ul>
</li>
<li><p>When should you automate a test case?</p>
<ul>
<li><p>When the test is repetitive</p>
</li>
<li><p>When the test requires large datasets</p>
</li>
<li><p>When the test is time-consuming if done manually</p>
</li>
<li><p>When the test has stable functionality</p>
</li>
</ul>
</li>
<li><p>Which tools are used for Automation Testing?</p>
<ul>
<li><p>Selenium</p>
</li>
<li><p>Cypress</p>
</li>
<li><p>Appium</p>
</li>
<li><p>JUnit</p>
</li>
<li><p>TestNG</p>
</li>
<li><p>Cucumber</p>
</li>
<li><p>Playwright</p>
</li>
</ul>
</li>
<li><p>What is Selenium?</p>
<ul>
<li>Selenium is an open-source automation tool for web applications that supports multiple programming languages like Java, Python, and C#.</li>
</ul>
</li>
<li><p>What are the components of Selenium?</p>
<ul>
<li><p>Selenium WebDriver – Automates browser actions</p>
</li>
<li><p>Selenium IDE – A record and playback tool</p>
</li>
<li><p>Selenium Grid – Executes tests on multiple machines</p>
</li>
</ul>
</li>
<li><p>What are different locators in Selenium?</p>
<ul>
<li><p>ID</p>
</li>
<li><p>Name</p>
</li>
<li><p>Class Name</p>
</li>
<li><p>CSS Selector</p>
</li>
<li><p>XPath</p>
</li>
</ul>
</li>
<li><p>How do you handle dropdowns in Selenium?</p>
<ul>
<li><p>Use the Select class to interact with dropdown elements</p>
</li>
<li><p>Select options by visible text, value, or index</p>
</li>
</ul>
</li>
<li><p>How do you handle alerts in Selenium?</p>
<ul>
<li><p>Switch to the alert window</p>
</li>
<li><p>Accept or dismiss the alert</p>
</li>
</ul>
</li>
<li><p>What is a Test Automation Framework?</p>
<ul>
<li>A structured approach to automation testing using reusable code and best practices</li>
</ul>
</li>
<li><p>Types of Test Automation Frameworks?</p>
<ul>
<li><p>Keyword-Driven</p>
</li>
<li><p>Data-Driven</p>
</li>
<li><p>Hybrid Framework</p>
</li>
<li><p>Page Object Model (POM)</p>
</li>
</ul>
</li>
<li><p>What is Page Object Model (POM)?</p>
<ul>
<li>A design pattern that separates test logic from UI elements by creating separate classes for each page</li>
</ul>
</li>
<li><p>What is the difference between JUnit and TestNG?</p>
<ul>
<li><p>JUnit is used for unit testing and is simpler than TestNG</p>
</li>
<li><p>TestNG provides better reporting, parallel execution, and data-driven testing</p>
</li>
</ul>
</li>
<li><p>What is Data-Driven Testing?</p>
<ul>
<li>Running test cases with multiple sets of input data, often stored in Excel or CSV</li>
</ul>
</li>
<li><p>How do you handle dynamic elements in Selenium?</p>
<ul>
<li>Use XPath functions like contains, starts-with, and following-sibling</li>
</ul>
</li>
<li><p>How do you perform Parallel Testing in Selenium?</p>
<ul>
<li>Modify the TestNG XML file to enable parallel execution</li>
</ul>
</li>
<li><p>What is API Testing?</p>
<ul>
<li>API testing checks if an API works correctly by sending requests and validating responses</li>
</ul>
</li>
<li><p>Which tools are used for API Testing?</p>
<ul>
<li><p>Postman</p>
</li>
<li><p>REST Assured</p>
</li>
<li><p>SoapUI</p>
</li>
</ul>
</li>
<li><p>What is Mobile Automation Testing?</p>
<ul>
<li>Mobile Automation Testing uses tools like Appium to automate testing on mobile apps</li>
</ul>
</li>
<li><p>What is Appium?</p>
<ul>
<li>An open-source tool for automating mobile applications on Android and iOS</li>
</ul>
</li>
<li><p>What is Continuous Integration (CI)?</p>
<ul>
<li>A practice where developers frequently merge code into a shared repository, and automated tests run to detect issues early</li>
</ul>
</li>
<li><p>What is Jenkins?</p>
<ul>
<li>An open-source CI/CD tool that automates testing and deployment</li>
</ul>
</li>
<li><p>How do you integrate Selenium with Jenkins?</p>
<ul>
<li><p>Install Selenium in Jenkins</p>
</li>
<li><p>Configure a Job</p>
</li>
<li><p>Run tests using a Maven or Gradle build</p>
</li>
</ul>
</li>
<li><p>What is Regression Testing?</p>
<ul>
<li>Testing to ensure new changes do not affect existing functionality</li>
</ul>
</li>
<li><p>What is Smoke Testing?</p>
<ul>
<li>A quick check to verify basic functionality before detailed testing</li>
</ul>
</li>
<li><p>What is Sanity Testing?</p>
<ul>
<li>A focused test to verify specific bug fixes or changes</li>
</ul>
</li>
<li><p>What is Functional Testing?</p>
<ul>
<li>Testing if the application meets functional requirements</li>
</ul>
</li>
<li><p>What is Performance Testing?</p>
<ul>
<li>Testing system speed, responsiveness, and stability under load</li>
</ul>
</li>
<li><p>What is Stress Testing?</p>
<ul>
<li>Checking how a system behaves under extreme conditions</li>
</ul>
</li>
<li><p>What is Load Testing?</p>
<ul>
<li>Evaluating system performance under expected user loads</li>
</ul>
</li>
<li><p>What is Soak Testing?</p>
<ul>
<li>Running the system for a long duration to check stability</li>
</ul>
</li>
<li><p>What is Security Testing?</p>
<ul>
<li>Testing the application's ability to protect data and resist attacks</li>
</ul>
</li>
<li><p>What is User Acceptance Testing (UAT)?</p>
<ul>
<li>Final testing by end users before deployment</li>
</ul>
</li>
<li><p>What is TestNG used for?</p>
<ul>
<li>Running automated tests with better control and reporting</li>
</ul>
</li>
<li><p>What is the role of a Test Script?</p>
<ul>
<li>A set of instructions that automate test execution</li>
</ul>
</li>
<li><p>What is a Test Case in Automation Testing?</p>
<ul>
<li>A set of preconditions, inputs, and expected results used to validate an application</li>
</ul>
</li>
<li><p>What are Assertions in Selenium?</p>
<ul>
<li>Assertions help verify expected results, commonly using SoftAssert or HardAssert</li>
</ul>
</li>
<li><p>What is the difference between Verification and Validation?</p>
<ul>
<li>Verification checks if the product is built correctly, while Validation checks if the right product is built</li>
</ul>
</li>
<li><p>What is XPath in Selenium?</p>
<ul>
<li>A query language to navigate and locate elements in XML documents and web pages</li>
</ul>
</li>
<li><p>What is the difference between Absolute and Relative XPath?</p>
<ul>
<li>Absolute XPath starts from the root node, whereas Relative XPath starts from any node in between</li>
</ul>
</li>
<li><p>What is Headless Browser Testing?</p>
<ul>
<li>Running tests in a browser without a graphical user interface to improve execution speed</li>
</ul>
</li>
<li><p>What is Implicit Wait in Selenium?</p>
<ul>
<li>A global wait that makes WebDriver wait for a defined time before throwing an exception</li>
</ul>
</li>
<li><p>What is Explicit Wait in Selenium?</p>
<ul>
<li>A specific wait applied to an element until a condition is met</li>
</ul>
</li>
<li><p>What is Fluent Wait in Selenium?</p>
<ul>
<li>A wait that checks for a condition at regular intervals before timing out</li>
</ul>
</li>
<li><p>What are Test Suites in Selenium?</p>
<ul>
<li>A collection of test cases that are grouped and executed together</li>
</ul>
</li>
<li><p>What is the difference between Build and Release in software testing?</p>
<ul>
<li>A Build is a version of the software for testing, while a Release is a version deployed to users</li>
</ul>
</li>
<li><p>What is the use of Cucumber in Automation Testing?</p>
<ul>
<li>Cucumber allows writing test cases in plain English using Behavior-Driven Development (BDD)</li>
</ul>
</li>
<li><p>What are the advantages of using Maven in Selenium?</p>
<ul>
<li><p>Simplifies project build management</p>
</li>
<li><p>Manages dependencies</p>
</li>
<li><p>Automates test execution</p>
</li>
</ul>
</li>
<li><p>What is the purpose of the TestNG XML file?</p>
<ul>
<li>It configures test execution, parallel execution, and test groups</li>
</ul>
</li>
<li><p>What is Cross-Browser Testing?</p>
<ul>
<li>Testing an application across different browsers like Chrome, Firefox, and Edge to ensure compatibility</li>
</ul>
</li>
</ol>
]]></content:encoded></item><item><title><![CDATA[Manual Testing Q/A]]></title><description><![CDATA[What is Manual Testing? Manual testing is the process of manually executing test cases without using automation tools to identify bugs and ensure the software functions as expected.

What is the difference between Manual Testing and Automation Testin...]]></description><link>https://bugdiary.pratiks-desk.in/manual-testing-qa</link><guid isPermaLink="true">https://bugdiary.pratiks-desk.in/manual-testing-qa</guid><category><![CDATA[Manual Testing]]></category><category><![CDATA[Testing]]></category><category><![CDATA[manual testing questions for interview]]></category><dc:creator><![CDATA[Pratik J]]></dc:creator><pubDate>Mon, 10 Mar 2025 12:59:46 GMT</pubDate><content:encoded><![CDATA[<ol>
<li><p><strong>What is Manual Testing?</strong><br /> Manual testing is the process of manually executing test cases without using automation tools to identify bugs and ensure the software functions as expected.</p>
</li>
<li><p><strong>What is the difference between Manual Testing and Automation Testing?</strong></p>
<ul>
<li><p>Manual Testing requires human effort to execute test cases, while Automation Testing uses scripts and tools.</p>
</li>
<li><p>Manual Testing is slower compared to Automation Testing.</p>
</li>
<li><p>Automation Testing is useful for repetitive tasks like regression testing, whereas Manual Testing is better for usability and exploratory testing.</p>
</li>
</ul>
</li>
<li><p><strong>What are the different types of Manual Testing?</strong></p>
<ul>
<li><p>Functional Testing</p>
</li>
<li><p>Usability Testing</p>
</li>
<li><p>Smoke Testing</p>
</li>
<li><p>Regression Testing</p>
</li>
<li><p>Exploratory Testing</p>
</li>
<li><p>Ad-hoc Testing</p>
</li>
</ul>
</li>
<li><p><strong>What are Test Cases?</strong><br /> A test case is a set of conditions and steps used to verify if a software application functions correctly.</p>
<p> <strong>Example:</strong></p>
<ul>
<li><p>Step 1: Open the login page</p>
</li>
<li><p>Step 2: Enter valid username and password</p>
</li>
<li><p>Step 3: Click the "Login" button</p>
</li>
<li><p>Expected Result: User should be logged in successfully</p>
</li>
</ul>
</li>
<li><p><strong>How would you test a login page manually?</strong></p>
<ul>
<li><p>Check login with valid and invalid credentials.</p>
</li>
<li><p>Verify "Forgot Password" functionality.</p>
</li>
<li><p>Check UI elements such as buttons and fields.</p>
</li>
<li><p>Test session timeout and security aspects.</p>
</li>
</ul>
</li>
<li><p><strong>What is Regression Testing?</strong><br /> Regression testing ensures that recent code changes do not break existing functionalities.</p>
</li>
<li><p><strong>What is the difference between Smoke and Sanity Testing?</strong></p>
<ul>
<li><p>Smoke Testing checks major functionalities of the application to ensure basic stability.</p>
</li>
<li><p>Sanity Testing verifies specific bug fixes or new features to confirm they work as expected.</p>
</li>
</ul>
</li>
<li><p><strong>What is Exploratory Testing?</strong></p>
<p> Exploratory testing is performed without predefined test cases, allowing testers to explore the application and find unexpected defects.</p>
</li>
<li><p><strong>What are Severity and Priority in Bug Tracking?</strong></p>
<ul>
<li><p><strong>Severity</strong> refers to the impact of the bug on the system (Critical, High, Medium, Low).</p>
</li>
<li><p><strong>Priority</strong> refers to the urgency of fixing the bug (High, Medium, Low).</p>
<p>  <strong>Example:</strong></p>
<p>  High Severity, Low Priority: A crash in an admin-only feature.</p>
<p>  Low Severity, High Priority: A spelling mistake on the homepage title.</p>
</li>
</ul>
</li>
<li><p><strong>Which bug tracking tools have you used?</strong></p>
<ul>
<li><p>JIRA</p>
</li>
<li><p>Bugzilla</p>
</li>
<li><p>Trello</p>
</li>
</ul>
</li>
<li><p><strong>What are the different levels of testing?</strong></p>
<ul>
<li><p>Unit Testing</p>
</li>
<li><p>Integration Testing</p>
</li>
<li><p>System Testing</p>
</li>
<li><p>User Acceptance Testing (UAT)</p>
</li>
</ul>
</li>
<li><p><strong>What is the difference between White Box and Black Box Testing?</strong></p>
<p>White Box Testing checks internal code and logic (done by developers), while Black Box Testing tests functionality without knowing internal code (done by testers).</p>
</li>
<li><p>What is a Test Plan and what does it include?</p>
<p>A Test Plan is a document that outlines the testing scope, objectives, schedule, resources, and deliverables. It includes:</p>
<ul>
<li><p>Test strategy</p>
</li>
<li><p>Test scope</p>
</li>
<li><p>Testing schedule</p>
</li>
<li><p>Test environment details</p>
</li>
<li><p>Test deliverables</p>
</li>
</ul>
</li>
<li><p><strong>What is a Test Scenario?</strong><br />A test scenario is a high-level description of a functionality to be tested.</p>
</li>
<li><p><strong>What is the difference between a Test Case and a Test Script?</strong><br />A test case is a step-by-step document to verify a feature, while a test script is a set of automation instructions written for testing tools.</p>
</li>
<li><p><strong>What is the Defect Life Cycle (Bug Life Cycle)?</strong></p>
<p>The defect life cycle includes the following stages:</p>
<ul>
<li>New → Assigned → Open → Fixed → Retested → Verified → Closed</li>
</ul>
</li>
<li><p><strong>What are different types of defects?</strong></p>
<ul>
<li><p>Functional Defects</p>
</li>
<li><p>Performance Defects</p>
</li>
<li><p>Security Defects</p>
</li>
<li><p>Compatibility Defects</p>
</li>
<li><p>UI Defects</p>
</li>
</ul>
</li>
<li><p><strong>How do you report a bug?</strong></p>
<p>A bug should be reported with:</p>
<ul>
<li><p>Summary</p>
</li>
<li><p>Steps to reproduce</p>
</li>
<li><p>Expected vs actual results</p>
</li>
<li><p>Screenshots/logs</p>
</li>
<li><p>Priority and severity</p>
</li>
</ul>
</li>
<li><p><strong>How would you test a login page manually?</strong></p>
<ul>
<li><p>Check login with valid and invalid credentials</p>
</li>
<li><p>Verify "Forgot Password" functionality</p>
</li>
<li><p>Check UI elements such as buttons and fields</p>
</li>
<li><p>Test session timeout and security aspects</p>
</li>
</ul>
</li>
</ol>
<ol start="15">
<li><p><strong>What is Regression Testing?</strong><br />Regression testing ensures that recent code changes do not break existing functionalities.</p>
</li>
<li><p><strong>What is the difference between Smoke and Sanity Testing?</strong></p>
<ul>
<li><p>Smoke Testing checks major functionalities of the application to ensure basic stability.</p>
</li>
<li><p>Sanity Testing verifies specific bug fixes or new features to confirm they work as expected.</p>
</li>
</ul>
</li>
</ol>
<ol start="17">
<li><p><strong>What are Severity and Priority in Bug Tracking?</strong></p>
<ul>
<li><p>Severity refers to the impact of the bug on the system (Critical, High, Medium, Low).</p>
</li>
<li><p>Priority refers to the urgency of fixing the bug (High, Medium, Low).</p>
<p>  <strong>Example:</strong></p>
</li>
<li><p>High Severity, Low Priority: A crash in an admin-only feature.</p>
</li>
<li><p>Low Severity, High Priority: A spelling mistake on the homepage title.</p>
</li>
</ul>
</li>
</ol>
<ol start="18">
<li><p><strong>What is Exploratory Testing?</strong><br />Exploratory testing is performed without predefined test cases, allowing testers to explore the application and find unexpected defects.</p>
</li>
<li><p><strong>How would you test an e-commerce website?</strong></p>
<ul>
<li><p>Verify user login and signup functionality</p>
</li>
<li><p>Test product search and filtering</p>
</li>
<li><p>Check the checkout and payment process</p>
</li>
<li><p>Validate order tracking and cancellation</p>
</li>
<li><p>Perform UI and security testing</p>
</li>
</ul>
</li>
</ol>
<ol start="21">
<li><p><strong>How do you handle a situation where a developer does not accept a reported defect?</strong></p>
<ul>
<li><p>Reproduce the bug and provide clear evidence (screenshots, logs)</p>
</li>
<li><p>Explain the impact of the defect</p>
</li>
<li><p>Discuss with the test lead or business analyst if required</p>
</li>
</ul>
</li>
</ol>
<ol start="22">
<li><p><strong>What would you do if you find a critical bug just before release?</strong></p>
<ul>
<li><p>Immediately report it to the test lead and stakeholders</p>
</li>
<li><p>Assess the impact and severity</p>
</li>
<li><p>Suggest a fix or a workaround</p>
</li>
<li><p>Document the risk if the fix is postponed</p>
</li>
</ul>
</li>
</ol>
<ol start="23">
<li><p><strong>How do you perform cross-browser testing manually?</strong></p>
<ul>
<li><p>Open the application in different browsers (Chrome, Firefox, Edge, Safari)</p>
</li>
<li><p>Check UI consistency and responsiveness</p>
</li>
<li><p>Validate functionality in each browser</p>
</li>
</ul>
</li>
</ol>
<ol start="24">
<li><p><strong>What is Compatibility Testing?</strong><br />Compatibility testing ensures that the software works across different devices, browsers, operating systems, and network environments.</p>
</li>
<li><p><strong>What are the key qualities of a good software tester?</strong></p>
<ul>
<li><p>Analytical skills</p>
</li>
<li><p>Attention to detail</p>
</li>
<li><p>Communication skills</p>
</li>
<li><p>Curiosity and exploratory mindset</p>
</li>
<li><p>Problem-solving ability</p>
</li>
</ul>
</li>
</ol>
<ol start="26">
<li><p><strong>What is Risk-Based Testing?</strong><br />Risk-based testing prioritizes test cases based on the likelihood and impact of failure.</p>
</li>
<li><p><strong>What is the difference between Static Testing and Dynamic Testing?</strong></p>
<ul>
<li><p>Static Testing involves reviewing documents, code, and requirements without execution.</p>
</li>
<li><p>Dynamic Testing involves executing the software to identify defects.</p>
</li>
</ul>
</li>
</ol>
<ol start="28">
<li><strong>What is Boundary Value Analysis (BVA)?</strong><br />BVA is a test design technique where test cases are created for boundary values of input fields.</li>
</ol>
<p><strong>Example:</strong><br />If an input field accepts values from 1 to 100, test cases should include 0, 1, 100, and 101.</p>
<ol start="29">
<li><p><strong>What is Equivalence Partitioning?</strong><br />Equivalence Partitioning is a technique where input data is divided into valid and invalid partitions, and test cases are created for each partition.</p>
</li>
<li><p><strong>What is Use Case Testing?</strong><br />Use case testing validates the application from an end-user perspective by testing real-world scenarios.</p>
</li>
</ol>
]]></content:encoded></item></channel></rss>