DEV Community: Vidhusha A

Task15

Vidhusha A — Sun, 28 Jan 2024 05:26:33 +0000

Difference between Selenium Webdriver, Grid and IDE?
Selenium WebDriver
Its object-oriented API is very useful when more dynamic elements that need to be tested. With Selenium WebDriver, developers and testers are able to target exact elements on the page, to increase both the speed and accuracy of the testing.
Broad language support - Allowing your team to use the language they know best, without additional training needed.
Multi-browser compatibility - Allowing for testing on multiple browsers to accommodate all possible users, as well as different user systems.
Open-source - This means you have vast stores of knowledge and tools that have built up over the years to solve any and all problems.
Community support - Giving you the support you need when you encounter problems, have questions, or need additional tools and innovations for your tests.
Easy implementation - Selenium is easy to install and set up, so you can implement and start using it quickly.
Compatible with a multitude of frameworks and other testing systems - You can plug in features you want into the framework you are already using.
Selenium IDE

Acts as a plug-in for your browser
Has point and click accessibility.
Provides the ability to build out tests into a grid for parallel test execution.
Provides the ability to execute testing remotely. This provides a significant advantage when testing multiple setups for the same test cases.
Able to record user behavior and play it back for reviewing and QA purposes.
You can record interactions within the application as test steps.
The application will test multiple locators before failing a test. The test can take longer, but it does work. Selenium Grid Selenium Grid is a smart proxy server that makes it easy to run tests in parallel on multiple machines. This is done by routing commands to remote web browser instances, where one server acts as the hub. This hub routes test commands that are in JSON format to multiple registered Grid nodes. The two major components of the Selenium Grid architecture are: Hub is a server that accepts the access requests from the WebDriver client, routing the JSON test commands to the remote drives on nodes. It takes instructions from the client and executes them remotely on the various nodes in parallel Node is a remote device that consists of a native OS and a remote WebDriver. It receives requests from the hub in the form of JSON test commands and executes them using WebDriver.

Qn2: Write a selenium script in java to open google and search selenium browser Driver.
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
public class Program1 {

public static void main(String args[])
{
    WebDriver driver = new ChromeDriver();
     driver.manage().window().maximize();
     driver.get("https://www.google.com/");
     WebElement ele= driver.findElement(By.xpath("//textarea[@id='APjFqb']"));

ele.sendKeys("Selenium browser Driver ");
ele.sendKeys(Keys.ENTER);
}
}

Qn:3 What is Selenium? How it is useful in automation testing?
Selenium is an open-source suite of tools and libraries that is used for browser automation.
It provides a single interface that lets you write test scripts in programming languages like Ruby, Java, NodeJS, PHP, Perl, Python, JavaScript, and C#, among others. Selenium is very extensible and can be integrated with other tools and frameworks like TestNG, JUnit, Cucumber, etc.
Importance of Testing in Selenium
Manual testing can be time-consuming and prone to human errors. Selenium Automation allows tests to be executed quickly and accurately, reducing the human mistakes and ensuring consistent test results.
Selenium allows developers and testers to automate the testing of web applications across different browsers and platforms.
Language Support : Selenium allows you to create test scripts in different languages like Ruby, Java, PHP, Perl, Python, JavaScript, and C#, among others.
Browser Support : Selenium enables you to test your website on different browsers such as Google Chrome, Mozilla Firefox, Microsoft Edge, Safari, Internet Explorer (IE), etc.
Scalability : Automated testing with Selenium can easily scale to cover a wide range of test cases, scenarios, and user interactions. This scalability ensures maximum test coverage of the application’s functionality.
Reusable Test Scripts : Selenium allows testers to create reusable test scripts that can be used across different test cases and projects. This reusability saves time and effort in test script creation and maintenance.
Parallel Testing : Selenium supports parallel test execution, allowing multiple tests to run concurrently. This helps reduce the overall testing time, making the development process more efficient.
Documentation and Reporting : Selenium provides detailed test execution logs and reports, making it easier to track test results and identify areas that require attention.
User Experience Testing : Selenium can simulate user interactions and behavior, allowing testers to assess the user experience and ensure that the application is intuitive and user-friendly.
Continuous Integration and Continuous Deployment (CI/CD) : Selenium can be integrated into CI/CD pipelines to automate the testing of each code change. This integration helps identify and address issues earlier in the development cycle, allowing for faster and more reliable releases.

