DEV Community: Muruganandh Srinivasan

Automation Testing

Muruganandh Srinivasan — Mon, 09 Oct 2023 18:23:29 +0000

Difference Between Automation and Manual Testing :

Automation Testing:-

Automation Testing uses automation tools to execute test cases.
Automated Testing is Processing Time faster than a manual testing.
Installing Automation Tool(Some Tools are paid)Investment in the automated testing is higher.
Automated Testing does not involve Human consideration.
Automation Testing can be executed on different operating Platforms in parallel time and reduce test execution time.
Programming knowledge is a must in Automation Testing.
It is Accurate because of Automation Tools scripts and Error risks are zero.
Automation testing is useful when executing the same set of test cases continuously.
In Automation Testing different types of Frameworks methods like POM, Cucumber, TestNG and Data-Driven to faster the Automation process.

Manual Testing:-

In Manual testing, Test cases are executed by a human tester.
Manual Testing is Time-consuming one.
The initial investment in the Manual testing is lower than Automation Testing because of No installation of Software Tools.
In Manual Testing method it allows Human observation.
In Manual Testing can be executed in parallel but would need to increase your Human Resource which is expensive for maintain.
Programming Knowledge is not Necessary in Manual Testing.
Due to Manual Execution Error May occurs in chance.
Manual Testing is useful when the Test cases only needs to Run once or twice.
Manual testing doesn’t use Framework Methods.

Automation Testing Tools :-

Selenium:-

Selenium is an Open-Source Web Automation Tool, currently in High demand and widely Used Tool in Worldwide.
It is one of the Best QA automation Tools that can Automate Multiple OS Like Windows, Mac, and Linux and Web Browsers like Firefox, Chrome, IE etc..,
Selenium Web-driver is powerful Because it Supports Multiple Programming Languages, Various Browsers & Different OS.
Also Selenium supports Mobile Applications like iPhone, Android etc..,
Unavailability of Technical support because of Selenium is Open-Source Tool.
Selenium Doesn't support to Automate the Desktop applications.

QTP:-

QTP Tool is used to Test functional Regression Test Cases of the Web-Based Application.
HP-QTP stands for Quick Test Professional. HP Quick Test Professional was originally owned by Mercury Interactive and it was acquired by Now HP.
This is Very Helpful for the New Test Engineer because they can Understand this tool easily. HP-QTP is designed on the scripting language like VB Script(Visual Basic)language to automate the application.
This Tool support Record and Playback feature.
Both Technical and Non-Technical Tester can use QTP.
In HP-QTP We can Test Both Desktop and Web-Based Applications.

Selenium IDE:-

Selenium IDE (Integrated Development Environment) it is a Record and Run tool that a test case developer uses to develop Selenium Test cases.
Selenium IDE is a Open Source Automation Tools.
No Coding knowledge required. Easy to install and just install any other browser extension.
Test scripts recorded in Selenium IDE can be exported to different programming languages like Java, Python etc..,
Selenium IDE is not as powerful as other Selenium tools (WebDriver) because of it not support complex testing scenarios.
Selenium IDE is a useful tool for simple and quick web testing but may not be the best choice for complex or large-scale projects.

Katalon Studio:-

The Katalon Studio is a Low-code Automation Testing Tool for Web, API, Desktop(Windows) and Mobile Applications.
This Tool support Record and Playback feature.
This Tool support Manual and Scripting mode.
Katalon Studio Subscribers will be Provided with Tech Product support.
The Katalon Studio is Free with Basic Testing features.
Katalon Studio support Java and Groovy Programming Languages only.
Katalon Studio can work on macOS, Windows and Linux.

Cross Browser Testing :-

Cross-browser testing is a type of Non-Functional software Testing where Web Applications are to Check the support Different Browsers and Devices.

The QA Testing Team is Most Responsible for Cross-Browser Testing Activities. The QA Testers Execute the Same Test cases on Different Platforms and Browser to Comparing and Analyzing the Behavior of the Website in Different browser.

