DEV Community: Indhumathi

Selenium Architecture

Indhumathi — Wed, 27 Mar 2024 08:26:23 +0000

The main purpose of automation testing is to minimize the time and effort of testers and generate accurate test results of end user. A tool combined with practical knowledge about the system is used to automate test execution. In an automation testing the automation test engineer, would know about the Selenium, is one tool that you would have used as main tool.

Selenium Client Libraries
These developers have made it possible to support different programming languages of our choice – Java, Python, C#, Ruby, JavaScript, etc.
It allows us to write the Selenium automation scripts to support multiple languages.
It provides an application programming interface (API), that is, a set of functions that performs the Selenium commands from the test script and is not a testing framework.

JSON Wire Protocol
JavaScript Object Notation is a data interchange format based on a subset of the JavaScript Programming Language. It is for storing and transferring data. The JSON wire protocol provides the capability of transferring data between Selenium scripts and browser drivers.
This Json ire Protocol provides support for data structures like arrays and objects, making data reading and writing more comfortable.
The JSON sent requests by the client are altered into HTTP requests format for the server to understand and converted back to JSON format while sending it back to the client Server again. These kind of process of data transfer is called serialization.
In this method, the internal logic of the browser is not disclosed, and the server can communicate with the client libraries, even that is with unfamiliar programming language too.

Browser Drivers
These drivers act as a bridge between the Selenium client libraries and the real browsers. They help us in running commands of selenium on the browser.
It is the main responsible for this driver is to executing user actions, like clicking the mouse, navigating the pages, clicking the button, etc., on the browser.
For every supported browser in the Selenium, have a unique browser driver. These browser drivers take commands from the Selenium test scripts and pass them to the respective browsers.
ChromeDriver, FirefoxDriver, SafariDriver, OperaBrowser, EdgeDriver, and HtmlUnitDriver are Some popular browser drivers in Selenium.

Selenium WebDriver Feature

1.Multi-Browser Compatibility
2.Multiple Language Support
3.Speed & Performance
4.Community Support
5.Open Source & Portable
6.Work On Different OS
7.Add-ons & Reusability
8.Simple Commands
9.Reduced test Execution time
10.No Server installation

Conclusion
The JSON Wire protocol over HTTP was the primarily used mode of communication between the Selenium client libraries and the browser driver in Selenium 3.0.

This protocol was replaced with the new WebDriver W3C (World Wide Web Consortium) protocol with the introduction of Selenium 4.0
This will be less unreliable and more stable With WebDriver W3C Protocol. Stability in this is a major reason to shift to Selenium 4.0

SIGNIFICANCE OF PHYTHON VIRTUAL ENVIRONMENT
Python Virtual Environment
A Python Virtual Environment is a powerful tool for managing dependencies and creating isolated spaces for your Python projects. Let’s delve into its significance:

1.Isolation and Independence:
A virtual environment provides an isolated space where you can work on your Python projects separately from your system-installed Python.
You can set up your own libraries and dependencies without affecting the system-wide Python installation.
Each virtual environment acts as a sandbox, allowing you to keep project-specific packages separate.

2.Scenario-Based Use Cases:
Imagine you’re simultaneously working on two web-based Python projects:
Project A uses Django 4.0.
Project B uses Django 4.1.
Without virtual environments, both projects would share the same directories for storing and retrieving third-party libraries.
This creates a problem because Python can’t differentiate between different versions of the same package in the system-wide “site-packages” directory.

Virtual environments come to the rescue:
Each environment contains its own set of dependencies, ensuring that Project A and Project B remain independent.

3.Creating a Virtual Environment:
To create a virtual environment, you can use the virtualenv tool.

Install it using:
$ pip install virtualenv

Test your installation:
$ virtualenv --version

Create a new virtual environment:
$ virtualenv my_env

Deactivate Python Virtual Environment
(virtualenv_name)$ deactivate

This command creates a directory named my_env containing all the necessary executables for your Python project.
You can also specify a specific Python interpreter (e.g., Python 3) when creating the environment:
$ virtualenv -p /usr/bin/python3 virtualenv_name

4.Benefits
Dependency Isolation: Each project has its own isolated environment, preventing conflicts.

Precise Dependency Management: Install specific versions of packages for each project.

Collaboration: Share your project with others, ensuring consistent environments.