Qn 4: What are all the browser drivers used in Selenium?
Selenium has provided support for different browsers and in order to support the browsers selenium webdrivers are required. Below are the browser drivers that extends Remote WebDriver.

Chromedriver : This is used to drive chrome browser.
Internet Explorer Driver: This is used to drive IE browsers
Geckodriver: To drive firefox browser
EdgeDriver: This is used to drive Edge browsers
OperaDriver: To handle Opera browsers
SafariDriver: To handle Safari browsers

Qn5: What are the steps to create the simple webdriver script .Expalin code.

https://github.com/VidhushaArumugam/Guvi1/blob/master/src/main/java/Task15.java

Manual and Automation testing, Automation testing tools,BDD vsTDD,Cross browser testing.

Vidhusha A — Sun, 28 Jan 2024 04:20:06 +0000

** Qn 1: Difference between manual and automation testing in Software development.**
The difference between manual testing and automated testing is that in manual testing, you perform the tests step by step without the help of tools, whereas in automated testing, tests are executed automatically using automation tools & frameworks.
Time-saving : Manual testing is repetitive and time-consuming, slowing the entire software development lifecycle. Automation testing saves considerable time by automating all the repetitive tasks and boosts the software development life cycle.
Less Manual Tasks : In automation testing, you can write the test cases once and use them over and over again. Some good automation tools also enable the generation of a detailed bug report for the failed case, making automation even more precise and powerful. In manual testing tasks are repetitively done manually.
Cost-effective : A dedicated testing team will be required to perform manual testing on industry-grade software. But in automation testing, the whole testing workflow can be automated with a minor team or even by a single person.
Team collaboration : When it comes to performing complex testing, team collaboration plays an important role, manual testing makes it considerably difficult, but in automated testing, you can easily add team members to review the test cases or contribute.
Easy to manage : Automation testing is relatively easy to manage than manual testing. In automation testing, the whole testing workflow can be automated and handled using a single graphical user interface.
But automation testing can’t replace manual testing. We need both manual and automation testing. Manual testing is helpful for complex test cases, whereas automated testing is preferred for simple and repetitive tests. Test automation is to help the testers to execute testing faster and more reliably. But it won’t replace humans.

Qn 2: Explore some most common automation tools in the market.
Selenium
Selenium is one of the most popular open-source frameworks for web testing automation. Its suite of software consists of Selenium WebDriver, Selenium Grid, and Selenium IDE.
Feature highlights:
• Supported programming languages: Java, C#, Python, JavaScript, Ruby, PHP, etc.
• Supported browsers: Chrome, Firefox, IE, Microsoft Edge, Opera, Safari, etc.
• Testing on local or remote machines via the Selenium server
• Parallel and cross-browser executions to reduce execution time and increase test coverage
• Integrations with other testing frameworks (e.g., TestNG for reporting) and CI/CD tools
The Katalon Platform
The Katalon Platform is a low-code and scalable automation testing tool for web, API, desktop (Windows), and mobile applications. Without having to code or built a test automation framework from scratch, users can simply download the tool and focus solely on testing.
Feature highlights:
• Flexible methods for test design: record & playback, manual, and scripting mode
• Supported testing methodologies: BDD, DDT, keyword-driven testing, cross-browser testing (Headless, Chrome, Edge, Firefox, and Safari), and cross-platform mobile testing (iOS, Android). Read more on how to do data-driven testing with Katalon here.
• Automatic retry failed tests, smart wait, and self-healing mechanisms.
• Reusable test objects, keywords, and test cases with test artifact sharing and page object model design
• Native integrations with popular CI/CD and ALMs tools (Jira, GitLab, Jenkins, Bitbucket, Azure DevOps, etc.)
Appium
Like Selenium, Appium is also an open-source automation testing tool, but for mobile applications. Using mobile JSON wire protocol, Appium allows users to write automated UI tests for native, web-based, and hybrid mobile applications on both Android and iOS.
• Supported programming languages: Java, C#, Python, JavaScript, Ruby, PHP, Perl
TestComplete
TestComplete can automate functional UI testing for desktop, mobile, and web applications. With built-in support for 500+ controls and third-party frameworks, TestComplete can handle and identify dynamic UI elements in most available technologies.
• Supported programming languages: JavaScript, Python, VBScript, JScript, Delphi, C++, C#
• Flexible methods for test design: record & playback, manual and scripting modes with built-in keywords
• Object identification with property-based and AI visual recognition
Cypress
Cypress is a developer-centric automation tool for end-to-end web testing. Built upon a new architecture, Cypress can directly operate within a browser in the same run-loop as your application, enabling native access to elements and faster executions.
Feature highlights:
Supported programming language: JavaScript
Postman
Postman is one of the most widely used automation testing tools for API. It allows users to write different kinds of tests, from functional and integration to regression tests, and execute them automatically in CI/CD pipelines via the command line.
Feature highlights:
Support for multiple HTML methods, Swagger, and RAML formats
Broad support for API schemas to generate collections and API elements
SoapUI
This open-source API testing tool is designed for REST and SOAP web services. Some vital features include automated functional, performance, regression, and security testing. Users can also aim for the commercial version, ReadyAPI (formerly SoapUI Pro), for more advanced capabilities.
Drag and drop to create tests, even with complex scenarios
More protocol support, capabilities, and CI/CD integration with ReadyAPI
Apache JMeter
This open-source tool is designed for automated performance testing, primarily for web applications. It can stimulate a heavy load of users to access web services and analyze the AUT’s performance. JMeter can also be used for functional API testing.
Applitools
Applitools stands out as an automated visual testing tool, revolutionizing the landscape of web and mobile application testing. The inclusion of visual testing is essential for identifying UI bugs on your web page, and Applitools excels in this regard.
Perfecto
Perfecto is a cloud-based and automated testing platform for web and mobile applications. From automated cross-environment executions, custom capabilities, test analysis, and broad integrations, Perfecto makes continuous testing more achievable for DevOps teams.
Feature highlights:
Scriptless test creation for UI web applications
LambdaTest
LambdaTest provides automated testing on the cloud. Its cloud service allows teams to scale up their test coverage with speedy parallel, cross-browser, and cross-device testing.