Using Selenium Grid we can achieve Cross Browser Testing.
Selenium Grid is a smart proxy server that makes it easy to run Tests in parallel on Multiple Machines.

In Selenium Grid will allow you to Run Test cases in Different Browsers and Versions simultaneously.

Selenium support Different type of Cross-Browser Testing tool for automation. Using TestNG framework we can do Cross Browser Testing also.

TDD :-

Test Driven Development (TDD) is Software Development approach in which Test cases are Developed to specify and validate what the code will do.
Test cases for each functionality are Created and Tested first and if the Test fails then the New Code is Re-Written and making the Code Simple & Bug-free.

Write a Test: In Beginning the Test case are created and it expected behavior of the test case should fail Initially, and next phase the Code has to be update.
Write the Code: The Aim is to make the Test cases to be Pass. So, In this phase Code has to be Update and this time it has to Fulfill the Expected Requirements in the Test case.
Run the Test: Execute the Test cases to check if it Passes or Not. If it is Pass then Move on to Next Functionality. If it fails, Then Continue With the Code Until the Test Passes.
Refactor: If The Test passes, then Refactor the code to make it more efficient to ensure the Test Still Passes.

Using TDD Identify the Bugs early stage of development process and It provides Confidence that code Works as its expected.

BDD :-

BDD stands for Behavior-Driven Development. It is one kind of Framework that enables the Software testers to complete test scripting in plain English, So a Non-Programmers can read and understand the requirements of software.

Cucumber is one of the Best tools used to Develop in the BDD Framework.

User Story: It Explains the functionality of the software were it written by the End-user perspective.
Scenario: Scenario Describes the product's behavior from the user's perspective
Given: Given (What all are the given conditions),
when: When (A particular action to be taken)
Then: Then (The result of that action)

BDD is written in Gherkin Language easy to understand by Stakeholders and Non-Technical users also.
By using Gherkin Language Stakeholders and Humans can read and Better communications.

Test Case Design Techniques

Muruganandh Srinivasan — Wed, 30 Aug 2023 08:32:49 +0000

Decision Table :

The App has three Different user roles like Basic user, Premium user and Admin user and these are the following test scenarios to execute :-

Scenario 1: User Roles and Access

Test Objective: To verify that different user like (Basic, Premium, Admin) have appropriate access to features.

Test Steps:

Log in as a basic user.
Verify that basic user have only limited features are accessible.
Log out and repeat the continue same process to Premium and Admin user.
Verify that Premium users have all access and Admin users can process Advanced settings.

Expected Results:

Basic user should only be able to access limited features. Premium user should have access to all features.
Admin user should have all features and advanced settings.

Scenario 2: Account Creation and Deletion

Test Objective: To verify that users can create and delete their accounts successfully.

Test Steps:

Get into the Account creation Page.
Enter all valid information, including a password that meets required standards.
And Submit the form and verify successful account creation.
Log in to the Newly created account.
And Delete the Account and verify successful deletion.

Expected Results:

Account creation should succeed with Valid Information and with a strong password.
After Create, the User should get the Email Confirmation message.
After Account create User should be able to Login the app.
Account deletion should delete the User Account.

Scenario 3: App Navigation and Error Handling

Test Objective: To Verify that users can navigate the app without crashes, performance issues, and receive expected error messages.

Test Steps:

Log in with different user roles.
Navigate through various app sections and features.
Attempt actions that users are not authorized to perform.
Check for performance issues and crashes during navigation and action attempts.

Expected Results:

App navigation should be without crashes.
Performance issues should be low or avoid.
Users attempting unauthorized actions should receive error messages.

Agile Methodology

Muruganandh Srinivasan — Fri, 25 Aug 2023 10:54:34 +0000

Smoke Testing :-

Smoke Testing is one of the Functional testing to helps the Software build & It is also called as Build Verification Testing (OR) Build Acceptance Testing.

In software Testing process The Smoke Tests is to verifying the important features are working correctly or not and to identify the Bugs in the testing.

Smoke Testing is the Important testing in Initial stage whether any issues in that function or the bug has found in this Initial stage Test effort, Time Consuming, Cost effects are easily can be overcome.