Safe Experimentation: Test new packages without affecting other projects.

SIGNIFICANCE OF PHYTHON VIRTUAL ENVIRONMENT

Indhumathi — Wed, 27 Mar 2024 08:25:49 +0000

Python Virtual Environment
A Python Virtual Environment is a powerful tool for managing dependencies and creating isolated spaces for your Python projects. Let’s delve into its significance:

Virtual environments come to the rescue:
Each environment contains its own set of dependencies, ensuring that Project A and Project B remain independent.

3.Creating a Virtual Environment:
To create a virtual environment, you can use the virtualenv tool.

Install it using:
$ pip install virtualenv

Test your installation:
$ virtualenv --version

Create a new virtual environment:
$ virtualenv my_env

Deactivate Python Virtual Environment
(virtualenv_name)$ deactivate

4.Benefits
Dependency Isolation: Each project has its own isolated environment, preventing conflicts.

Precise Dependency Management: Install specific versions of packages for each project.

Collaboration: Share your project with others, ensuring consistent environments.

Safe Experimentation: Test new packages without affecting other projects.

WHAT IS SELENIUM ? WHY DO WE USE FOR AUTOMATION?

Indhumathi — Tue, 19 Mar 2024 09:55:37 +0000

Selenium
Selenium is most renowned open-source test automation frameworks. It is powerful tool for controlling web browsers through programs. It is simpler to test web applications for performance, compatibility, and usefulness.

It is compatibility with programming languages like Java, Python, C#, Ruby, and etc to create Selenium Test Scripts. Developers and Testers can use Selenium’s features in the programming environment of their choice and in the language.

Selenium is functional for all browsers, works on all major OS, and its scripts are written in various languages.

Selenium Tool Suite
Selenium Integrated Development Environment (IDE)
Selenium Remote Control (RC)
WebDriver
Selenium Grid

Selenium IDE
It enables testers to develop test cases without having to have a deep understanding of programming. This IDE provides a straightforward, user-friendly user interface for adding and updating test cases.

Selenium IDE implemented as a Firefox Add-On and as a Chrome Extension.

This was previously known as Selenium Recorder.
This provides commands for performing actions in a browser and for retrieving data from the resulting pages.

Selenium RC (Remote control)
The first automated web testing tool that allows users to use a programming language they prefer. It can support the following programming languages:
C#
Java
PHP
Python
Perl
Ruby

WebDriver
It is the often-used tool in the Selenium suite. It uses native OS level functionality rather than browser-based JavaScript commands to drive the browser. This WebDriver does not need a special server to execute tests. It implements a more modern and stable approach in automation.

Selenium GRID
It is a tool used together with Selenium Remote Control to run parallel tests across different machines and different browsers all at the same time. Running multiple tests at once is called as Parallel execution.
Selenium GRID Saves time enormously. This must be perfect for organizations with oversized test suites. This Selenium Grid allows testers to spread test cases and execute them in parallel.

Selenium GRID is needed when run a huge test suite, that needs to complete in the soonest time possible.

Using Selenium for Automated Testing

1. Language and Framework Support
Selenium supports all major languages like Java, Python, JavaScript, C#, Ruby, and Perl programming languages for software test automation. Selenium converts any programming languages it into Selenium compatible codes in no time.

2. Open-Source Availability
The Main advantages of Selenium it is open-source availability. It helps the developers and software engineers in automating the web browser features and functionalities.

3. Multi-Browser Support
Selenium script is compatible with most used browsers in worldwide so no need to rewrite scripts for every browser, just one script for all browsers.

4. Support Across Various Operating Systems
It is necessary that your automation tool supports all different operating systems like Windows, Linux, Mac OS, UNIX, etc. Selenium test suites over any platform.

5. Ease Of Implementation
It is very easy-to-use tool. It provides a user-friendly interface, so it helps to create and execute test scripts easily and effectively.

6. Reusability and Integrations
As we mentioned above that the test suites can be tested across multiple browsers and operating systems are reusable.

7. Flexibility
Selenium features like regrouping and refactoring of test cases becomes easier and more efficient so it helps developers and testers in quick changes to the code improving maintainability, minimizing complications, these features make Selenium more flexible and usable as compared to other automation testing tools.