Qn 3: What is Cross Browser Testing?
Cross Browser testing is a type of non-functional testing that lets you check whether your website works as intended when accessed through:
Different Browser-OS combinations i.e., on popular browsers like Firefox, Chrome, Edge, Safari—on any of the popular operating systems like Windows, macOS, iOS and Android.
Different devices i.e., users can view and interact with your website on popular devices—smartphones, tablets, desktops and laptops etc.
Below are the steps how the cross browser testing is usually done
• Identify which features you’ll test and write steps to specify the scenarios.
• Identify the browsers and platforms—either by popularity or site traffic analysis—that you’ll test on.
• Pick how you’ll execute the test scenarios—manually or automatically.
• Set up devices/browsers you’ll test on (or connect with a cloud-based provider).
• Execute test scenarios on browsers with the highest share of traffic, then move on to outliers.
• Document and share the test results with teams who can debug/fix issues.
• Continuously run cross browser compatibility tests to ensure that no bugs were missed.

Qn4: What is BDD and TDD?
TDD (Test Driven Development) and BDD (Behavior Driven Development) are development approaches that both emphasize testing and collaboration, yet have major differences in focus and methodology. In TDD, developers test first, then use the test results to guide their development, while in BDD, developers express the system behavior they want to create through Gherkin syntax, then code according to those Gherkin expressions.

TDD is more developer-centric, revolving around code correctness, with programming language-specific frameworks.
• Create Tests
• Execute 1 Specific Test
• Implement The Code
• Run All Tests And Refactor The Code

On the other hand, BDD is more user-centric, revolves around system behavior, and promotes collaboration between relevant stakeholders with a domain-specific language.
• Write Scenarios Using Gherkin
• Apply TDD

1.Write test cases for Book my Show app 2.Write key points for Test Scenario, Case, Test Strategy, Plan, Test Summary Report.

Vidhusha A — Sat, 23 Dec 2023 05:56:20 +0000

1. Write as many test scenarios and test cases for Book my Show app

Uploaded the test cases in JIRA (Attached screenshot below)

Google doc link: https://docs.google.com/document/d/1TvcF2tUJIXYha_pgH7bneMzwtGSyNzHW8kkA8RASFLM/edit