Sanity Testing :-

Sanity Testing is one of the Functional testing to test the Minor change or New Build has released from the Developer team.

Sanity testing is to evaluate that all the defects have been solved and no added issues come after the new build has been released.

In this Testing is to verify the Whether the New Build doesn't affect the old working functionalities. Sanity Testing is a Mini Regression Testing.

Difference Between Smoke & Sanity Testing :-

Smoke Testing is to Check the Critical Functionalities of the program is working fine & Sanity Testing is to check the New functionality (or) Bugs have been fixed.
Smoke Testing is done in Initial Stage of the Testing process & The Sanity Testing is Done when New Bugs has been found or New Build has been released.
Smoke Testing is also called as Build Verification Testing(BVT) or Build Acceptance Testing(BAT) & Sanity Testing is also called as Mini Regression Testing.
Smoke Testing is to Test the Major and Minor functionality of the Software module & Sanity Testing is to test the Specific Software module.
Smoke Testing is done by either Developer or Tester & Sanity Testing is done only by the Tester.
Smoke Testing is check all software modules & Sanity Testing only check the Sanity Testing is check only the defect or modify modules.

Validation :-

Validation is like if the software product actually meets the exact needs of the customer or not. The Validation process is to check the software that fulfills the Customer needs and azure the working condition of Software in High quality.

Verification :-

Verification is like a process of Checking Documents, Design, Code to check if the software has been built according to the requirements or not. The aim of verification process is to check the quality of Software Application were designed.

Difference Between Validation & Verification :-

Validation checks only the Developed Product is right &
Verification checks the Developing product is right.
Validation involve in Basic Functional testing & Verification involve in checking Inspection, Reviews and Documents.
Validation check the software at the end of the development cycle & Verification check the software In between the development stage process.
Validation comes after the Verification process & Verification comes First and after only Validation process comes in.
Validation work with Code in Functional Testing & Verification work with Detailed Documents.

Agile Model

Agile model is a one of the most widely used SDLC Process for developing the software application in all Industry.

Nowadays it is widely use in process and it is easy to approach with collaborative to team members, with Clients, Project Stage, Results, Feedbacks from Customers feedback etc...,
Scrum

SCRUM is an agile project management process used to build software development based on Weekly Sprint meeting, Review Meeting and Retrospective meeting.

Scrum Master: The Scrum Master lead the Scrum team for developing the software. Scrum Master arrange the meeting, Helps the Product owner and Support organization.
Product owner: The Product owner Knows the Aim of the Product and he is the In-charge of the product development and
He communicate with Development Team and Master.
Scrum Team: In Scrum Team each member is responsible for
delivering High quality product with collaboration with each other and self motivated.

Epic and User Story:-

Epic:

A Epic can be defined as a Task (or) User Story that can be divided into several smaller User Stories like Sub-task as per the customer's requirements.

The requirement of the software product is a divided into the collection of Epics and each Epics contains Tasks and Sub-tasks.

It helps the Agile team to know about the Roadmap of Product and Product workflow condition and Decision-making easily.

User Story:

A User story is the smallest unit of work in an agile framework and the User story is usually written from the user's perspective way.

The aim of a user story is little a piece of work are divided and it will deliver a valuable product back to the customer.

The user story describes the user requirement, what they want and why? and they are very easy to understand.

STLC & QA Testing

Muruganandh Srinivasan — Wed, 23 Aug 2023 15:23:18 +0000

1. Models Of SDLC

SDLC is a Software Development Life Cycle and it is a Process to produce or develop the software that satisfy the customer expectations.
Some phases of SDLC Models :

Waterfall
Agile

Waterfall Model

Waterfall model is a Straight Forward process and it is a Linear Sequential Model.

After One Phase of Output and Next Phase has to start with the help of Previous Phase.

It used in Earlier stage before, but Nowadays it is not widely used in Industry practice.

Agile Model

Agile model is a one of the most widely used SDLC Process for developing the software application in all Industry.

