DEV Community: Priyadharsini RK

Python Selenium Architecture and Virtual environment with example commands

Priyadharsini RK — Thu, 07 Mar 2024 20:46:14 +0000

Selenium Architecture:
Selenium is a powerful tool for controlling web browser through program. It is functional for all browsers, works on all major OS and its scripts are written in various languages i.e Python, Java, C#, etc, we will be working with Python. Selenium has four major components – Selenium IDE, Selenium RC, Selenium Web driver, Selenium GRID.
The architecture of Selenium is composed of:
Selenium IDE
1.IDE - Integrated Development Environment
It is just a web-browser extension that you need to download and install the extension for that particular web browser and start working with it.
One of the major advantages of using Selenium IDE is that it can automate and record the entire automation process as well
People generally do not use IDE, they rather prefer selenium scripts in order to do the same job.

2.Selenium Remote Control
It is an outdated and deprecated technology. We do not use it these days.
It has been replaced with WebDriver which is far more better and easy to use.

3.Selenium WebDriver:
• It is the most important and major component of selenium architecture.
• It provides a programming interface between the language and the web-browser.
• It is composed of:
a.Selenium Client Library:
• It consists of language bindings or commands which you will be using to write in your automation scripts.
• They are compatible with W3C protocols like HTTP, HTTPS, TCP, UDP etc
• They are the wrappers which send the script commands to the network, for the execution into the web-browser.

b.Selenium API
• It contains a set of rules and regulation which your Programming language (Python) used to communicate with the Selenium
• It helps in automation without the need for the user to understand what is happening in the background.

c.JSON wire protocol:
• The commands that you write are converted into JSON which is then transmitted across the network or to your web-browser so that it can be executed.
• The JSON data are sent to the client using the HTTP protocol
• It is used by the browsers also,

d.Browser Drivers:
• It acts as a bridge between the Selenium Script, Libraries and the browser.
• It helps us to run the selenium commands on the web browser.
• https://github.com/mozilla/geckodriver/releases/tag/v0.34.0

Browser:
• All the web browser.

4.Selenium Grid:
• It is used to run parallel test on multiple devices running same or different browsers and we could also simulate at different geographical locations.
• We can run multiple test-cases simultaneously at the same time.
• It uses the master-slave architecture.

Virtual Environment:
• It is a tool which helps python Developers and testers to keep project dependencies and modules which are required for different projects separate and independent from each other.
• With this we can manage our projects and their dependencies far more easily and efficiently.
• This allows us to have multiple independent python environments on the same system without them interfering with each other.

Uses of Virtual Environments:

Isolation
Dependency Management

How to create virtual environments in Python,

virtualenv:

Install the virtualenv package:

pip install virtualenv

Create the python virtual environment:

virtualenv

b. Select the virtual environment:

Click ctrl + shift + p and select Python: Select Interpreter

c. Select your environment which you have created now

Other way of using pipenv using terminal:

Create the Virtual Environment by:

pipenv - -python 3.12

Install the packages

pipenv install selenium

pipenv install webdriver_manager

Run the python file

pipenv run python main.py

What is Selenium and why do we use it for Automation

Priyadharsini RK — Tue, 05 Mar 2024 19:34:54 +0000

What is Selenium and why do we use it for Automation:

Selenium:

Selenium is an automation framework and open source software(o need to pay or owned licensed to download this software from https://www.selenium.dev/ website.

• It is created by Jasson Huggins in 2004. It was written in pure Java.
• Selenium can be used with various other programming languages like Python, JavaScript, C#, Java, PHP and so on.
• With selenium we can validate or verify the web applications.
• Selenium is predominantly used in Automation Testing

Automation:

• Automation is a technology that is used to perform certain tasks with minimum or no human interactions or interference or efforts.

• It could run the tests directly on the target browser, drive the interactions on the required web page and rerun them without any manual input. It eliminates repetitive manual testing that consumes lots of time and effort.

• Selenium is an open-source software of tools and libraries that is used for browser automation.

• It allows users to test their websites functionally on different browsers like Microsoft edge, google chrome, firefox, Opera, etc.,
•
Perform Cross browser testing to check if the website functions consistently across different browsers.

• Can be used to multiple operating system like windows, mac, linux /unix

Advantages of Using Selenium for automation testing:

1.Language and Framework Support :
Selenium as it supports all major languages like Java, Python, JavaScript, C#, Ruby, and Perl programming languages for software test automation.
You can write your scripts in any of these programming languages and Selenium converts it into Selenium compatible codes in no time
2.Open Source availability:
Selenium is a publicly accessible automation framework and is free, with no upfront costs. So, being open source also helps you customize the code for better code management and enhance the functionality of predefined functions and classes. Selenium has become the most reliable web automation tool because of the ease of generating test scripts to validate functionality.
3.Multi browser Support:
“One Selenium script for all browsers” is what the Selenium community has been working on and improvising every day. No need to rewrite scripts for every browser, just one script for all browsers.
4.Support across various operating system:
Selenium is yet a highly portable tool that supports and can work across different operating systems like Windows, Linux, Mac OS, UNIX, etc, can create Selenium test suites over any platform .
5.Ease of Implementation:
This framework is very easy-to-use tool. Selenium provides a user-friendly interface that helps create and execute test scripts easily and effectively. You can also watch while tests are running. You can analyze detailed reports of Selenium tests and take follow-up actions.
6.Reusability:
Selenium is not an all-inclusive web automation testing tool. Hence, it needs third-party frameworks and add-ons to broaden the scope of testing.
For example, we need to integrate Selenium with TestNG and JUnit for managing test cases and generating reports.
7.Flexibility:
Selenium features like regrouping and refactoring of test cases. This helps developers and testers in quick changes to the code, reducing duplication, minimizing complications and improving maintainability.
8.Parallel Tests execution:
With the help of Selenium Grid, we can execute multiple tests in parallel, hence reducing the test execution time. And With the help of cloud-grids for cross-browser testing you can test across as many as hundreds of browsers in parallel using Selenium.
9.Less Hardware Usage:
If you compare Selenium with other vendor focused automation tools like QTP, UFT, SilkTest, you will find that Selenium requires less hardware as compared to other testing tools.
10.Easy to Learn and Use:
Selenium scripts are not something like writing hundred-page complex algorithm. Writing Selenium scripts is not more than writing a few pieces of codes to automate functionalities of our website.

Manual Testing -Benefits and Drawbacks with example

Priyadharsini RK — Sun, 10 Dec 2023 16:13:49 +0000

Manual Testing:

Manual testing is a software testing process which will done by testers manually without any code or tool to test the applications.
Test cases should design for the given requirements. Test cases contains step by step instruction to proceed with the flow.
All test cases will be executed manually and Testers has to compare Expected vs actual results to ensure application working as expected.
If testers finds any discrepancy from the requirements and application then it should logged as defect and assigns to developers whose worked on that module.
Once developers analyzed the issue and fixing from their end then inform to testers to retest the issue.
Testers will retest the issue if issues resolves then defect wil
l be closed else it will again back to developers queue.

Example - Login page

Above screen requirements,

User name and password is a mandatory field
If both username and password is correct then login will happen
If user doesn’t register can signup

Login Scenario:

o Without providing username password and click Login button should throw error message display.
o Input wrong username and click Login button should throw error message display.
o Input wrong password and click Login button should throw error message display.
o If user input registered username and password and click Login button should redirect to Home screen.
o Clicking on SignUp button should redirect to registration

Benefits:
• Easy to find every defects from the application
• No coding knowledge is needed to test
• Compared to automation testing it is less expensive
• Suitable when unplanned code change or deployment happen

Drawback:

• It is not reliable because testers cannot cover all the aspects of the testing, Since Exhaustive testing is not possible
• Need human intervention to test for all testing
• Testers should have functional knowledge and experience in testing
• Time consuming process

Functional Testing and Non-Functional Testing Types with example

Priyadharsini RK — Tue, 28 Nov 2023 16:12:47 +0000

Functional Testing:
It is a one of the software testing type and test against with functional requirements and specifications. While testing it should satisfy the functional requirements or specifications. It will verify each and every functionalities of the software application. This testing not involved source code of application. Each functionality of the software application with test input ,actual output, expected output. Post testing compares the actual result with expected output .
Some types of functional testing,
• Unit Testing
• Integration Testing
• System Testing
• Regression Testing
• Sanity Testing
• Smoke Testing
• User acceptance Testing(UAT)
Unit Testing:
Unit testing is done by development side .Developers will run each code program/block and test the code. Once test passed then code will pushed into codebase.
Eg: Testing only Registration page of an application which is working or not.
Integration Testing:
Integration testing also done by development side. Tested unit tests must be integrated with code and test the functionality of the integration test code. Once test passed then code will pushed into codebase.
Eg: Testing registration page along with Login Page of an application both the functionality should work.
System Testing:
System Testing will be done for complete application once all flows are tested End to End. It should satisfied all requirements of the software application.
Eg: Testing the application from login, search product, addToCart, placeOrder along with payment screen ,orderConfirmation mail also should verify and working as expected

Regression Testing:
For every release of a project, we may expect bug when integrate existing functionalities with new functionalities so need to test the new functionalities along with existing by Testers.
For Eg: Whatsapp app now came with sharing functionality, need to test whole application (existing functionality)along with new functionality.
Sanity Testing:
Sanity testing will happen when build is released to check the stability. It is similar to regression testing, but it doesn’t check all the functionalities instead check affected part.
Eg: At first we need to test basics of new functionality(whatsapp channels feature) then need to check that new functionalities should not affect existing functionality(Update functionality).
Smoke Testing:
Once build is completed then Testers will pick critical functionalities and test it. This is the last stage of testing phase post this software will go to User hands.
Eg: E-commerce website, user should able to login and launch application. Once products are picked and add to cart then it should redirect to payment page with payment options.
User Acceptance testing:
This testing will be done by User community, user will test the functionalities and should approve it. Once user provide “Signed Off” the application then only it will go in to Live System.
Non- Functional Testing:
Non-functional Testing will be test the properties of the application
There are many types of non-functional tests:
• Performance testing
• Load testing
• Usability testing
• Security testing
Performance Testing:
Performance testing will test the performance level of the application, loading speed, system crash rate and latency time.
Eg: While launching E-commerce application, check the response time, CPU and memory usage of the website.
Load Testing:
Load testing will check load of the application at same time.
Eg: when many students logging into Exam result portal application at result time .
Usability Testing:
Usability testing will be done by real users. Users will test and complete any of the task/flow of the application.
Eg: Before releasing banking application, professional/experienced people will test it and confirm the testing status.
Security Testing:
Security testing will check with software’s weakness, vulnerabilities and should not be easy to hack or attack the software application.
Eg: Banking application
• URL should be with https by the way share data securely to application.
• password, pin are should be encrypted then stored in the database
• Invalid user id/password should not accept

Type of Testing Techniques with example

Priyadharsini RK — Sun, 26 Nov 2023 11:34:31 +0000

Testing Techniques:

         Software Testing Techniques help to design test cases and also helps to cover requirements, Since exhaustive testing is impossible.  Its has different types of techniques which help to align and fulfil the test conditions. It helps to avoid increasing testcase in further.

1.Boundary value analysis –
Boundary value analysis is based on testing at the boundaries between partitions. It includes maximum, minimum, inside or outside boundaries, typical values and error values.
For Example,
A Textbox will accepts age in numbers from 18 to 56,
Age
Testcases to cover boundary value analysis,
1.To verify if Minimum Value input is accepting or not - 18
2.To verify if Maximum Value input is acceting or not – 56

To verify if Minimum-1 Value input is acceting or not – 17
To verify if Minimum+1 Value input is acceting or not – 19
To verify if Maximum+1 Value input is acceting or not – 57
To verify if Maximum-1 Value input is acceting or not – 55

2.Decision Table –
-A decision table is also known as to Cause-Effect table. This software testing technique is used for functions which respond to a combination of inputs or events.

Test Condition | TC1 TC2 TC3 TC4

User Name |Valid Invalid Valid Invalid
Password |Valid Valid Invalid Invalid
Homepage |Yes

Invalid/Error | Yes Yes Yes

Using decision table , it reduces time and effort tester and helps to align the testcases to cover requirements with less effort .Since we are documenting testcases in table it helps to verify for further use and also add scenarios when it missed while verify the table.

3.UseCase Testing:
Use Case Testing is a one of the software testing technique it helps to identify test cases that cover entire system on a transaction from start to end. In this technique should involve and make interaction with software system. Its helps to identify defects in an application which may missed to find by testing individual software components.

In general Use case Testing is depends on User Actions and System’s Response.

For Example,

UseCase Name | Login

UseCase Description | User login into System and redirecting to
Homepage
Actors | User,Admin
Pre-Condition | User credentials to be entered
Post-Condition | Successful login ,user will get
confirmation mail

Main Scenario S.No Steps

Actors/Users 1 Enter Username and Password
2 Validate Username and Password
3 Redirecting to Homepage
Extension 1a Invalid Username
System will throw error msg “Please enter
valid Username”
2b Invalid Password
System will throw error msg “Please enter
valid password”
3c Invalid password more than 3times then
Account will be blocked.

4.LCSAJ Testing:
Linear Code Sequence and Jump, it is used to determine code coverage.Percentage of a code executed with existing testcase and also helps to designing new testcases and increase coverage.
Once the code coverage reaches a certain level, we can stop the testing.
A single LCSAJ has,
• Start of the segment, End of the segment and specific target line
1.int a=5,b=3;
2.if(a>b)
3.{
4.a=a+1;
5.}
6.else
7.{
8.b=b+1;
9.}
10.return 0;
11.}
LCSAJ | Sequence Start | Sequence End | Jump |