2. Write key points about Test Scenario, Test Case, Test Strategy and Plan, Test Summary Report.
A test scenario is a collective set of test cases that helps the testing team to determine the positive and negative features of the project.
Purpose of Test Scenario:
Verify complete functionality: Test scenarios help to verify the complete functionality of the software application under test.
The business process according to functional requirements: Test scenarios help to ensure that the business flows and processes are as per the functional requirements of the application.
Organize workforce: Test scenarios help to determine testing work effort, and create a proposal for the client, thus helping to organize the workforce.
Test cases contain definite test steps, data, and expected outcomes for testing all the features of the software under test.
Test cases are the set of actions to execute and test particular feature of the application on the other hand test scenarios is any functionality that can be tested.
Test cases are derived from test scenarios whereas test scenarios are derived from SRS, BRS, etc.
Test cases help in the exhaustive testing of the application and test scenarios help in the agile way of testing the application.
Test cases are focussed on how to test and what to test on the other hand test scenarios are focussed on what to test.
Test cases require more time and resources as compared to test scenarios.
Test cases are low-level actions and test scenarios are high-level actions.
Test Plan:
The test plan is created for specific projects, and considers goals, stakeholders, and risks. In Agile development, a master plan for the project can be made, with specific sub-plans for each iteration. During the planning phase, QA engineers only need to define test points. A test plan records the types of testing undertaken and may be reused in case regression testing is performed at a later stage. The following are the critical uses of test plans:
• Guide to testing process.
• Bridge between teams.
• Streamlined functional coverage.
• Ensures availability of resources.
• Prevents testing ‘out of scope’.
• Keeps a record of testing.
• Tracks the testing progress.
• Ensures risk management.

Test Strategy :
Test strategy is a high-level plan consisting of principles that guide the overall software testing process. It provides a structured approach to the entire QA team, guiding them toward achieving testing objectives in the most efficient way.
Guides the testing effort by providing focus, clarity, and effective risk management.
Ensures efficiency, effectiveness, and adherence to standards in testing practices.
Promotes better collaboration between members of the QA team.
Ensures that all members are aligned on the overall vision of the project.
Acts as reference for resource planning and allocation for optimal utilization.
Allows you to track progress more efficiently.
Test Summary Report :
A QA test summary report provides details of any important information uncovered during any phase of testing.
The summary report includes assessments of the quality of the testing effort, the quality of the software system under test, and statistics derived from incident reports.
It also allows project stakeholders to review testing efforts with respect to the test plan ensuring transparency and accountability throughout the organization. A typical test summary report template generally contains:
• A summary of test activities and final test results.
• An assessment of how well the testing is performed.

Task 1 - Manual Testing

Vidhusha A — Sat, 09 Dec 2023 05:56:32 +0000

QN1 : What are the different types of Testing?
The Software testing is broadly classified into Manual Testing and Automation Testing.
Manual Testing: Testing any software or an application according to the client's needs without using any automation tool is known as manual testing.
Automation Testing: Automation Testing is a software testing technique that is performed using special automated testing software tools to execute a test case suite.
Manual testing is further classified into many subcategories which are explained as below:
• White Box Testing
• Black Box Testing
• Grey Box Testing
White Box testing : In white-box testing, the developer will inspect every line of code before handing it over to the testing team or the concerned test engineers. The purpose of implementing the white box testing is to emphasize the flow of inputs and outputs over the software and enhance the security of an application.
White box testing is also known as open box testing, glass box testing, structural testing, clear box testing, and transparent box testing.
Black Box testing : In this testing, the test engineer will analyse the software against requirements, identify the defects or bug, and sends it back to the development team. The main objective of implementing the black box testing is to specify the business needs or the customer's requirements.
Black box testing is a process of checking the functionality of an application as per the customer requirement. The source code is not visible in this testing; that's why it is known as black-box testing.
Black Box testing is classified into Functional testing and Non-functional testing.
Functional Testing : In functional testing, all the components are tested by giving the value, defining the output, and validating the actual output with the expected value.
Functional testing is a part of black-box testing as its emphases on application requirement rather than actual code. Functional testing is also known as Component testing.
Functional testing is further classified into the following:
1) Unit Testing - With this functional testing type, smallest functional and testable unit of code is tested during unit testing. Mostly, performed by developers, since it is a White-Box testing technique.
2) Integration Testing - Two or more unit tested components of the software are integrated together, and tested to validate the interaction between them is as expected. The communication of commands, data, DB calls, API calls, Micro-services processing is happening between the units and there is no unexpected behaviour observed during this integration. It has 3 approaches called Top-Down Approach, Bottom-Up Approach and Hybrid Approach.
3) System Testing - All components of the system are combined and the system is tested for compliance and correctness against the requirement specifications (Functional or System).
4) Regression Testing - After some enhancements or code fixes by developers, it becomes very important to run the regression test suite. Regression is run to ensure that these code changes have not hampered the existing working functionalities or any new defect is not injected in the code.
5) Smoke Testing - After development, when a new build is released, Smoke Testing is performed on the application to ensure that all end-to-end major functionalities work. Smoke testing is usually done for the builds created during the initial phase of development for an application, which are not yet stable.
6) Sanity Testing - Sanity Tests are selected from the Regression Test suite, covering major functionalities of the application.
7) Acceptance Testing - During Acceptance Testing, the acceptance of the application by the end-user is tested. It is performed just after the System Testing and before the final release of the application in the real world.
Non-functional Testing : It provides detailed information on software product performance and used technologies.
Non-functional testing will help us minimize the risk of production and related costs of the software.
It is classified into:
• Load Testing
• Stress Testing
• Scalability Testing
• Stability Testing
Grey Box testing : Another part of manual testing is Grey box testing. It is a collaboration of black box and white box testing.
Since, the grey box testing includes access to internal coding for designing test cases. Grey box testing is performed by a person who knows coding as well as testing

