DEV Community: Hameed Hussain

Task 15

Hameed Hussain — Thu, 25 Apr 2024 09:16:47 +0000

QUE 1 : Explain difference between Selenium IDE, Selenium WebDriver and Selenium grid

Selenium IDE:

Selenium IDE is a record-and-playback tool primarily used for creating and executing Selenium tests without writing code.
It's a browser extension available for Chrome and Firefox, allowing users to record interactions with the browser and generate automated test scripts in various programming languages like Java, Python, Ruby and Selenese (Selenium’s own scripting language).
Selenium IDE is suitable for quick test case creation and prototyping but may lack the robustness and flexibility of WebDriver for complex testing scenarios.

Selenium WebDriver:

Selenium WebDriver is the most powerful component of the Selenium suite, providing a programming interface for creating and executing test scripts.
It allows testers to write code in programming languages like Java, Python, C#, etc., to interact with web elements and automate browser actions.
WebDriver directly communicates with the browser using its native automation support, providing more control and flexibility over browser interactions compared to Selenium IDE.
WebDriver supports various browsers such as Chrome, Firefox, Safari, Edge, etc., and enables testing across different operating systems.

Selenium Grid:

Selenium Grid is a tool used for parallel execution of Selenium tests across multiple machines and browsers simultaneously.
It consists of a hub and multiple nodes. The hub acts as a central point where test requests are sent, and nodes are remote machines (physical or virtual) where tests are executed.
Selenium Grid enables testers to distribute test execution, reducing the overall test execution time and increasing test coverage.

QUE 2 : Write a Selenium script in Java to open Google and search for "Selenium Browser Driver"

Below GITHUB link contains code and screenshot of program

https://github.com/Hameed1206/Task-15_and_16_SeleniumStarts/tree/main/src/test/java/MavenFirst/MavenProjectOne
Code file -> Task15Que2.java
Snap file -> Task 15 2ndQues.png

QUE 3 : What is Selenium and how it is useful in automation testing

Selenium is an open-source automation testing framework primarily used for automating web applications. It provides a suite of tools that facilitate the automation of web browsers for testing purposes. Selenium allows testers to automate interactions with web elements, such as clicking buttons, entering text, submitting forms, and verifying expected behavior

Here's how Selenium is useful in automation testing:

Cross-browser Testing: Selenium supports multiple web browsers such as Chrome, Firefox, Safari, Edge, and Opera. Test scripts written with Selenium can be executed across different browsers, ensuring that web applications function correctly regardless of the browser being used.

Cross-platform Testing: Selenium enables testing across various operating systems like Windows, macOS, and Linux. This ensures that web applications behave consistently across different platforms.

Automation of Repetitive Tasks: Selenium automates repetitive testing tasks, such as regression testing, where testers need to repeatedly validate the functionality of an application after code changes. By automating these tasks, testers can save time and effort, allowing them to focus on more complex testing scenarios.

Improved Test Coverage: Automated tests created with Selenium can cover a wide range of test scenarios, including positive and negative cases, edge cases, and user interactions. This helps in achieving comprehensive test coverage, identifying bugs early in the development cycle, and improving the overall quality of the software.

Integration with Continuous Integration (CI) Systems: Selenium can be integrated with CI systems like Jenkins, Bamboo, or Travis CI, enabling the execution of automated tests as part of the continuous integration and continuous deployment (CI/CD) pipeline. This ensures that new code changes are thoroughly tested before being deployed to production, reducing the risk of introducing bugs into the application.

Support for Multiple Programming Languages: Selenium WebDriver, the core component of Selenium, supports multiple programming languages such as Java, Python, C#, Ruby, and JavaScript. This allows testers to write test scripts in their preferred programming language, making it accessible to a wide range of users with different skill sets.

QUE 4 : What are all browser driver used in selenium

Selenium WebDriver supports various browser drivers, each corresponding to a specific web browser. Here are the commonly used browser drivers in Selenium

ChromeDriver
GeckoDriver (FirefoxDriver)
InternetExplorerDriver
EdgeDriver
SafariDriver
OperaDriver
ChromiumDriver

QUE 5 : What are the steps to create a simple WebDriver script. Explained with code.

STEP 1 ->
Import the necessary Selenium WebDriver classes and any other required libraries.

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;

STEP 2 ->
Setup WebDriver using WebDriverManager for chrome

WebDriverManager.chromedriver().setup();

STEP 3 ->
Initialize WebDriver instance

WebDriver driver = new ChromeDriver();

STEP 4 ->
Use the driver instance to navigate to a specific URL.