2 5 10
6 9 10
10 11 Exit _______________________________________________________

Software testing, needs and relevance.

Priyadharsini RK — Sun, 19 Nov 2023 06:02:02 +0000

Today i have started learning about software testing with basis.
How the applications will starts develop,

Entrepreneur/Stakeholder who used to provide requirements to Business Analyst(BA) to make the application for their business need.
BA will analyse the requirements, feasibility and start designing the applications with features, functionality, components along with documentation.
Requirement Documentation which consists of all the features with module sections, each sections will define how the application of the particular screen should look also it will have component list with Attribute name, type, size and description.
Developers will get the KT from BA with requirement document then they analyse and start design screens along with components mentioned in the requirement after that they start writing the logic for the components of the screen and later they will integrate with next next screens, these things were done from front end.
From Back end the will keep database and create number of tables depends on project need, each table will data(which will get from application as a input).Then Backend developers will co-ordinate with Frontend developers and make connectivity by writing logics and query.
Once development done from development side then they do unit testing to ensure the functionalities working as per requirement.
Testers will start testing once the application is done with development phase and deployed into test environment.
In Testing phase if tester finds any defect then testers will report to developers once they fixed it then the defect back to tester, again tester has to test and confirm the whether raised issue is resolved or not. By that testers will determine the quality of the application.