QN2: What are the different STLC phases?
The Software Testing Life Cycle (STLC) is a systematic approach to testing a software application to ensure that it meets the requirements and is free of defects. It is a process that follows a series of steps or phases, and each phase has specific objectives and deliverables. The STLC is used to ensure that the software is of high quality, reliable, and meets the needs of the end-users.

Phases of STLC
Requirement Analysis : In this phase quality assurance team understands the requirements like what is to be tested.

Creating a requirement traceability matrix (RTM) to map requirements to test cases

Test Planning : Test Planning is the phase where all testing plans are defined. In this phase, team lead and team calculate the estimated effort and cost for the testing work.

Test Case Development : In this phase testing team notes down the detailed test cases. The testing team also prepares the required test data for the testing.

Test Environment Setup : The test environment decides the conditions on which software is tested. In this process, the testing team is not involved. either the developer or the customer creates the testing environment.

Test Execution : After the test case development and test environment setup test execution phase gets started. In this phase testing team starts executing test cases based on prepared test cases in the earlier step.
The activities that take place during the test execution stage of the Software Testing Life Cycle (STLC) include:
• Test execution
• Defect logging
• Test data preparation
• Test environment setup
• Test execution
• Test result analysis
• Defect retesting
• Test Reporting

Test Closure : Test closure is the final stage where all testing-related activities are completed and documented. The main objective of the test closure stage is to ensure that all testing-related activities have been completed and that the software is ready for release.
The main activities in test closure stage include:
• Test summary report
• Defect tracking
• Test environment clean-up
• Test closure report
• Knowledge transfer
• Feedback and improvements

QN3:As a manual tester, what qualities are you required to possess?

Attention to detail, curiosity, creativity, strong analytical and problem-solving skills, communication and collaboration skills, patience and persistence, and a passion for quality is the important quality I feel a manual tester is required to posses. I believe I posses these qualities and by cultivating these qualities, testers can make a significant contribution to the success of the software development process and help to deliver high-quality products that meet customer needs and expectations.
The below technical skills are also a must to be a good manual tester and I strongly believe in improving these skills as per the market demand.
• Experience in project management and QA approaches
• Familiarity with agile frameworks
• Working knowledge of testing tools, programming languages
• Error documentation and debugging
• Test management software experience

Apart from these, I also do believe that I have a good soft-skills as mentioned below that helps me to communicate and execute my thought process to deliver a high quality product.
• Written and oral communication skills
• Attention to detail
• Team working and critical thinking
• Professionalism with a team focus
• Interpersonal skills

The QA tester responsibilities includes the following activities and I am good at the below mentioned skills/responsibilities.
• Define testing objectives and the methodology to fulfill them
• Review, analyze system specifications, and test procedures
• Early testing of applications for early identification of errors
• See to it that the test strategy is aligned with the development requirements
• Report errors, document logs, and solve technical problems with the development team through bug tracking tools like Bugzilla, etc.
• Root cause analysis of errors and defects
• Executing debugging programs for fixation of defects and bugs
• Design and execute test scripts, and test cases, and evaluate results for manual and automated tests