Nowadays it is widely use in process and it is easy to approach with collaborative to team members, with Clients, Project Stage, Results, Feedbacks from Customers feedback etc...,

Scrum

SCRUM is an agile project management process used to build software development based on Weekly Sprint meeting, Review Meeting and Retrospective meeting.

Scrum Master: The Scrum Master lead the Scrum team for developing the software. Scrum Master arrange the meeting, Helps the Product owner and Support organization.

Product owner: The Product owner Knows the Aim of the Product and he is the In-charge of the product development and
He communicate with Development Team and Master.

Scrum Team: In Scrum Team each member is responsible for
delivering High quality product with collaboration with each other and self motivated.

2. STLC:

STLC is process and also an integral part of Software Development Life Cycle (SDLC). STLC is a process used to test the software and confirm that product conditions works are met as per the customers needs.

1. Requirement Analysis : Analyzing customer needs and types of tests to be performed and gather the details about product from the customer about the software applications were to build.

2. Test Planning: After the Requirement Analyzing Preparation of test plan for different types of testing process are prepared like Selection of Test tools, Test Methods and Team allocation etc..,

3. Test Case Development: Test cases are developed based on the test plan and the Test cases written by its specific conditions, Priority, Inputs and expected outcomes.

4. Test Environment Setup: Testing environment is established by hardware, software, and network configurations based on the Systems engineer software developers and Dev-ops engineer.

5. Test Execution: The actual testing takes place here Testers execute the prepared test cases and record the outcomes and if any bugs send it to developers team and fix the issue after all bugs close the Reports are submitted.

6. Test Closure: Closure report is prepared and this report tells about the Testing activities, Results, Issues, and the quality of the software and all testing related activities have be completed and the software ready for release.

3. Risk Factors in Testing

Correct Planning: Insufficient time, skilled personnel can lead to incomplete testing.

Security Risks: Defects in the application can affect the user data.

Regression Risk: Introducing new features may impact the existing functionalities.

Performance Risk: Poor performance after new build can cause the user experience.

4. Diff Between the Responsibilities of Quality Assurance & Quality Control:

Quality Assurance: The Quality Assurance(QA)is a process to test the products to reach the high quality standards as per customers expected.

Quality Control: Quality Control(QC) is a process to test the defect in the product and and clear technical issues in the software and ready to use.

Difference between QA & QC :

QA is aimed to avoid the defect & QC is aimed to identify and fix the defects.
QA does not involve in coding and execution & QC Involve in Coding and execution.
QA requires involvement of Whole team & QC requires on Testing Team.
QA focuses on final product with high quality standards & QC focus on each process to build the software test.

Difference between Manual & Automation:

Test cases are done by Humans manually & Test Cases are done by software tools.
Time Consuming High in Manual & Time consuming Less in Automation.
Programming knowledge is not Necessary in Manual & Program Knowledge is Necessary in Automation.
Due to Manual errors may occur & Due to Automation Errors may avoid.
No cost effective by installation tools in Manual & Software tools needed and it cost effective is High.

Testing Methodologies & SDLC

Muruganandh Srinivasan — Mon, 21 Aug 2023 14:57:56 +0000

Software testing is a part of the software development process that helps the quality, functionality of a software product to improve by the Customer needs.

These Two are the Major Basic Testing Methodologies are Functional and Non-functional types of testing.

Functional Testing: Functional Testing is a testing to checks whether the software functions works according to the specified requirements as per it expected.
Non-Functional Testing: Non-functional Testing is a testing to test the software about its performance, stability etc..,

Here are some of the most common types of testing:

Unit Testing: Unit Testing is a testing to test the individual units or components of a software application. It is done by developers to identify bugs early in the development process.
Performance Testing: This Testing evaluating the software's responsiveness, speed, stability under various conditions.
This type includes subcategories such as:

A.) Load Testing: To Test the software's behavior under expected load conditions.
B.) Stress Testing: To Test the software to its limits to assess how it handles extreme conditions.