8. Parallel Test Execution and Faster Go-to-Market
The main purpose of automated testing is to save time and efforts, With the help of Selenium Grid, we can execute multiple tests in parallel to save time.

9. Less Hardware Usage
Selenium requires less hardware as compared to other testing tools like QTP, UFT, SilkTest.

10. Easy to Learn and Use
Selenium scripts are easy to learn it is not writing like hundred-page complex algorithm.
11. Constant Updates
Selenium community is constantly releasing constant upgrades are readily available and easy to understand. Compared to other tools it is cost-effective as well.

TASK 4 - MANUAL TESTING

Indhumathi — Sun, 24 Dec 2023 11:38:30 +0000

MANUAL TESTING
As the name itself suggests, this testing is the one in which application testing happens manually. The test cases are executed one by one by Testers manually without using any readymade tools, and then the results are verified.

In this software testing, a tester carries out tests on the software by following a set of predefined test cases. Testers make test cases for the codes, test the software, and give the final report about that software to meets its user requirements.

The tester has to makes sure that reported defects are fixed by developers and re-testing has been performed by testers on the fixed defects.
The manual testing verification is the most primitive form of software testing. Any new or updated applications must be tested manually before automation testing.

Need of Manual Testing

With the changing trends in the software field, more and more software professionals prefer automated testing, but there are still multiple reasons which justify the need for manual testing. Few of them are:

The main goal of this testing is to ensure that the application is bug-free, stable, in conformance with the requirements and delivers a stable product to the end users.
It helps the test engineers get more familiar with the product and get an end-user perspective. This helps them to write correct test cases for the software application.
Manual testing helps to verifies that the defects are fixed by the developer and that retesting has been done on the fixed defects.

Requirement Analysis
Tester has to study the software project documentation, guides, and Application Under Test (AUT). Analyse the requirements thoroughly from SRS.
The Tester identifies test conditions, to check the basis of the test where tests basis is the crucial info on which test cases are based, like architecture, requirements, design specifications, product risk analysis, and interfaces.
The tester has to plan the tests.
To design the test environment set-up and determine the required tools and infrastructure.

Test Plan Creation
Tester has to Create a test plan covering all the requirements of the end user.
These test cases help us follow a sequence to test functionality and various test scenarios such that we cover the entire application and check expected results.

Test Case Creation
Tester has to design the test cases that cover all the requirements described in the documentation.
After the analyses the necessities, now time to develop and hierarchize test cases by using methods and creating test data for those testing.
Test cases function as reference guides for QA engineers, laying out as well as steps to test the distinct scenarios and functions within the software application.

Test Case Execution
After the test case Review and baseline the test cases with the team lead and client. Then Execute the test cases on the application under test.

Defect Logging
To Detect the bugs, log and report them to the developers is the primary thing in this stage.
In this procedure to identify defects in the software under test or product by testing or keeping records from customers and making advanced versions of the product that mitigate and fix the flaws.

Defect Fix and Re-verification
In this stage bugs are fixed, again execute the failing test cases to verify that they pass or not.

The software developer makes changes in code alterations and verifies the modifications then he/she can build bug status as ‘Fixed’ and the bug issues are shifted to QA manual testing team.

At this phase, the tester performs the further certification and testing of the altered code.

TYPES OF MANUAL TESTING
There are so many different methods to implement manual testing, but it is mainly classified into three types of manual testing

Black Box Testing
It is the type of testing where the tester testing the functions without the knowledge of about any internal structure or logical or code implementation. This test simply checks the inputs and user expected output it meets the requirements or not. This testing focus on user perspective only.

White Box Testing
It is the testing where the tester must have full knowledge of internal functions or structure, and logically it performs or not. In this testing user has to know code and implementation. It is completely developers' perspective only. It is also called as clear box or glass box.

Grey Box Testing
It is the testing that combines both black box testing and white box testing. This testing performs from both developer point of view and user point of view. In this testing we have some knowledge of how it works internally.

Tools Used for Manual Testing

Test Link
Web-based test management system that facilitates software QA.
The most user-friendly programs.
Available through a browser with good internet connection.
Supports cross-browser testing across different platform.

Bugzilla
Web-based bug-tracking tool that is developed by Mozilla.
This has simple bug search that it searches the complete text of the bug.
Supports various OS like Windows,Linux,Mac etc.,
It has the Facility to list the software bug in different format.
This has advance searching facility.