QN4:What is the difference between Waterfall and Agile methodologies in SDLC?

Agile and Waterfall are two well-known project management methodologies. Both of them are popular in software development but each is best suited for different types of projects. The main difference is that Waterfall is a linear system of working that requires the team to complete each project phase before moving on to the next one while Agile encourages the team to work simultaneously on different phases of the project.
Agile Methodology
• Approach: Frequent stakeholder interaction
• Flexibility: High
• Requires: Team initiative and short-term deadlines
Agile methodology was developed as a response to Waterfall’s more rigid structure. As a result, it’s a much more fluid form of project management. A software development project can take years to complete, and technology can change significantly during that time. Agile was developed as a flexible method that welcomes incorporating changes of direction even late in the process, as well as accounting for stakeholders’ feedback throughout the process.
In Agile, the team will work on phases of the project concurrently, often with short-term deadlines. Additionally, the team, rather than a project manager, drives the project’s direction. This can empower the team to be motivated and more productive, but also requires a more self-directed team.
Waterfall Methodology
• Approach: Hands-off; goals and outcome established from the beginning
• Flexibility: Low
• Requires: Completing deliverables to progress to the next phase
Waterfall methodology is a linear form of project management ideal for projects where the end result is clearly established from the beginning of the project. The expectations for the project and the deliverables of each stage are clear and are required in order to progress to the next phase.

Task 1 - Manual Testing

Vidhusha A — Sat, 09 Dec 2023 05:54:36 +0000

Test Planning : Test Planning is the phase where all testing plans are defined. In this phase, team lead and team calculate the estimated effort and cost for the testing work.

Test Case Development : In this phase testing team notes down the detailed test cases. The testing team also prepares the required test data for the testing.

QN3:As a manual tester, what qualities are you required to possess?

QN4:What is the difference between Waterfall and Agile methodologies in SDLC?

Agile and Waterfall are two well-known project management methodologies. Both of them are popular in software development but each is best suited for different types of projects. The main difference is that Waterfall is a linear system of working that requires the team to complete each project phase before moving on to the next one while Agile encourages the team to work simultaneously on different phases of the project.
Agile Methodology
• Approach: Frequent stakeholder interaction
• Flexibility: High
• Requires: Team initiative and short-term deadlines
Agile methodology was developed as a response to Waterfall’s more rigid structure. As a result, it’s a much more fluid form of project management. A software development project can take years to complete, and technology can change significantly during that time. Agile was developed as a flexible method that welcomes incorporating changes of direction even late in the process, as well as accounting for stakeholders’ feedback throughout the process.
In Agile, the team will work on phases of the project concurrently, often with short-term deadlines. Additionally, the team, rather than a project manager, drives the project’s direction. This can empower the team to be motivated and more productive, but also requires a more self-directed team.
Waterfall Methodology
• Approach: Hands-off; goals and outcome established from the beginning
• Flexibility: Low
• Requires: Completing deliverables to progress to the next phase
Waterfall methodology is a linear form of project management ideal for projects where the end result is clearly established from the beginning of the project. The expectations for the project and the deliverables of each stage are clear and are required in order to progress to the next phase.

Write key points about Test Scenario, Test Case, Test Strategy and Plan, Test Summary Report.

Vidhusha A — Sun, 03 Dec 2023 19:07:18 +0000

A test scenario is a collective set of test cases that helps the testing team to determine the positive and negative features of the project.
Purpose of Test Scenario :
Verify complete functionality : Test scenarios help to verify the complete functionality of the software application under test.
The business process according to functional requirements : Test scenarios help to ensure that the business flows and processes are as per the functional requirements of the application.
Organize workforce : Test scenarios help to determine testing work effort, and create a proposal for the client, thus helping to organize the workforce.
Test cases contain definite test steps, data, and expected outcomes for testing all the features of the software under test.
Test cases are the set of actions to execute and test particular feature of the application on the other hand test scenarios is any functionality that can be tested.
Test cases are derived from test scenarios whereas test scenarios are derived from SRS, BRS, etc.
Test cases help in the exhaustive testing of the application and test scenarios help in the agile way of testing the application.
Test cases are focussed on how to test and what to test on the other hand test scenarios are focussed on what to test.
Test cases require more time and resources as compared to test scenarios.
Test cases are low-level actions and test scenarios are high-level actions.
Test Plan :
The test plan is created for specific projects, and considers goals, stakeholders, and risks. In Agile development, a master plan for the project can be made, with specific sub-plans for each iteration. During the planning phase, QA engineers only need to define test points. A test plan records the types of testing undertaken and may be reused in case regression testing is performed at a later stage. The following are the critical uses of test plans:
• Guide to testing process.
• Bridge between teams.
• Streamlined functional coverage.
• Ensures availability of resources.
• Prevents testing ‘out of scope’.
• Keeps a record of testing.
• Tracks the testing progress.
• Ensures risk management.