Smoke Testing: Smoke Tests means verifying the important features are working and there are no Bugs in the build that is under testing. In software testing process the smoke test determines whether the deployed software build is stable or not. Smoke testing is a confirmation for QA team to proceed with further software testing and Smoke testing is also known as “Build Verification Testing” or “Confidence Testing.”
Sanity Testing: Sanity testing means after receiving a software build, with minor changes in code, or functionality that the bugs have been fixed and no further issues are introduced due to these changes. Sanity testing aims to ensure that specific changes or fixes introduced in a software build have not negatively impacted the existing functionalities.
Regression Testing: Regression testing is a type of software testing that focuses on the recent code changes or updates in a software application do not negatively affect existing functionalities. The primary aim of regression testing is to maintain the overall quality and stability of the software, even as new features or fixes are added. In simple terms, Regression testing is like double-checking that new updates haven't broken the previously working parts of the software.
User Acceptance Testing : UAT is a final phase of testing where real users where evaluate the software application to determine whether it meets their requirements and is ready for actual use. In simple terms, UAT is like giving the software a Trial Run to make sure it works the way users expect it to before it's officially deployed.

Different Types of STLC Phases

STLC is a process used to test the software and confirm that product conditions works are met. Testing is process and also an integral part of Software Development Life Cycle (SDLC). There are 6 phases in STLC

Requirement Analysis: In this phase, the testing team reviews and analyzes the project requirements, specifications, and documentation to understand the scope of testing and the expected behavior of the software.
Test Planning: In this phase, plan is created based on the analysis of requirements. This plan outlines the testing approach, scope, objectives, resources, schedule, and criteria for success.
Test Case Development: Test cases are developed based on the test plan. Test cases outline the specific conditions, inputs, and expected outcomes for testing different aspects of the software.
Test Environment Setup: A suitable testing environment is established, including hardware, software, and network configurations, to simulate real-world conditions for testing.
Test Execution: In this phase, the actual testing takes place. Testers execute the prepared test cases and record the outcomes. Defects and issues are identified, documented, and reported to the development team.
Test Closure: Once testing is complete, a formal closure report is prepared. This report summarizes the testing activities, results, issues, and the overall quality of the software. It also provides a recommendation for the software's release.

As a Manual tester, I have certain qualities that make me good at testing software. Here are some of those qualities..,

I'm Really Good at Paying Attention: I'm really good at noticing even the small things that might be wrong in the software.
I'm Great at Solving Puzzles: I'm good at figuring out why something isn't working correctly and finding solutions to it unexpected challenges that arise during testing.
I'm a Clear Communicator: I can explain things in a way that makes sense to others and I am skilled in documenting also.
I'm Interested In Testing: I possess a strong understanding of the domain or industry for which the software is being developed.
I'm Creative with Ideas: I can come up with different ways to test things that others might not think of and also I am able to think outside the box when it comes to test scenarios and test cases and missed scenarios.
I'm Good at Managing My Time: I can plan my work so that I finish on time. I made a plan, focused on the most important parts, and managed to test everything in time for the release.
I'm a Problem Solver: I'm good at finding ways to fix problems and troubleshooting and finding solutions to unexpected challenges.
I Think about Users: I always think about how the people using the software will feel. I always keep the end-users in mind while testing, aiming to deliver a flawless product.

Agile vs Waterfall – Difference Between Methodologies

Agile:

Small Steps: Work is divided into small parts called "sprints". Each sprints delivers a piece of the software.
Changes Welcome: Changes can be made even after work has started. Flexibility is a big thing here.
Testing Along the Way: Testing is done continuously as each part is built, helping catch issues early.
Quick Deliveries: You get smaller pieces of the software more often, which is good for seeing progress.
Team Collaboration: The team works closely together and communicates a lot. Communication is important.

Waterfall:

Step-by-Step: Waterfall is like building things step by step, like a waterfall flowing down.
Changes are Harder: Changes are tough once you've moved to the next phase. It's like turning back in a one-way street.
Testing at the End: Testing happens after everything is built. Sometimes problems are found too late.
Single Delivery: You get the whole software at the end, which can take a while.
Sequential Teams: Different teams handle different phases, often working separately.