Jira
This is the Manual testing tool that helps the teams to assign, track, report, and manage work and bring the teams together.
This tool is one which is compatible with agile software projects also.
It has the Option to track and manage the bugs and defects in the software application.
This will Prioritize and assign tasks.
Collaborate with team members is possible.
In this we can Easily generate reports and track progress.

LoadRunner
Most widely used performance testing tools.
The purpose of this tool is to categorize the most prevalent causes of performance problems.

Simulates real-world user behaviour and load.
Identifies bottlenecks and performance issues.
Scalable architecture for large-scale testing.
Provides detailed reports and analysis.

Apache JMeter
It has Open-source load testing tool for analysing and measuring the performance of a variety of services in software application. It has an easy-to-use user interface.
Simulates various types of loads (web, database, etc.).
Highly configurable and extensible.
Integrates with various plugins for additional features.
Provides comprehensive performance reports and graphs.

ADVANTAGES AND DISADVANTAGES OF MANUAL TESTING

ADVANTAGES

Fast and accurate visual feedback
Less expensive
No coding is required.
It is suitable in case of unplanned changes to the application, as it can be adopted easily. so, its Efficient for unplanned changes
It uses black box testing, so don’t need programming knowledge.
Easy for new testers to learn.
The tester interacts with the apps as a real user, to spot usability and user interface issues.

DISADVANTAGES

It is less reliable as it does not provide testing on all aspects of testing.
It comparatively large number of human resources needed.
Testers cannot use a given test case again so cannot be reused.
Testers need to develop separate test cases for each new
application for the software.
In this tester develops test cases based on their skills and previous experiences. So, there is no proof that they have covered, all functions in the software applications.
If the project is large, then this type of testing process is time-consuming.

EXAMPLE:
LOGIN WEB PAGE

The user provides the correct username and password the user will be redirected to the homepage. If the user input is wrong, an error message will be displayed.

Test Case 1 – Username and password both were wrong. It shows an error message.
Test Case 2 – Username was correct, but the password was wrong. It shows an error message.
Test Case 3 – Username was wrong, but the password was correct. It shows an error message.
Test Case 4 – Username and password both were correct, and the user navigated to the homepage.

Mobile Banking Test Cases
Banking applications allow the users to experience financial services that banks offer more easily for the end user.
Test the installation and setup of the mobile banking app.
Verify the compatibility with different mobile device types (iOS, Android).

Test the installation process and setup functions of the mobile banking app.
Verify it works with different mobile device types like iOS, Android.
Test the responsiveness of the app function on various screen sizes and resolutions.
Verify that mobile check deposit functions working correctly.
Test mobile bill payment and funds transfer process in a right manner.
Verify the accuracy of notifications and alerts.
Testing the offline functionality, such as viewing account balances without an internet connection is possible or not.
Verify the ability to check between multiple user accounts.
Test the mobile app's synchronization with the web-based banking platform.
Verify that the app is accessible to all type of users with disabilities (ADA compliance).
Test the performance of the mobile app under low-network conditions.
Verify that biometric authentication works securely e.g., fingerprint, face ID works securely.
Test mobile app updates and their impact on existing data.
Verify that the mobile app supports various language preferences and localization.
Test mobile app-specific features like remote account deactivation is available or not.
Verify that mobile app data is protected against device theft or loss.
Test the mobile app's ability to generate and scan QR codes for transactions.
Verify the handling of interruptions (e.g., phone calls) during app use.
Test the mobile app's accessibility on both smartphones and tablets.
Verify the integration of mobile app analytics for performance monitoring.

TASK 3 - FUNCTIONAL AND NON-FUNCTIONAL TESTING

Indhumathi — Mon, 18 Dec 2023 13:00:15 +0000

FUNCTIONAL TESTING
It is a type of software testing which verifies that each function of the software application tested against the functional requirements and specifications. Functional testing mainly involves black box testing, and it is not concerned about the source code of the software application.
Every functionality of the system is undergoing testing by providing appropriate input, verifying the output and comparing the actual results with the expected results. In this type of testing can be done manually.

Functional testing is particularly concerned with the result of processing. It is performed before the non-functional testing.
It verifies the operations and actions of an application than the behaviour of an application.

Examples of Functional Testing Types