driver.get(""https://www.google.com/"");

STEP 5 ->
Perform Actions, Interact with the web elements on the page using various WebDriver methods like findElement(), sendKeys(), click(), etc.
Here I have found the web element of search text field using findElement method and by using sendKeys method I have entered value "Selenium Browser Driver" to it. Then I used keys.Enter function to perform enter option in keyboard

driver.findElement(By.name("q")).sendKeys("Selenium Browser Driver", Keys.ENTER);

STEP 6 ->
Close the WebDriver instance after the test execution is complete.

driver.quit();

TASK 14

Hameed Hussain — Wed, 17 Apr 2024 12:39:22 +0000

QUE 1 : what is difference between Automated and Manual testing in Software development

Manual Testing

Manual testing is testing of the software where tests are executed manually by a QA Analyst without the use of automation tools. It is performed to discover bugs in software under development.
In Manual testing, the tester checks all the essential features of the given application or software.
The tester executes test cases and generates test reports without any help from the automation tools.
It is conducted by the experienced tester to accomplish the testing process.
Manual testing allows testers to adapt quickly to changes in requirements or user interface designs, making it suitable for exploratory testing and ad-hoc scenarios.
Manual testing is essential for evaluating aspects of usability, user experience, and user interface design that cannot be easily automated.

Automation Testing

In Automated Software Testing, testers write code/test scripts to automate test execution. Testers use appropriate automation tools to develop the test scripts and validate the software. The goal is to complete test execution in a less amount of time.
It is faster than manual testing because it is done with some automation tools. There is no chance of any human errors.
Automated testing entirely relies on the pre-scripted test which runs automatically to compare actual result with the expected results. This helps the tester to determine whether or not an application performs as expected.
Automated testing allows you to execute repetitive task and regression test without the intervention of manual tester. Even though all processes are performed automatically, automation requires some manual effort to create initial testing scripts.

QUE 2 : Explore some of the most common automation testing tools available in market

Selenium WebDriver: (Web)

Selenium is one of the most widely used open-source automation testing frameworks for web applications.
Selenium WebDriver allows testers to write tests in various programming languages such as Java, Python, C#, etc.
It supports multiple browsers (Chrome, Firefox, Safari, Edge, etc.) and platforms (Windows, macOS, Linux).

Appium: (Mobile App)

Appium is an open-source automation tool for testing mobile applications.
It supports iOS, Android, and Windows platforms and allows tests to be written in various programming languages.
Appium provides cross-platform testing capabilities and integrates with popular test frameworks like JUnit, TestNG, etc.

Katalon Studio: (Web, MobileApp & API)

Katalon Studio is a comprehensive test automation solution for web, mobile, API, and desktop applications.
It offers a user-friendly interface with features for test recording, scripting, and test case management.
Katalon Studio supports multiple scripting languages (Groovy, Java) and integrates with various CI/CD tools.

Unified Functional Testing (UFT): (Web, Desktop, MobileApp & API)

Formerly known as HP QuickTest Professional (QTP), UFT is a commercial automation tool for functional testing of web, desktop, and mobile applications.
It supports multiple scripting languages (VBScript, JavaScript) and integrates with ALM (Application Lifecycle Management) tools.
UFT provides features for keyword-driven testing, object recognition, and automated test maintenance.

Cypress: (Web & API)

Cypress is an open-source end-to-end testing framework specifically designed for modern web applications.
It provides a fast, reliable, and deterministic testing experience with real-time feedback.
Cypress offers features like automatic waiting, time travel debugging, and built-in support for APIs and browser events.

Robot Framework: (Web, Desktop, MobileApp & API)

Robot Framework is an open-source automation framework that uses a keyword-driven approach and plain-text syntax.
It supports test automation for web, mobile, API, and desktop applications and integrates with various libraries and tools.
Robot Framework is highly extensible and supports multiple test data formats and reporting options.

Playwright (Web & API)

Playwright supports multiple web browsers, including Chromium (Google Chrome), Firefox, and WebKit (Safari). This allows for comprehensive cross-browser testing to ensure consistent behavior across different browsers.
Playwright offers bindings for multiple programming languages, including JavaScript, Python, and .NET (C#). This enables developers to write tests using their preferred programming language and ecosystem.
Playwright can run browser automation in headless mode, which means the browser UI is not displayed during test execution. Headless mode is useful for running tests in environments without a graphical user interface, such as CI/CD pipelines or remote servers.

Postman(API):

Postman is one of the most popular API testing tools, offering a user-friendly interface for designing, testing, and debugging APIs.
It supports various HTTP methods (GET, POST, PUT, DELETE, etc.) and allows users to create and organize collections of API requests.
Postman offers features such as environment variables, automated testing with scripts (using JavaScript), and team collaboration capabilities.

SoapUI:(API)

SoapUI is a widely used API testing tool for testing SOAP and RESTful web services.
It offers a comprehensive set of features for functional testing, load testing, and security testing of APIs.
SoapUI supports data-driven testing, assertion scripting, and integration with CI/CD pipelines for automated testing.

REST Assured: (API)

REST Assured is a popular Java library for testing RESTful APIs, commonly used in automated testing frameworks and tools.
It provides a fluent interface for writing test cases and assertions, making it easy to create readable and maintainable tests.
REST Assured integrates seamlessly with popular Java testing frameworks like JUnit and TestNG.

Apache JMeter: (Performance)

JMeter is one of the most widely used open-source performance testing tools.
It allows users to simulate various scenarios, including load testing, stress testing, and functional testing of web applications.
JMeter supports multiple protocols (HTTP, HTTPS, SOAP, JDBC, etc.) and offers features for distributed testing, dynamic parameterization, and result analysis.

LoadRunner: (Performance)

LoadRunner is a commercial performance testing tool developed by Micro Focus.
It provides a comprehensive set of features for load testing, stress testing, and performance monitoring of applications.
LoadRunner supports various protocols (HTTP, SOAP, JDBC, etc.) and offers integrations with CI/CD tools for automated testing.

QUE 3: what is cross browser testing

Cross-browser testing is the process of verifying that a web application functions correctly and consistently across different web browsers and browser versions. Since web browsers can interpret HTML, CSS, and JavaScript code differently, web applications may render and behave differently depending on the browser being used. Cross-browser testing ensures that users have a consistent and reliable experience regardless of the browser they choose to use.

The primary objective of cross-browser testing is to identify and address any discrepancies or issues in how a web application is displayed or functions across different browsers.
Verify that the layout, styling, and visual elements of the web application are consistent across browsers.
Ensure that all features, interactions, and behaviors of the web application work as expected across browsers.
Test the responsiveness and performance of the web application, including page load times and responsiveness to user interactions, across browsers.
Confirm that the web application is compatible with older versions of browsers, as well as newer versions and alternative browsers.

QUE 4: Write blog on TDD and BDD

Test Driven Development

Test Driven Development is a development technique which focuses more on the implementation of a feature of a software application/product.
Here, we create the test cases first and then write the code underlying those test cases. Although TDD is a development technique, it can also be used for automation testing development.
The teams that implement TDD, take more time for development however, they tend to find very few defects. TDD results in improved quality of code and the code that is more reusable and flexible.
TDD also helps in achieving high test coverage of about 90-100%. The most challenging thing for developers following TDD is to write their test cases before writing the code.

Benefits:

Unit test provides constant feedback about the functions.
Quality of design increases which further helps in proper maintenance.
Test driven development act as a safety net against the bugs.
TDD ensures that your application actually meets requirements defined for it.
TDD have very short development lifecycle.

Behavior Driven Development

BDD is a software development approach that extends TDD by focusing on the behavior of the software from the perspective of its stakeholders.
BDD emphasizes collaboration between technical and non-technical stakeholders to define and verify the behavior of the system through examples written in a common language.
BDD is considered a best practice when it comes to automated testing as it focuses on the behavior of the application and not on thinking about the implementation of the code.
The behavior of the application is the center of focus in BDD and it forces the developers and testers to walk-in the customer’s shoes.

Benefits:

Greater clarity on business goals and customer requirements.
Reaches a larger customer set as it uses non-technical languages.
Helps in defining acceptance criteria before development.
Focuses on the system’s behavior from the client’s and developer’s point of view.
Collaboration between team members is promoted through BDD, involving all stakeholders in the development process to ensure a shared understanding of objectives.
Detailed documentation of user stories, acceptance criteria, and step definitions can improve overall project documentation, facilitating maintenance and updates to the system.

Task 11

Hameed Hussain — Sun, 14 Apr 2024 10:41:50 +0000

QUE 1 : Access modifiers in java

Access modifiers in Java are keywords used for controlling the use of the methods, constructors, variables, and Classes.
There are four main types of access modifiers,

Public
Protected
Default
Private

PUBLIC

The public access modifier has the widest scope among all other access modifiers. Public access modifier allows members (classes, methods, and variables) to be accessed from any other class, Inside and Outside the package

A public class can be accessed from any other class, Inside and Outside the package
A public method can be accessed from any other class, Inside and Outside the package
A public variable can be accessed from any other class, Inside and Outside the package

PROTECTED

The protected access modifier is specified using the keyword protected. The protected access modifier allows members to be accessed within the same package or by subclasses in a different package.

A protected class is not allowed in Java.
A protected method can be accessed within the same package or by subclasses in a different package.
A protected variable can be accessed within the same package or by subclasses in a different package.

DEFAULT

When no access modifier is specified for a class, method, or data member – It is said to be having the default access modifier by default. The default (no modifier) access modifier allows members to be accessed within the same package only.

A class with default access modifier is only accessible within the same package.
A method with default access modifier is only accessible within the same package.
A variable with default access modifier is only accessible within the same package.

PRIVATE

The private access modifier is specified using the keyword private. The private access modifier restricts access to members to within the same class only.

A private class is not allowed in Java.
A private method can only be accessed within the same class.
A private variable can only be accessed within the same class.

================================================================================================================

QUE 2 Difference Between Exception and Error

Exception can be recovered by using try-catch block.
Error cannot be recovered by using try-catch block.

Exception is classified into two types:

Checked exceptions
Unchecked exceptions

Error is classified into two types:

Fatal errors
Non-fatal errors.

Exception occurs during the execution of a program, that disrupts the normal flow of the program's instructions.
Error is a serious problem that occurs during the execution of a program, that disrupts the normal flow of the program's instructions.

=============================================================================================================

QUE 3 Difference Checked Exception and Unchecked Exception

Checked Exceptions

These are the exceptions that are checked at compile time. If some code within a method throws a checked exception, then the method must either handle the exception or it must specify the exception using the throws keyword.
Ex: ClassNotFoundException, IOException, SQLException and InterruptedException.

UnChecked Exceptions

Unchecked exceptions are runtime exceptions that are not required to be caught or declared in a throws clause. These exceptions are usually caused by programming errors, such as attempting to access an index out of bounds in an array or attempting to divide by zero.
Ex: ArrayIndexOutOfBoundsException,ArithmeticException, NullPointerException. IllegalThreadStateException.

QUE 4,5,6,7 & 8. Coding part in below in GIT Repository

https://github.com/Hameed1206/Task11ExceptionHandling

TASK 2 Test Case Design Techniques

Hameed Hussain — Mon, 25 Mar 2024 10:26:10 +0000

Question : 1 ->

Test Scenario 1

==================
Test Case 1 : Validating without appointment data
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Valid data in Email field
Enter Valid data in Phone Number field
In appointment Field Don't choose any, just leave empty and try to book

Expected Result : It should display error "All fields are required"

Test Case 2 : Validating without Phone number
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Valid data in Email field
Leave the Phone Number field Empty/Blank
In appointment Field choose a available slot

Expected Result : It should display error "All fields are required"

Test Case 3 : Validating without Email data
Enter Valid data in First name field
Enter Valid data in Last name field
Leave the Email field Empty/Blank
Enter Valid data in Phone Number field
In appointment Field choose a available slot

Expected Result: It should display error "All fields are required"

Test Case 4 : Validating without Last name data
Enter Valid data in First name field
Leave the Last name field Empty/Blank
Enter Valid data in Email field
Enter Valid data in Phone Number field
In appointment Field choose a available slot

Expected Result : It should display error "All fields are required"

Test Case 5 : Validating without First name data
Leave the First name field Empty/Blank
Enter Valid data in Last name field
Enter Valid data in Email field
Enter Valid data in Phone Number field
In appointment Field choose a available slot

_Expected Result _: It should display error "All fields are required"

With the above approach we can ensure the if any field is left blank then we should not book appointment.

Test Scenario 2

==================
Test Case 1 : Validating with Invalid email (eg., Without @ symbol)
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Invalid Email in email field (eg., Enter without @ symbol)
Enter Valid data in Phone Number field
In appointment Field choose a available slot

_Expected Result _: It should display error "Please enter a valid email"

Test Case 2 : Validating with Invalid email (eg., Without . symbol)
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Invalid Email in email field (eg., Enter without . symbol)
Enter Valid data in Phone Number field
In appointment Field choose a available slot

Expected Result: It should display error "Please enter a valid email"

Test Case 3 : Validating with more than one @ symbol.
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Invalid Email in email field (eg., Enter @ symbol twice)
Enter Valid data in Phone Number field
In appointment Field choose a available slot

Expected Result : It should display error "Please enter a valid email"

Test Case 4 : Validating with more than one . symbol
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Invalid Email in email field (eg., Enter . symbol twice)
Enter Valid data in Phone Number field
In appointment Field choose a available slot

_Expected Result _: It should display error "Please enter a valid email"

Test Case 5 : Validating with continuous special characters
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Invalid Email in email field (eg., Enter @ and . symbols together like @.)
Enter Valid data in Phone Number field
In appointment Field choose a available slot

Expected Result: It should display error "Please enter a valid email"

In the above approaches we are trying to enter invalid email like without @ or . symbols.
Any email ID will contain @ and . symbols. So If the data entered in field not having these symbols means it should throw error
Also we are testing by giving each symbols twice and also together, which are also not valid email , So the page should throw error as "Please enter a valid email".

Test Scenario 3

===================

Test Case 1 : Validating with 9 digits
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Valid data in Email field
Enter Invalid Phone Number in Phone number field (eg., Enter 9 digit no)
In appointment Field choose a available slot

Expected Result : It should display error "Please enter a valid Phone Number"

Test Case 2 : Validating with 11 digits
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Valid data in Email field
Enter Invalid Phone Number in Phone number field (eg., Enter 11 digit no)
In appointment Field choose a available slot

_Expected Result _: It should display error "Please enter a valid Phone Number"

Test Case 3 : Validating with 9 numbers and 1 alphabet
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Valid data in Email field
Enter Invalid Phone Number in Phone number field (eg., Enter 9 digit no and 1 alphabet)
In appointment Field choose a available slot

Expected Result : It should display error "Please enter a valid Phone Number"

Test Case 4: Validating with 10 numbers and 1 alphabet
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Valid data in Email field
Enter Invalid Phone Number in Phone number field (eg., Enter 10 digit no and 1 alphabet)
In appointment Field choose a available slot

Expected Result : It should display error "Please enter a valid Phone Number"

In above case we are trying to validated the phone number field with invalid data
So we are using boundary value analysis technique
In case 1 and 2 we are giving phone number with 9 and 11 digits, Any phone number will have 10 digits, so the field should not accept the data other than 10 digits.
In case 3 and 4 I am trying to give 9/10 numbers and 1 alphabet to ensure it accepts only numerical value.

Test Scenario 4

==================

Test Case 1 : Trying to book a already booked slot
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Valid data in Email field
Enter Valid data in Phone Number field
In appointment Field choose a slot which is already booked

Expected Result : Form should not be submitted and display error as "Please choose another date/time"

Test Case 2 : Trying to book a out of range slot
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Valid data in Email field
Enter Valid data in Phone Number field
In appointment Field choose a slot which is not available (Like outside range)

_Expected Result _: Form should not be submitted and display error as "Please choose another date/time"

Test Case 3 : Trying to book a slot from past date
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Valid data in Email field
Enter Valid data in Phone Number field
In appointment Field choose a slot from past date/Time

Expected Result: Form should not be submitted and display error as "Please choose another date/time"

Test Scenario 5

==================

Test Case 1 : Validating with all valid data and conform slot booking
Enter Valid data in First name field
Enter Valid data in Last name field
Enter Valid data in Email field
Enter Valid data in Phone Number field
In appointment Field choose a available slot

Expected Result : Appointment should be successfully scheduled.

==================================================================

Question : 2 ->

Test Scenario 1

==================

Test Case 1 : New Account Creation
-> Users open the Application and Navigated to Account Creation Page
-> User enter Valid data in all respective fields (eg., First Name, Last Name, Email, Password)
-> Users clicks the submit button
-> Ensure Account is created and Account creation confirmation mail received

Expected Result : Account should be created and Confirmation mail is received

Test Scenario 2

===============

Test Case 1: Checking with password does not match the required complexity standard
-> Users enters valid data in First Name, Last Name, Email Fields
-> Users enter Invalid password which does not meet the complexity requirement (eg., Shorter length, Longer length, without lower case/uppercase/numbers/special characters)
-> Users click the submit button
-> Ensure Account is not created and respective error message displayed

Expected Result : Account not created and displays a error "Password does not meet the requirement"

Test Scenario 3

===================

Test Case 1 : Account Deletion
->Application is opened, Logged in and Navigated to settings page
->Now click the delete account tab
->Click confirm delete
->Ensure Account is deleted and should not be able to login anymore

Expected Result : Account is deleted and user not able to login the deleted account

Test Scenario 4

==================

Test Case 1: Application Navigation and performance
-> Application is opened and Logged in.
-> Navigate to different fields and functions
-> Perform various actions like account creation, deletion.
-> Ensure the app performance is good

Expected Result : Application should navigate seamlessly without any crashes or performance issues

Test Scenario 5

==================

Test Case 1 : Validating Unauthorized access
-> Login as basic user
-> Try to access premium features
-> Make sure user not able to access

Expected Result : User should not be able access premium features and gets error as "Unauthorized access / Permission denied"

Test Case 2: Validating premium user access
-> Login as premium user
-> Try to access premium features
-> Make sure user able to access all features

Expected Result: User should be able to access all premium features

Test Case 3 : Validating Admin user access
-> Login as Admin user
-> Try to access all advanced settings and features
-> Make sure user able to access all advanced settings and features

Expected Result: User should be able to access all advanced settings and features

TASK 5

Hameed Hussain — Tue, 19 Mar 2024 14:06:14 +0000

Question 1 : Write Test cases for any one scenario from Book My Show application

Answer:

Please find the Google sheet link below
Refer both sheet 1 and sheet 2
Sheet 1 : Select your city module
Sheet 2 : Sign In module

https://docs.google.com/spreadsheets/d/1G_7zHPXGsWuHR2o7VSyr-ClHswRRx_24CyrjiqJDKlo/edit?usp=sharing

= = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = =

Question 2 : Write Key points Test Scenario, Test Case, Test Strategy, Test Plan and Test summary report

Answer:

Test Scenario:

-> A test scenario is a high-level description of a specific module or function we going to test from software application
-> It describes a Overall user's interaction with the system on what user going to do.
-> Test scenarios are often derived from user stories and requirement.
-> They focus on the end-to-end flow of the application and help identify test cases needed to validate the functionality.

Test Case:

-> A test case is a detailed description of a specific test scenario, including test inputs, actions, and expected results.
-> It provides step-by-step instructions for executing a test scenario.
-> Test cases include Test case ID, Test Case description, preconditions, test steps, expected results, Actual results, status and comments.

Test Strategy:

-> The Test Strategy is a higher-level document that defines the overall testing approach for a specific project. It sets the direction for testing by providing guidelines and principles to be followed.
-> It defines the testing objectives, scope, methodologies, tools, and resources required for testing.
-> Test strategies address factors such as testing types (e.g., functional, performance, security), automation, test environment setup, and risk management.

Test Plan:

-> A test plan is a detailed document that outlines the specific test activities, schedules, and resources required to execute the test strategy.
-> It provides a roadmap for the testing process, including test objectives, scope, approach, deliverables, and timelines.
-> Test plan include information on test environment setup, test execution, defect management, and reporting.
-> They are developed based on the test strategy and may be updated throughout the project lifecycle to reflect changes in requirements or priorities.

Test Summary Report:

-> A test summary report is a comprehensive document that provides an overview of the testing activities, results, and findings.
-> It summarizes the test execution status, including the number of test cases executed, passed, failed, and blocked.
-> Test summary reports highlight key findings, issues, and risks identified during testing, along with recommendations for improvement.
-> They serve as a communication tool for stakeholders, providing insights into the quality of the software and informing decision-making processes.

TASK 4

Hameed Hussain — Fri, 15 Mar 2024 02:35:18 +0000

Question: 1 (1) -> Describe the difference between smoke testing and sanity testing

Answer:

Smoke Testing:

-> Smoke testing, also known as build verification testing (BVT), is performed early in the software development lifecycle to verify whether the software build is stable enough to proceed with further testing. Ensuring that the critical and essential functionalities of the application are working correctly after a new build or release.
-> The primary goal of smoke testing is to identify major defects or showstopper issues that could prevent further testing or deployment of the software build. Smoke testing does not go in depth of any functionalities but focuses on the overall stability of the application.

Sanity Testing:

-> Sanity testing is performed in replace for regression testing due to lack of time or time consumption. Focusing only on specific functionalities or areas of the application have been fixed or updated after changes or modifications. Also verifying the specific functionalities or features that have undergone changes, enhancements, or fixes, rather than testing the entire application comprehensively.
-> The purpose of sanity testing is to ensure that the recent changes or modifications have not adversely affected the stability or behavior of the application, and it is ready for further testing or deployment. Sanity testing involves more targeted and focused testing of the specific features or functionalities to ensure their correctness and stability.

Question: 1 (2) -> Describe the difference between validation and Verification

Answer:

Verification:

Verification is the process of verifying the software meets the specified requirements and design. Verification focuses on ensuring that the software is built correctly according to the defined specifications, design documents, and requirements. It also include reviewing and inspecting software artifacts such as requirements documents, design specifications, source code, and test cases to check for consistency, correctness, and adherence to standards.

Validation:

Validation is the process of evaluating whether the software product satisfies the user's needs and expectations. Main focus is to ensure that the software product meets the user's requirements and delivers the expected functionality and usability. Validation activities include testing the software in real-world scenarios, gathering feedback from users and stakeholders, and perform testing to verify that the software meets user needs and business objectives.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Question: 2 -> Explain about Agile Methodology

Answer:

Agile methodology is an iterative approach to software development, where we divide a Huge amount of work in to small pieces. Once each set of work is completed, we are going for product release/deployment. In Agile, we work with all other department people, collaborating with them and finding the issues early and working on its fix. Main thing is, we will be collaborating with Customer throughout the process to have a smooth and clear progress. Agile supports changes in requirement which makes customer satisfy and happy.
On a whole in software development, Agile methodology is one, which is very flexible, making way for people collaboration and working together to identify issues early and rectify. Due to this iterative approach we are able to give continuous delivery & improvement to the product and also by accepting changes, we ensures customer satisfaction.

Principles of Agile Testing

Constant response
Less documentation
Continuous Testing
Customer Satisfaction
Easy and clean code
Involvement of the entire team
Test-Driven
Quick feedback

In Agile methodology, there are several approaches or frameworks that we can adopt to implement Agile principles and practices effectively. The most commonly used Agile frameworks are Scrum and Kanban

Scrum:

-> Scrum is one of the most widely used Agile frameworks, which have a fixed time interval called sprint, lasting 1-4 weeks for every release
-> Scrum having some set of rules which will be followed, We have a fixed set of people who involves in scrum process
Product owner
Scrum master
Development team
QA Team
above are the main key participants in scrum based project.
-> Key components of Scrum include sprint planning, daily stand-up meetings, sprint reviews, and sprint retrospectives ceremonies

Kanban:

-> Kanban is an Agile approach that focuses on visualizing work, limiting work in progress (WIP), and optimizing flow.
-> Kanban boards visually represent the workflow, with columns representing different stages of work and cards representing individual tasks or user stories.
-> Teams use pull-based systems to manage work, with tasks pulled into the workflow only when there is capacity to handle them.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Question: 3 -> Explain about Epic and User Stories

Answer:

EPIC:

-> Epic is a large body of work which can be break in to small pieces of work.
-> Any Function that can be further divided into multiple small pieces is Epic, the branches under the functions is nothing but the User stories.
-> Epics provide a overview of the particular set of functionalities and help stakeholders understand the overall direction and objectives of the project.

EG., In Amazon website we can see options like electronics, men's wear, women's wear, kids wear, home appliances.
All these where whole functions (EPIC). Below that we have lot of small functions or divisions which is User stories
EPIC ->> Electronics->

Mobile
Laptop
Head phone

User Story:

-> User Story describes a piece of functionality or a feature from an end-user's perspective.
-> User Stories are written from the perspective of the user.
-> Each User Story follows a simple template: "As a user, I want [some goal or objective], so that [some benefit or value]."
-> User Stories capture the "who," "what," and "why" of a feature, focusing on the user's needs, requirements, and desired outcomes.
-> User Stories are small, manageable units of work that can be implemented and tested within a single iteration or sprint.
-> Under User stories we will be having lot of sub tasks.

EG., In Amazon website we can see options like electronics, men's wear, women's wear, kids wear, home appliances. All these options can be further divided in to small pieces. Those each valuable functions will be tested from user point of view, which is nothing but User Stories.

EPIC ->> Electronics->

User Stories

Mobile
Laptop
Head phone

TASK 3

Hameed Hussain — Wed, 13 Mar 2024 09:36:06 +0000

Question: 1 -> List down all models of SDLC

Answer:

Models of SDLC:

Waterfall Model
V-Model (Verification and Validation Model)
Prototype Model
Spiral Model
Iterative Model
Incremental Model
Big Bang Model
Agile Model (Includes various methodologies/Frameworks such as Scrum, Kanban, etc.)
Rapid Application Development (RAD) Model
DevOps Model

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Question: 2 -> What is STLC ? Also, Explain all stages of STLC.

Answer:

STLC (Software Testing Life Cycle) is a process performed by Testing team to validate and ensure the software Quality.

Stages in STLC:

1. Requirement Analysis:
-> In Initial stage, Testing team will work with Product Owner to understand the requirement of application.
-> Requirement will be done from testers point of view. Like, Checking whether the requirement can be tested or not.
-> Main objective is to understand the requirement specifications of software and making sure whether we can able to perform testing in all fields.

2. Test Planning:
-> Test planning is a stage where we do planning on how to conduct test, and what kind of tools required and, also how many resources needed.
-> Also, we will decide to choose which approach of testing technique has to be implemented for each requirement.
-> Test Estimation , deciding the test approach and techniques also entry and exit criteria.

3. Test case preparation:
-> Test cases will be developed with test steps for each and every scenario.
-> Test case will be developed with following contents,
Test case ID, Scenario headline, Test case title, Preconditions, Test steps, Expected result, Actual result, Status(pass/fail), comments.
-> Test case will be reviewed and approved by PO.

4. Test Environment setup:
-> We need a test environment to test the application, which will be similar to production environment.
-> Environment setup has to be made with respective configuration and infrastructure that is required for testing.
-> If needed test data also prepared and loaded in this environment.

5. Test Execution:
-> Test execution is stage where we actually performs the testing actions we wrote in test cases.
-> As per test case and requirement, all the field will be validated and if any discrepancy found we need to raise a defect and report it.
-> We have to make sure that test results are recorded and documented.

6. Defect logging and tracking:
-> We will raise a defect if we found any issues or discrepancy in software application.
-> We will use a tool to log a defect and track it, like JIRA.
-> We have yo prioritize the defects as per severity and priority.
-> In JIRA or other defect tracking tool, we can track the defect status and to get resolution from developers.
-> Once defect is fixed, we do retest and validate it.

7. Test Reporting:
-> Test reporting involves generating test reports to communicate the progress, results, and quality of the testing effort to stakeholders.
-> Based on testing report the stakeholders will take a decision on software release.
-> Test report will include Test coverage, defect density and execution report.

8. Test Closure:
-> Test closure marks the end of the testing phase.
-> It involves evaluating the testing process, identifying lessons learned, and documenting best practices and areas for improvement.
-> Test closure also includes obtaining sign-off from stakeholders indicating that testing is complete and the software is ready for release.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Question: 3 -> Risk factors that need to include in test plan

Answer:

When creating a test plan for a web-based application, it's important to consider various risk factors that could affect the functionality, security, performance, and usability of the application.
Risks factors called as RAID block. Risks Assumptions issues dependencies

-If we depend on any team if they did not deliver the work this will affect our schedule
-If we need any equipment's or tools from client or management, then we depend on that, If its not delivered on time that will affect our execution.
-Also we need to plan resources, if anyone is not available means that will also affect the deliver
-If there is sudden requirement change has been told means, we need to plan such cases also.
-And Natural Disaster also a risk factor in test planning.
Like above we can assume lot of list factors depends on our application

Some of the common risk factors we need to take care every time.

-> Functional Risks:

Misunderstanding the requirement, we need to ensure that we understand the requirement completely.

-> Security Risks:
Unauthorized access to sensitive data or resources due to security vulnerabilities. we should plan a clear strategy and risks factors when it comes to security testing.

-> Performance Risks:
There might be performance issues like slow down, late response due to inadequate server.
There might be a chance of environment failure, then we should plan to do testing in different environment

-> Compatibility Risks:
Need to check in all browsers and platforms to make sure application functions as expected in all areas

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Question: 4 -> What is QA & QC ? Distinction between QA and QC responsibilities

Answer:

Quality Assurance (QA):

Quality Assurance (QA) is a process of ensuring that the processes, procedures, approaches, techniques and standards used to develop and deliver products meet predefined quality requirements. Assurance will be given by organization management, giving a positive declaration on product which obtains confidence outcome.

-> QA focuses on preventing defects by following and implementing processes, standards, and guidelines throughout the product development lifecycle.
-> Responsibilities include defining quality objectives, designing quality management systems, establishing quality standards and metrics, and ensuring compliance with industry regulations and best practices.
-> QA ensures that processes are in place to identify potential issues early in the development process, thereby minimizing the likelihood of defects in the final product.
-> QA activities involve continuous monitoring, evaluation, and improvement of processes to enhance efficiency, effectiveness, and overall product quality.
-> Examples of QA responsibilities include developing quality assurance plans, conducting process audits, providing training and support to team members, and promoting a culture of quality within the organization.

Quality Control (QC):

Quality Control (QC) refers to the set of activities and techniques used to evaluate and verify that a product meets specified quality requirements and standards.

-> QC focuses on identifying defects and deviations from quality standards through inspections, testing, and analysis of the final product or service.
-> Responsibilities include conducting product inspections, performing tests to verify compliance with specifications, analyzing defects.
-> QC ensures that the final product meets specified quality requirements and satisfies customer expectations by detecting and rectifying defects before delivery.
-> QC activities involve both manual and automated testing processes, including functional testing, regression testing, performance testing, and usability testing.
-> Examples of QC responsibilities include executing test cases, analyzing test results, reporting defects, collaborating with development teams to resolve issues, and ensuring the overall quality of the final product.

In summary, QA sets the standards and guidelines for product development, whereas QC validates whether those are satisfied. In other words QC activities focus on identifying defects in the actual products, QA responsibilities aim to prevent defects by establishing and maintaining effective processes, standards, and guidelines.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Question: 5 -> Difference between manual and automation testing

Answer:

Manual Testing:

Manual testing is the process of manually testing the software application and executing test cases to identify defects or errors in software without using any automated testing tools or techniques.

-> Test cases are executed manually by human testers, who interact with the software application's user interface (UI) to perform various tests, validate functionality, and verify expected behavior.
-> Manual testing allows testers to adapt test cases and test scenarios dynamically based on their intuition, domain knowledge, and exploratory testing techniques. where testers explore the software application dynamically to uncover defects and identify potential areas of improvement.
-> Manual testing is effective testing as human eye can catch more defects and also we can test scenarios that involve subjective evaluation, and real time user experience validation.
-> Manual testing offers flexibility and adaptability in test execution, allowing testers to make real-time decisions and adjustments.

Automation Testing:

Automation testing is the process of using automated testing tools and scripts to execute test cases, validate software functionality, and compare actual results against expected results.

-> Test cases are automated using specialized testing frameworks, scripting languages, and test automation tools, allowing for the automated execution of repetitive test scenarios and regression testing.
-> Automation testing ensures repeatability and consistency in test execution by eliminating human errors and variability in testing processes.
-> Automation testing is ideal for regression testing, where repetitive test cases are executed to verify that new changes or enhancements do not adversely affect existing functionality.
-> Automation testing is scalable and efficient for testing large and complex software applications, enabling faster test execution and broader test coverage.

In summary, Both Manual and Automation are effective in market. We can go with manual testing in initial phase of software testing and can convert it to automation in future for doing large amount of testing. If the application is more dynamic we can adopt manual testing, if application is stable then lets go with Automation approach. Manual testing needs more resources and time, But Automation testing need only tools and script for execution. Manual testing is suitable for exploratory testing, usability testing, and scenarios requiring subjective evaluation, while automation testing is suitable for regression testing, performance testing, and scenarios requiring repetitive test execution.

=== = * = === = * = === = * = === = * = === = * = === = * = === = * = === = * = === = * = === = * = === = * = === = * = === = * = = = *

Have a look here for Types of Testing , STLC Phases , Qualities of Manual Tester & Testing Methodologies

Hameed Hussain — Wed, 06 Mar 2024 16:35:45 +0000

Types of Testing :

There are various types of testing that are performed throughout the software development life cycle to ensure the quality and reliability of software products. Some of the common types of testing include:

Unit Testing: This testing is performed by developers on individual units or components of the software to verify that each unit functions correctly in isolation.

Integration Testing: Integration testing is conducted to test the interactions between different units or components of the software to ensure that they work together as expected.

System Testing: System testing involves testing the entire software system as a whole to validate that it meets the specified requirements and functions correctly in various scenarios.

Acceptance Testing: Acceptance testing is performed to determine whether the software meets the acceptance criteria and satisfies the stakeholders' requirements. It can include User Acceptance Testing (UAT) where end-users validate the software against their needs.

Regression Testing: Regression testing is conducted to ensure that recent changes or enhancements to the software do not adversely affect the existing functionality. It involves retesting previously tested features to verify that they still work as intended.

Sanity Testing: Sanity testing, also known as Sanity check or Build Verification Testing (BVT), is a type of testing performed on a stable build of the software application to ensure that the critical functionalities work as expected. It is a subset of regression testing and the focus of sanity testing is not to verify all functionalities but to ensure that the most crucial features are working correctly.

Smoke Testing: Smoke testing, also known as Build Verification Testing (BVT) or Build Acceptance Testing, is a type of testing performed on a freshly built software application to verify that the basic functionalities work as expected and the application is ready for further testing.

Retesting: Retesting is a type of testing performed to verify that a previously identified defect has been fixed correctly and the affected functionality now works as expected. Retesting is typically performed as part of the defect resolution process, where developers fix reported defects, and testers verify the fixes before the software is released.

Performance Testing: Performance testing evaluates the responsiveness, throughput, reliability, and scalability of the software under various load conditions. It includes types such as Load Testing, Stress Testing, and Scalability Testing.

Security Testing: Security testing is performed to identify vulnerabilities and weaknesses in the software's security mechanisms. It includes tests such as Penetration Testing, Vulnerability Scanning, and Security Audits.

Usability Testing: Usability testing assesses the software's user interface and user experience to determine how easy and intuitive it is for end-users to use the software.

Compatibility Testing: Compatibility testing checks whether the software functions correctly across different devices, operating systems, browsers, and environments.

Exploratory Testing: Exploratory testing is an informal testing approach where testers explore the software application dynamically and spontaneously to uncover defects and identify potential areas of improvement. Testers use their domain knowledge, intuition, and creativity to design and execute test scenarios in real-time.

STLC Phases :

Software Testing Life Cycle(STLC) typically consists of the following phases:

Requirement Analysis: In this phase, testers analyze the requirements to understand the scope of testing and identify testable requirements.

Test Planning: Test planning involves defining the testing objectives, scope, approach, resources, and timelines. Test plans and test strategies are created during this phase.

Test Case Development: Test cases are created based on the requirements and test conditions identified during the requirement analysis phase. Test cases outline the steps to be executed, expected results, and test data.

Test Environment Setup: The test environment is set up to mimic the production environment where the testing will take place. This includes configuring hardware, software, and network components.

Test Execution: Test cases are executed based on the test plan. Testers run the test cases, record test results, and report any defects found during testing.

Defect Reporting and Tracking: Defects found during test execution are reported in a defect tracking system. Testers track the status of defects from discovery to resolution.

Test Closure: In this phase, the testing activities are formally concluded. Test closure activities may include summarizing test results, preparing test closure reports, and obtaining sign-off from stakeholders.

Qualities of Manual Tester

Manual tester is the one who ensures the software is developed as per requirement and also to achieve a good quality to sustain in market. Manual tester should possess several important qualities that contribute effectiveness in testing software.

Attention to Detail: One should have a keen eye for detail and can identify even the smallest discrepancies or inconsistencies in the software under test.

Example:
You are assigned to test a web application's registration form, which includes fields for the user's name, email address.

->So at First you enter a valid email address in the email field and ensure that the form accepts it without error.
Next, you enter an invalid email format (e.g., missing "@" symbol) and verify that the form displays an appropriate error message prompting the user to enter a valid email address.

Analytical Thinking: One should possess strong analytical skills, allowing to break down complex problems into manageable components and identify the root cause of issues.

Example:
->While reviewing the requirement, you think analytically about potential edge cases or boundary conditions that may impact the system's behavior.
->For example, you consider scenarios such as testing with email addresses containing special characters, testing with email addresses exceeding the maximum character limit, and testing with email addresses from different domains.

Communication Skills: Effectively communicate with stakeholders, developers, and other team members to convey testing results, report defects, and discuss testing requirements

Example:
->When you encounter defects during testing, you carefully document them in the defect tracking system, providing detailed information such as steps to reproduce, expected behavior, and actual behavior.
->You prioritize defects based on severity and impact, clearly communicating the urgency of fixing critical issues to the development team and product owner.
->As you work closely with developers to resolve defects, you maintain open and constructive communication, discussing the root cause of issues and proposing potential solutions.
->You provide feedback on the effectiveness of defect fixes and collaborate with developers to verify the resolution of issues through retesting.

Adaptability: One should be Adaptable and can quickly adjust to changing project requirements, priorities, and timelines.

Example:
->Your testing team receives updated requirements from the project manager.
->Despite the tight deadline, you adapt quickly to the changes by reviewing the updated requirements and adjusting your testing approach accordingly.
->You analyze the new requirements and identify the areas of the application affected by the changes.
->You promptly update your existing test cases to reflect the changes, adding test scenarios to verify the new functionality.

Problem-Solving Skills: Need to demonstrate strong problem-solving skills, allowing to identify creative solutions to testing challenges and overcome obstacles encountered during testing

Example:
->During testing, you encounter a scenario where the system does not correctly handle email addresses with special characters, such as underscores or hyphens.
->Instead of simply reporting the issue, you analyze the underlying cause by examining the system's validation logic and the handling of special characters in email addresses.
->Based on your analysis, you identify that the system's regular expression for email validation does not account for certain special characters, causing the validation to fail.
->You propose a solution to update the regular expression pattern to include the necessary special characters, ensuring that the system accurately validates email addresses according to the requirement.

Waterfall Methodology:

Sequential Approach: Waterfall follows a linear and sequential approach to software development, where each phase (requirements, design, implementation, testing, deployment) is completed sequentially and the next phase begins only after the previous one is finished.

Detailed Planning: Waterfall requires comprehensive planning and documentation upfront, with all requirements and design specifications defined in detail before development begins.

Rigid Structure: Waterfall is characterized by its rigid and inflexible structure, with limited room for changes once the project moves into the implementation phase.

Longer Timeframes: Due to its sequential nature and upfront planning, Waterfall projects typically have longer development cycles and may face challenges in adapting to changing requirements.

High Documentation: Waterfall emphasizes extensive documentation throughout the development process, including requirements documents, design specifications, and test plans.

Agile Methodology:

Iterative and Incremental: Agile follows an iterative and incremental approach to software development, where requirements, design, implementation, and testing are carried out in short, iterative cycles called sprints.

Adaptive Planning: Agile promotes adaptive planning and welcomes changes in requirements, design, and priorities throughout the development process. Requirements evolve and are refined collaboratively with stakeholders.

Flexibility: Agile is characterized by its flexibility and ability to respond to changing customer needs and market conditions. Teams can adjust priorities and make course corrections quickly based on feedback received during each iteration.

Continuous Integration and Testing: Agile encourages continuous integration and testing, with a focus on delivering working software incrementally at the end of each sprint. Testing is integrated throughout the development process, ensuring early detection and resolution of defects.

Collaboration and Communication: Agile emphasizes collaboration and communication within cross-functional teams, with a strong focus on customer collaboration and delivering value to the customer.

Difference Between Waterfall and Agile methodologies

The main differences between Waterfall and Agile methodologies lie in their approach to planning, flexibility, adaptability to change, and level of customer involvement.
->Waterfall is characterized by its sequential structure and detailed upfront planning.
->Agile is known for its iterative and adaptive approach, fostering collaboration, flexibility, and continuous improvement.