Test Strategy :
Test strategy is a high-level plan consisting of principles that guide the overall software testing process. It provides a structured approach to the entire QA team, guiding them toward achieving testing objectives in the most efficient way.
Guides the testing effort by providing focus, clarity, and effective risk management.
Ensures efficiency, effectiveness, and adherence to standards in testing practices.
Promotes better collaboration between members of the QA team.
Ensures that all members are aligned on the overall vision of the project.
Acts as reference for resource planning and allocation for optimal utilization.
Allows you to track progress more efficiently.
Test Summary Report:
A QA test summary report provides details of any important information uncovered during any phase of testing.
The summary report includes assessments of the quality of the testing effort, the quality of the software system under test, and statistics derived from incident reports.
It also allows project stakeholders to review testing efforts with respect to the test plan ensuring transparency and accountability throughout the organization. A typical test summary report template generally contains:
• A summary of test activities and final test results.
• An assessment of how well the testing is performed.

Explain about Epic and User Stories

Vidhusha A — Sun, 03 Dec 2023 10:49:13 +0000

Epic :
An agile epic is a body of work that can be broken down into specific tasks (called user stories) based on the needs/requests of customers or end-users. Epics are an important practice for agile and DevOps teams.
When adopting agile and DevOps, an epic serves to manage tasks. It's a defined body of work that is segmented into specific tasks (called “stories,” or “user stories”) based on the needs/requests of customers or end-users.
Epics are a helpful way to organize your work and to create a hierarchy. Epics help teams break their work down, while continuing to work towards a bigger goal.
User Story :
A user story is an informal, general explanation of a software feature written from the perspective of the end user. Its purpose is to articulate how a software feature will provide value to the customer.
A user story is the smallest unit of work in an agile framework. It’s an end goal, not a feature, expressed from the software user’s perspective.
The purpose of a user story is to articulate how a piece of work will deliver a particular value back to the customer. User stories are a few sentences in simple language that outline the desired outcome. User stories are also the building blocks of larger agile frameworks like epics and initiatives. Epics are large work items broken down into a set of stories. Generally, a story is written by the product owner, product manager, or program manager and submitted for review.

Explain about Agile Methodology

Vidhusha A — Sun, 03 Dec 2023 10:42:57 +0000

Agile methodology is a project management approach that prioritizes cross-functional collaboration and continuous improvement. It divides projects into smaller phases and guides teams through cycles of planning, execution, and evaluation.
Agile’s four main values are:
• Individuals and interactions over processes and tools.
• Working software over comprehensive documentation.
• Customer collaboration over contract negotiation.
• Responding to change over following a plan.
Many teams embrace the Agile approach for the following reasons:
Rapid progress : By effectively reducing the time it takes to complete various stages of a project, teams can elicit feedback in real time and produce working prototypes or demos throughout the process.
Customer and stakeholder alignment : Through focusing on customer concerns and stakeholder feedback, the Agile team is well positioned to produce results that satisfy the right people
Continuous improvement : As an iterative approach, Agile project management allows teams to chip away at tasks until they reach the best result.
Types of Agile methodologies
Agile project management is not a singular framework but an umbrella term that includes a wide range of methodologies, including Scrum, Kanban, Extreme Programming (XP), and the Adaptive Project Framework (APF).
• Scrum : It is ideal for projects with rapidly changing requirements, using short sprints.
• Kanban : It visualizes project progress and is great for tasks requiring steady output.
• Lean : It streamlines processes, eliminating waste for customer value.
• Extreme Programming (XP) : It enhances software quality and responsiveness to customer satisfaction.
• Adaptive Project Framework (APF) : Works well for projects with unclear details, as it adapts to constantly evolving client needs.

Describe the difference between a. Smoke and Sanity Testing b. Validation and Verification