Unit testing
It is a type of software testing that focuses on individual units or componentsof a software system. The purpose of this testing is to validate each unit of the software works as properly and meets the user requirements.

Smoke testing
This testing method that determines whether the employed build is stable or not. It acts as a confirmation of whether the quality assurance team can proceed the next step of testing. This testing is important in software development as it ensures the correctness of the system in initial stages.
This Testing also called as Confidence Testing or Build Verification Testing.
It carried out by quality assurance engineers. Smoke testing measure the stability of the software product by performing testing.

Integration Testing
In this testing where interaction between two or more different components within the software.
Multiple Components need to be tested together.
In this software modules are integrated logically and tested as a group.
The need of this level of testing is to find out defects in the interaction between these software modules when they are integrated.
This focuses on checking data communication among these modules. Hence it is also called as ‘String Testing’ and sometimes ‘Thread Testing’.

Interface Testing
This software testing that focuses on verifying the interaction between different components, modules, or systems.
It integrates the connection of two components is called interface. This interface in a computer may be anything like API’s, web services, etc.

Regression Testing
It ensures that new code changes in the software do not cause any effects on the existing functionalities. The previous code still works once the latest code changes are modified.
For example, we make a little change to the source code for any reason like adding new functionality, optimization, etc. then our program may fail in the previously designed test suite for obvious reasons.

User Acceptance
It is performed by the end user or the client to verify the software system before moving the software to the business environment. These are done in the final phase of testing after functional, integration and system testing are done.
This is also called as End-User Testing.

NON-FUNCTIONAL TESTING

It is type of Software testing to check non-functional aspects software application. It is designed to test the accessibility of a system as per nonfunctional parameters which are never addressed by functional testing.
Non-functional testing involves evaluating a system's performance, reliability, usability, efficiency, maintainability, and scalability.

Each software application has its own functionality. For Example, we can't expect a food delivery app to deliver your favourite dishes when you click on “Order food.” The role of a n*on-functional tester is to test if you can easily the user navigate to the “Order food” button*. They must also test if more than the ‘n’ number of users could place an order simultaneously from any browser/OS/device configuration it gives the results in a efficient time.

Documentation Testing
It is a type of software testing that involves testing the documented test cases developed before or during the testing process begins. Like a user manual all the sequence of steps are documented clearly.
It requires** Test Case document, Test description, Test case report, Test logs**.

After the testing completed, the test summary remains which is a collective analysis of all test reports.

Installation Testing
It is a type of software testing that verifies the installation process of software and verify that the software is installed correctly on various systems and configurations.
This process helps to ensure that the software can be easily installed, configured, and uninstalled without any issues.

The main goal of installation testing is to verify that the software installation correctly on different operating systems, hardware, and software configurations to ensure that it can be installed and configured correctly, and that the software’s functionality is not compromised during in the installation process.

Performance Testing
It is a type of software testing that verifies software applications perform properly under their expected workload. This testing technique carried out to determine system performance in terms of speed, responsiveness, stability and scalability of a software application.

The goal of performance testing is to measure system performance under various loads and conditions and ensure that the system can handle the expected number of users or transactions.

Load Testing
This test ensures the real-world load on the system to see how it performs under stress. It helps to determine the maximum number of users or transactions the system can handle.

Stress Testing
It is a type of load testing that tests any potential issues that may occur under heavy load conditions. Stress testing helps to identify the breaking point of the system and ability to handle a high load.

Scalability Testing
It is a type of testing to ensures how the application scales with increasing workload and to measure at what point the software product or the system stops scaling and identify the reason behind it.
Example - Testing of a web page depends on the number of users, usage of CPU, network usage while scalability testing of a web server depends on the number of requests processed.

Reliability Testing
It is a type of software testing that ensures the ability of a system to perform its intended function consistently and without failure over an extended period of time.
The need of reliability testing is to identify and address issues that which situation can cause the system to fail or to become unavailable like Data crashes.

Security Testing
It is a type of software testing that mainly focuses on evaluating the security of a system or application. The need of security testing is to identify vulnerabilities and potential threats and to ensure that the system is protected against unauthorized access, data breaches, and other security-related issues.
It determines that the software system and application are free from any threats or risks that can cause a loss.

Differences between Functional and Non-functional Testing

Key Difference Between Functional Testing and Non-Functional Testing

Functional testing verifies each function whereas Non-Functional testing verifies non-functional aspects like performance, usability, reliability, etc.

Functional testing can be done manually whereas Non-Functional testing is hard to perform manually.

Functional testing is based on User’s requirements whereas Non-Functional testing is based on User’s expectations.

Functional testing has a goal to validate software actions whereas Non-Functional testing has a goal to validate the performance of the software.

The Functional Testing example is to check the login functionality whereas a Non-Functional testing example is to check the dashboard should load in 2 seconds.

Functional testing is performed before the non-functional testing.

TASK 2 -TESTING TECHNIQUES

Indhumathi — Sun, 17 Dec 2023 13:25:51 +0000

BOUNDARY VALUE ANALYSIS
Boundary testing is the process of testing between boundaries or extreme ends between partitions of the input values. So these extreme ends like Maximum-Minimum, Lower- Upper, Start- End, Just Inside-Just Outside values are called boundary values and the testing is called “boundary testing”.

Boundary testing is the type of black box testing

Based on this testing the boundary values of valid and invalid partitions. In this Testing Behaviour at the edge of the equivalence partition is more likely to be incorrect than the behaviour within the partition, so boundaries are an area where testing is likely to yield defects.

Equivalence Class Partitioning plays a good role in the boundary testing. It is type of black box testing technique which can be applied to all levels of software testing like unit, integration, system, etc. In this technique, input data units are divided into equivalent partitions that can be used to derive test cases which reduces time required for testing because of small number of test cases.

Equivalence Partitioning or Equivalence Class Partitioning divides the input data of software into different equivalence data classes, where there is a range in the input field.

The boundary value for a valid partition is consider as valid boundary value.
The boundary value for an invalid partition is considered as invalid boundary value.
For each variable we check- Minimum value, just above the minimum, Nominal Value, just below Max value, Max value.

Example 1: Consider a system that accepts ages from 18 to 58.
Boundary Value Analysis (Age accepts 18 to 58)

Invalid = (min - 1)

Valid= (min, min + 1, nominal, max – 1, max)

Invalid= (max + 1)

Valid Test cases: Valid test cases for this below example might be any value entered greater than 18 and less than 58.

Invalid Testcases: When any value less than 18 and greater than 58 is entered.

If We Take (17,18,19,37,55,58,59)

If we Enter the value - 18
If we Enter the value - 19
If we Enter the value - 37
If we Enter the value - 55
If we Enter the value - 58

The above are all Valid test cases

If we Enter the value - 17
If we Enter the value - 59
The above are all Invalid test cases
Example 2 Below is the example to combine Boundary Value and Equivalence Partitioning.

Consider a field that accepts a minimum of 8 characters and a maximum of 12 characters. Then the partition of the test cases ranges 0 – 7, 8 – 12, 13 – 18.
Enter value 0 to 7 character - Not accepted.
Enter 8 to 12 character - Accepted.
Enter 13 to 18 character - Not accepted.

DECISION TABLE TESTING
Decision table testing is a type of software testing technique where the testers has used to test system behaviour for different input combinations. This testing includes type of Black Box Testing.
In this where the different input combinations and their corresponding system behaviour (Output) are captured in a tabular form. The output may be dependent on many input conditions, decision tables give a tabular view of various combinations of input conditions and these conditions are in the form of True(T) and False(F).That is why it is also called as a Cause-Effect table where Cause and effects are captured for better test coverage.

This technique is an effective tool used for both complex software testing and requirements management. It helps to check all possible combinations of conditions for testing and the testers can also identify missed conditions easily.
Example: Decision Base Table for Login Screen

The user provides the correct username and password the user will be redirected to the homepage. If the user input is wrong, an error message will be displayed.

Test Case 1 - Upload a photo with format ‘.jpg’, size less than 50kb and resolution 250*250 and click on upload. The result is Photo should upload successfully.

Test Case 2 - User Upload a photo with format ‘.jpg’, size less than 50kb and resolution not 250*250 and click on upload. The result is Error message must be displayed.

Test Case 3- User Upload a photo with format ‘.jpg’, size more than 50kb and resolution 250*250 and click on upload. The result is Error message size mismatch should be displayed.

Test Case 4 - User Upload a photo with format ‘.jpg’, size more than equal to 50kb and resolution not 250*250 and click on upload. The result is Error message size and resolution mismatch might be displayed.