Vidhusha A — Sun, 03 Dec 2023 10:35:52 +0000

Smoke and Sanity Testing:
The process to create an executable program uses “build” software and is called “Software Build”.

Sanity testing: Sanity Testing verifies the new functionality like bug fixes and is a is a subset of Regression Testing.
Sanity testing is performed to check if new module additions to an existing software build are working as expected and can pass to the next level of testing. It is a subset of regression testing and evaluates the quality of regressions made to the software. The main purpose of Sanity testing is to verify that the changes or the proposed functionality are working according to plan. Suppose there are minor changes to be made to the code, the sanity test further checks if the end-to-end testing of the build can be performed seamlessly.
Smoke Testing: Smoke Testing verifies the critical functionalities of the system and is a subset of acceptance testing.
Smoke Testing is carried out post software built in the early stages of SDLC (software development life cycle) to reveal failures, if any, in the pre-released version of a software. The testing ensures that all core functionalities of the program are working smoothly and cohesively. The intent of smoke testing is not exhaustive testing but to eliminate errors in the core of the software. It detects errors in the preliminary stage so that no futile efforts are made in the later phases of the SDLC.
Validation and Verification:
Verification in Software Testing is a process of checking documents, design, code, and program to check if the software has been built according to the requirements or not. The main goal of verification process is to ensure quality of software application, design, architecture etc. The verification process involves activities like reviews, walk-throughs, and inspection. It does not involve executing the code. It comes before validation.
Validation in Software Engineering is a dynamic mechanism of testing and validating if the software product meets the exact needs of the customer or not. The process helps to ensure that the software fulfills the desired use in an appropriate environment. The validation process involves activities like unit testing, integration testing, system testing and user acceptance testing. It always involves executing the code. It comes after verification.

What is the difference between manual and Automation testing?

Vidhusha A — Sun, 03 Dec 2023 10:16:07 +0000

In manual testing, a human performs the tests step by step, without test scripts. In automated testing, tests are executed automatically via test automation frameworks, along with other tools and software.
When manually testing, the tester validates the key features of a software application. Analysts execute test cases and develop summary error reports without specialized automation tools.
Automated testing helps testers execute more test cases and improve test coverage. When comparing manual vs. automation testing, manual takes longer. Automated testing is more efficient.
Both have their strengths and weaknesses. Manual testing is slow and tedious. But its strength is that it better handles complex scenarios. Automated testing requires coding and test maintenance. But on the plus side, it is much faster and covers many more permutations.
Manual:
• Done manually by QA testers.
• Time-consuming and less efficient.
• Entirely manual tasks.
• Difficult to ensure sufficient test coverage.
• less expensive as one does not need to spend a budget on automation tools and processes.
• Manual testing is flexible as it can adapt easily to changes in the user interface.
Automation:
• Done automatically using automation tools and scripts.
• More testing in less time and greater efficiency.
• Most tasks can be automated, including real user simulations.
• Easy to ensure greater test coverage.

What is the difference between QA and QC?

Vidhusha A — Sun, 03 Dec 2023 10:15:07 +0000

QA is process-oriented, and it focuses on preventing quality issues. QC is product-oriented and focused on identifying quality issues in manufactured products that could affect customer satisfaction. Another way to understand this distinction is actions vs. results.
QA Processes:
• Documentation
• Audits
• Supplier management
• Personnel training
• Change control
• Investigation procedures
QC Procedures:
• Batch inspection
• Product sampling
• Validation testing
• Laboratory testing
• Software testing

Many people think QA and QC are the same and interchangeable, but this is not true. Both are tightly linked and sometimes it is very difficult to identify the differences. Fact is both are related to each other, but they are different in origins. QA and QC both are part of Quality Management however QA is focusing on preventing defect while QC is focusing on identifying the defect.

What is the difference between QA and QC?

Vidhusha A — Sun, 03 Dec 2023 10:09:09 +0000

QA is process-oriented, and it focuses on preventing quality issues. QC is product-oriented and focused on identifying quality issues in manufactured products that could affect customer satisfaction. Another way to understand this distinction is actions vs. results.
QA Processes:
• Documentation
• Audits
• Supplier management
• Personnel training
• Change control
• Investigation procedures
QC Procedures:
• Batch inspection
• Product sampling
• Validation testing
• Laboratory testing
• Software testing