Test Case 5 - User Upload a photo with format other than ‘.jpg’, size less than 50kb and resolution 250*250 and click on upload. The result is Error message for format mismatch must be displayed.

Test Case 6 - User Upload a photo with format other than ‘.jpg’, size less than 50kb and resolution not 250*250 and click on upload. The result is Error message format and resolution mismatch should be displayed.

Test Case 7 - User Upload a photo with format other than ‘.jpg’, size more than 50kb and resolution 250*250 and click on upload. The result is Error message for format and size mismatch must be displayed.

Test Case 8 - User Upload a photo with format other than ‘.jpg’, size more than 50kb and resolution not 250*250 and click on upload. The result is Error message for format, size and resolution mismatch must be displayed.

USE CASE TESTING
Use Case Testing is a part of black box testing, and it helps the developers and testers to identify test scenarios that exercise the whole system on each transaction basis from start to finish.
Use case testing helps to identify the gaps in software that might not be identified by testing individual component and helps to identify the gaps in software that might not be identified by testing individual components.
It is a type of end-to-end testing it won’t ensure the entire coverage of the user application and it will find out the defects in integration testing.
Example: In this a person is represented by “P” and system by “S”. We create Use for a login functionality of a Web Application as displayed below.

The Person enters email and password and the next step, the system will validate the password.
If the password is correct, then the access will be granted.
If in case password is not valid system will display a message and ask for re-try three times.
If Password, not valid three times system will ban the IP address.

Linear code sequence and jump
It is a white box testing technique to identify the code coverage, which begins at the start of the program and ends at the end of the program.
It is also called JJ-path, standing for jump-to-jump path.
LCSAJ means 100% Statement Coverage, Branch Coverage, procedure or Function call Coverage, Multiple condition Coverage.

Example: checking the Age Eligibility to Vote

Input age of the person and check whether a person is eligible or not.

Eligible - Age >= 18
Not Eligible - Age < 18

Check the condition, whether age is greater than or equal to
18, will be eligible for the voting.

If it is less than 18 the person will not be eligible for the voting.

TASK 1-SOFTWARE TESTING

Indhumathi — Tue, 12 Dec 2023 11:21:44 +0000

Software Testing
Software Testing Is the Process of Identifying Defects in The Software and Eliminate the Bugs to Meet the End User Requirements with High Quality.

Need To Know About Software Testing
The Need of Software Testing Is to Verify,Identify and Fixing the Issues Earlier in the Development Process in Order To reducing the cost And Effort of Fixing Them Later. So, Its Time Saver and Cost Effective. It Also Reduces the Risk in The Software.

Types Of Software Testing
1. Manual Testing
2. Automation Testing

Manual Testing
In Manual Testing, Humans Involves in The Process to Fix the Issues in The Software before the Automation Testing. This Testing does not require Any Automation Tools. It makes the user to get full knowledge about the Needs of The End Of the user. It Identify The bugs in the Earlier stages itself.

Stages Of Manual Testing
Unit Testing
Integration Testing
System Testing
UI Testing
Acceptance Testing

Unit Testing
It is the testing where individual components or functions have to tested separately. Example: In Calculator we have to test addition, subtraction, division, multiplication individually whether it performs in a right way and give output Correctly.

Integration Testing
It is the testing where number of units are integrated and then tested. Like two components or two functions are tested as a whole. Its the next step of unit testing.

System Testing
It is the testing where all integrated components or functions tested as a whole. Like We Said in The Example of Calculator In unit testing, here it is tested as whole function in the calculator.

UI Testing
It is the testing involves visual elements of the software. UI Testing Checks the Graphical Interface Like fonts, menu, colors, checkboxes and more.

Acceptance Testing
Acceptance Testing ensures that to meet the business requirements of the user and also evaluate the product satisfy the user standards. It is the last stage to identify the bugs before releasing the product.

Types Of Manual Testing
Black Box Testing
White Box Testing
Grey Box Testing

Automation Testing
In Automation Testing, it uses some specific software to test the functions. Many Cases we have to check N number of thing at a time so in these humans has not able to process it all at a time. so, automation testing needed at this time. So, it's Really a Time Saver. But Picking a Right Automation Tools Is Mandatory.