DEV Community: AeroSiva

Selenium Architechture and Virtual Environment

AeroSiva — Tue, 03 Oct 2023 16:26:14 +0000

Selenium architecture:

In Selenium Framework Selenium WebDriver supports overall browser-based automation tests majorly. WebDriver is the remote-control interface component that allows test programs to instruct and interact with browsers, manipulate DOM elements in a web page, and control the user agent’s behaviour. 
Selenium WebDriver and Selenium RC were merged to form Selenium 2.0 and later upgraded to Selenium 3.0 now Selenium 4.0 is further developed.
Now, all companies widely use a 3X version of Selenium. Now 4x version has been introduced these two have completely two different architectures.

Selenium WebDriver 3.0 Architecture.

Selenium Client Libraries

Selenium client libraries or language bindings permit Selenium to support multiple languages to write test scripts like Ruby, C#, Python, and Java. It contains classes and methods required to write test automation scripts. It provides an application programming interface (API), i.e., a set of functions that performs the Selenium commands from the test script.
Web Driver protocol clients (They are thin wrappers around WebDriver protocol HTTP calls) and WebDriver-based tools are two major groups (These are higher-level libraries that allow us to work with WebDriver automation).

Json wire protocol

Selenium WebDriver 3.0 uses JSON to communicate between Selenium client libraries and browser drivers. The request sent by the client is converted into an HTTP request for the understanding of the server and it again returns information in the JSON format to the client. It uses Layer 5 of the OSI reference model.

Browser Driver

Browsers that support selenium have unique browser drivers like ChromeDriver for Google Chrome and GeckoDriver for Mozilla Firefox. It takes commands from the test scripts and passes them to the browser and is responsible for user actions like mouse clicks, keyboard inputs, etc.

This HTTP request is routed through the HTTP Server which in turn directly drives the command execution on the browser.
The browser then sends back the test status to the HTTP Server, which in turn forwards it to the test automation script.

Browser

Google Chrome, Mozilla Firefox, Microsoft Edge, and Apple’s Safari are some of the browsers Selenium supports it is also one of the components of Selenium Architecture. When these browsers receive a command it calls for respective commands and executes the test.

Selenium WebDriver 4.0 Architecture.

Here Json wire protocol is replaced by the W3C protocol. The problem with JSON protocol is that the commands need to be converted into HTTP requests because the server only understands protocols but with the introduction of the W3C protocol there is no such need so the test can happen faster.

Virtual Environment

It is the way we can separate different Python environments for different projects.

Significance of virtual environment

Isolation
If one is working on multiple projects and each project relies on packages like Flask, Django but in different versions, then installing these packages globally on his device may create conflicts and may even break the working projects. To avoid conflict virtual environment is created individually for every single project. And on these virtual environments, we can install all the necessary dependencies like libraries.
Dependency management
 Easy to manage dependencies like libraries, online services, and programming scripts.
Version Compatibility
 Simultaneously working on different versions of Python in different projects.
Clean and Reproducible Environments
 Easy to share projects and deploy we can give requirement files so the client can reproduce the environment.
Security
 By sandboxing Python projects it provides security to the project.
 Also, it prevents unauthorized access to the global libraries installed in the system.
Portability
 Packaging the entire project including its virtual environments project has higher portability.
Enabling Continuous Integration (CI) and Deployment
 Virtual environments play an important role in CI/CD (Continuous Integration and Continuous Deployment) pipelines. These pipelines use virtual environments to set up reproducible build and test environments.
Work on multiple Python projects
 Usually, all IT workers including Developers and Testers work on multiple projects and it is highly useful in that case.

So now,What is Selenium? and why do we need to use Selenium

AeroSiva — Mon, 02 Oct 2023 02:56:36 +0000

So what is Selenium?

In short, Selenium is a suite of tools for automating web browsers. It remotely controls browser instances and emulates the user’s interaction with the browser. It allows users to simulate common activities performed by end users;

Entering text in the field.
Selecting dropdown values.
Checking check boxes.
Clicking links in the documents.
Mouse movements.
Execution of arbitrary JavaScript, Etc.

Who uses Selenium?

The companies are using it for browser-based tests for functional test automation.

Let us discuss about Short history of Selenium

.
In Chicago Jason Huggins works in Thoughtworks consultancy, Where automatic testing of any application was done on Agile methodology. There he built a core of selenium mode as “JavaScript Test Runner” for testing an internal Time and Expenses application Plone._ Plone_ is a ready-to-run content management system, that offers a complete set of features needed by various organizations. When he shares it with his colleague it grows into what we see now due to its usage and contribution of many coders. Later initial development Shinya Kasatani in Japan wrapped the core into an IDE module in the Firefox browser to record tests and played it back to develop Selenium IDE. In 2007, With the support of Google Selenium RC and Selenium Grid, it gained much development. _Simon Stewarts _at Thoughtworks Web testing tool called WebDriver and Jason’s Selenium project was merged into get better selenium as of today.

Why Do we need to use SELENIUM ? First, let us understand various Test-Tool Suites.

Selenium IDE.
Selenium WebDriver.
Selenium RC.
Selenium Grid.

Selenium IDE.

• It is an easy-to-use browser extensions like

Google’s – Chrome/Chromium.
Mozilla’s - Firefox.
Microsoft – Edge • Generally, it is the most efficient way to develop a test case. Developed by Shinya Kasatani from Japan. • It records the User’s actions in the browser using existing Selenium controls with parameters defined by the context of that element.

Selenium WebDriver.

• At the core of selenium is the WebDriver, an interface to write instruction sets that can be run interchangeably in many browsers.
• WebDriver uses browser automation APIs provided by browser vendors to control the browser and run tests. This is as if a real user is operating the browser.
• API-Application programming Interface is the set of commands used to manipulate WebDriver.
• WebDriver passes commands to the Browser through the Driver and gets information back via the same path.
• Driver – Responsible for controlling the actual browser and is specific to the Browser such as

ChromeDriver for Google Chrome.
GeckoDriver for Mozilla Firefox.

These Drivers are generally executable modules that run on the system within the browser itself and not in the system executing the test suite.
• Tests may or may not be executed in the same system.

Selenium RC
• It is now WebDriver.
• It supports various languages like Python, PHP, C#, etc.

Selenium Grid

• After the development of the WebDriver tests, one may need to run tests on multiple browsers and operating system combinations.
• It is used to run test cases in different machines across different platforms.
• The control on triggering the test cases is on the local end, an when the test cases are triggered, they are automatically executed by the remote end.

Framework

An additional library is used as a support for WebDriver suites. This framework matches the language bindings.

Junit for Java.
Nunit for .NET.
RSpec for Ruby.

The test framework is responsible for running and executing WebDriver and related steps in tests. Natural language frameworks /tools such as Cucumber may also exist as part of that Test framework box.

And Finally for now can we once some thing regarding manual testing

AeroSiva — Sun, 03 Sep 2023 17:20:03 +0000

Manual testing:

It is a software testing process in which test cases are executed manually without using any automated tool. Here all the test cases are manually executed by the tester in the end user perspective. The difference between the actual output and the expected output is termed as defect and the test report is also prepared manually. Manual testing is done before the automation testing. And as the tester gets familiar with the application in the end user perspective, it will be useful for the tester to check all the bugs and end user’s difficulty and is also useful to write automation testing scripts.

Types of manual testing:

White box testing: done by developer and the code is visible is so called a white box. Checks whether the cod is written as per the standard or not.
Black Box testing: Done by test engineer and the code is not visible so called as Black box. Checks the functionality.
Grey Box testing: combination of both white box and black box. It requires requirement document to write test cases. Some of the tools used by the manual testers for manual testing are: • Jira • Jmeter • Mantis Drawbacks of manual testing:
It needs large number of human resources and hence needs more money resource also.
It is a time-consuming process.
Tester develops test cases based on their skills and experience. There is no evidence that they have covered all functions or not.
Test cases cannot be used again. Need to develop separate test cases for each new software.
It does not provide testing on all aspects of testing.

Some examples in support of my answer

Need more resources: As this involves manually testing , IT companies need skilled and trained software testers which cost them extra man power and extra cost for the support of that man power.
Time consuming: As the tester need to execute each test cases manually it requires more time. • Regression testing: It is not practically possible to make regression testing again and again with full perfection after each time modification is made in the program.
Test case efficiency: In some cases if testers overlook some test cases, or mis interoret results, or make mistake while executing test cases, the efficiency of the test case may in question. • Constraints: Due to time constraints and resource constraints it is not possible to check each and every test cases as expected so as to ensure the application is bug free.
Test case not reusable: As the testers need to write again and again some same kind of work they may loss interest. And make mistake even when recreating test cases. It needs more time to test.
All aspects of testing: not possible to perform extensive load testing and performance testing in a level of the market demand. • Load testing, stress testing: Practically it is impossible to simulate real world level load and stress level within company by using manual testing.

Here can we discuss about what is the difference between functional and non- functional testing briefly.

AeroSiva — Sun, 03 Sep 2023 16:58:00 +0000

So first of all what is Functional Testing

It is a black box testing. Testing what the system actually does is functional testing. It is to check whether each function of the software application behaves as specified in the SRS document. It is testing all the functionalities by providing appropriate input to verify whether the actual output is matching the expected output or not.
What the system actually does is functional testing
To ensure that the product meets customer and business requirements and doesn’t have any major bugs
To verify the accuracy of the software against expected output
It is performed before non-functional testing
Example of functional test case is to verify the login functionality

some Testing types are

• Unit testing/ Component testing- it checks individual unit/module – usually done by Developer
• Smoke testing – it is also called as day 0 testing, It is to check whether key features and key bugs, usually done on unstable build. The main purpose is to check whether the build is testable or not.
• User Acceptance – Basically there are there are 2 user acceptance test viz. 1. Alpha, Beta. One done by inhouse developer or tester in the customer point of view. while another is done by limited number of end users. There is also third type namely Gamma testing – which is done at client place in the absence of inhouse developer and tester, and is done by Client-side developer or tester or by both.
• Integration Testing – it is done by integrating 2 or more individual software units/ modules.
• Regression testing- It is repeated testing of already tested software after modification , since the modification may brought new bugs or defects which wasn’t there before modification.
• Localization – Adapting global software to specific region or locality.
• Globalization – Adapted to varies region and language without any changes.
• Interoperability- It is done to check interaction either with two software or its components. There are five subtypes they are:1. Data type interoperability testing, 2. Semantic interoperability Testing, 3. Physical Interoperability testing, 4. Protocol Interoperability Testing (Security), 5. Data format Interoperability testing.

Here then we see about Non-Functional Testing

How well the system performs is non-functionality testing. Non-functional testing refers to the things such as performance, load, stress, scalability, security, compatibility etc., Here the main focus is to improve the user experience on how fast the system responds to a request.
How well the system performs is non-functionality testing
To ensure that the product stands up to customer expectations
To verify the behavior of the software at various load conditions
It is performed after functional testing
Example of non-functional test case is to check whether the homepage is loading in less than 2 seconds

Some Testing types are

• Performance Testing – Check the behavior of the application by applying load like response time, simulating multiple user, simulating many transactions.
• Volume Testing- It is basically performed by increasing the volume of data in the database.
• Scalability- is a type of load test.it teat how the system is gong to perform during sudden spike or fall of user request load.
• Usability Testing- It is done by researchers either working in-person or remotely to find out what are all the places the users usually gets struck or confused, so that the user experience can be improved by solving the issues.
• Load Testing- It is a type of performance testing. Specifically it tests the performance of the application when multiple users are using the application.
• Stress Testing- also called as Endurance testing and Torture testing. Different things measured in this testing are pages per second, pages retrieved, Byte data, transaction per second Failure of connection. And all these are under stress condition.
• Compliance Testing- Validate software’s compliance with the company’s standards, policies, and philosophies.
• Portability Testing- How easy or difficult to transfer software or its components to another hardware, environment, software-Operating System.
• Disaster Recover Testing – It is a type of system testing. It is important for mission-critical system like defense system, medical devices. And the failure are like power cut, external server not reachable, Wireless network system loss, external device not working properly.

Let we discuss about some topics like 1) Boundary Value Analysis 2) Decision Table Testing 3) Use Case Testing 4) LCSAJ Testing

AeroSiva — Sun, 03 Sep 2023 16:43:59 +0000

Boundary Value Analysis
It is one of the functional testing. It is based on testing the boundary values of valid and invalid partitions. Boundaries are values where testing is likely to yield defects.
For each variable we check-
1) Minimum value.
2) Just above the minimum.
3) Nominal Value.
4) Just below Max value.
5) Max value.
For example:
If the valid input is between 1 to 10. Then the boundary values are 0,1,2 and 9,10,11.
Limitations:
• It is useful when the product is under test.
• BVA is quite rudimentary.
Decision Table Testing
This technique is used if we have more conditions and we have to perform action based on the conditions at that moment.

The decision table have four parts they are.
Stubs   Entries

Condition C1
C2
C3

Rule
Action A1
A2
A3

Outputs

Condition stubs.
Action stubs
Condition Entries.
Action Entries.

For example:
Condition:
1. Account has to be approved.
2. OTP to be matched
3. Sufficient amount to be present in the account
Action:
1. Transfer money.
2. Show alert message “insufficient account balance”
3. Block if any suspicious activity.
TC1 TC2 TC3 TC4 TC5
Condition 1 Account already approved T T T T F
Condition 2 OTP Matched T T F F x
Condition 3 Sufficient money T F T F x
Action 1 Transfer money Execute

Action 2 Show insufficient money alert message Execute

Action 3 Block the transaction Execute Execute x

Use Case Testing
It is a Black box testing.Use Case is a tool for defining the required user interaction. It depends on the user interaction and the response of the system to the user’s action. It is mainly user- oriented. It tests the functional requirement of the system. It usually helps to uncover the integration defects, due to the incorrect interaction between different components.
Use case testing is generally produced from the SRS document. If specific User interaction scenario missed in the SRS document, probably the same be missed in the test case also.
For example:

User - Enters the mail Id.
System – Validates the mail id.
User – Enters the password.
System – Validates the Password.
System – Enter in to respective user mail.

Linear code sequence and jump (LCSAJ) Testing:
It is a white box testing used to test code coverage. Means what percentage of code is executed with the existing test cases.
It has three components they are
1) Start of the segment.
2) End of the segment.
3) Target line
The code usually executes from the start of the segment to the end of the segment and then the control flow breaks the sequential execution and jumps to the target line to transfer the control flow.
For example:
LCSAJ Number Starting of the segment Ending of the segment Target line to transfer control flow
1 4 9 11
2 4 13 7
3 7 10 15
4 7 13 7
5 11 13 7

100% LCSAJ coverage means the test data covers all the above LCSAJs in the table.
And line density means number of times the a line number appears in LCSAJs.

Want to know about Automation Testing ???

AeroSiva — Sun, 03 Sep 2023 16:26:26 +0000

Here we are going to find answers for What is software testing ? what we need to know about software testing ? What is the relevance of software testing ?

First what is Software:

Software refers to a collection of programs, data, and instructions that tells a computer what to do. It enables hardware (the physical components of a computer) to perform specific tasks and functions.

Then what is Software Testing:

Software testing is the process of verifying and validating whether a software or application is quality or not that is checking whether it is

• bug-free,
• meets the technical requirements,
• is functioning efficiently and effectively.
In software testing two important words are used they are
Verification: “Are we building the product right?”
• it refers to the set of tasks that ensure that the software correctly implements a specific function.
Validation: “Are we building the right product?”
• it refers to a different set of tasks that ensure that the software that has been built is traceable to customer requirements.

What are the Types of software testing:

There are mainly two types of software testing they are.
        1. Manual testing.
        2. Automation Testing.

Do you know about Manual testing:
This testing is done without using any automation tool or any script. The tester took over the role of end-user and test the software to identify defects.
Levels of the testing in manual are:

unit testing,
integration testing,
system testing, and
user acceptance testing. Testers use test plans, test cases, or test scenarios to test software to ensure the completeness of testing.

Here is what you seeking for _Automation Testing / Test automation:_

Here in Automation testing the tester writes the scripts and uses another software to test the product. Here the automation of manual process takes place. Apart from regression testing, automation testing is also used to test the application from a load, performance, and stress point of view. It increases the test coverage, improves accuracy, and saves time and money when compared to manual testing.

what we need to know about software testing?

*1. Types of Testing: *
1.Functional Testing – test whether the actual output matches the expected output or not.
i). Black box testing
2. Non-functional Testing – How well th system performs.
i). Performance Testing: Evaluates the system's performance under various conditions to ensure it meets performance requirements.
ii). Load Testing: Measures how the software performs under expected and peak loads.
iii). Usability Testing: Assesses how user-friendly the software is by observing how users interact with it.
iv). Load Testing: Measures how the software performs under expected and peak loads.
v). Compatibility Testing: Ensures the software works correctly on different devices, browsers, and operating systems.

2.Levels of testing.
i). unit testing,
ii). integration testing,
iii). system testing, and
iv). user acceptance testing.

3.Software Developing Lifecycle (SDLC) Models.
i).Waterfall model
ii). Prototyping model
iii). Iterative/ incremental model
iv). Spiral
v). V-model
vi). Agile model
vii). RAD model
4. Software Testing Life cycle (STLC)
i. Requirement analysis- Requirement traceability matrix - RTM
ii. Test planning – Test strategy
iii. Test case development – Test case
iv. Test environment setup.
v. Test execution- Defect logging, Test dat preparation, Defect retesting, Test reporting.
vi. Test closure – test summary report, defect tracing, Test environment cleanup, Test closure report. Knowledge transfer, Feedback and improvement.
5. Test Case design Techniques.
1. Dynamic testing.
i. From SRD/ Black box testing.
ii. From structural component of a system.
iii. From testing experience
2. Static testing
i. Review.
ii. Walkthrough
iii. Inspection
iv. Technical review
6. Principles of Software testing.
7. Some important keywords used in software testing life cycle. some of them are.
1. Continuous Testing
2. Security Testing
3. Alpha and Beta Testing.
4. Regression Testing
5. Code Coverage
1.Unit Testing
2.Integration Testing
3.User Acceptance Testing (UAT)
1.Alpha and Beta Testing

What is the relevance of software testing ?

Software testing is highly relevant and essential in the field of software development for several crucial reasons:

Quality Assurance
Defect Identification
Risk Mitigation
User Satisfaction
Compliance and Regulations
Cost Savings
Continuous Improvement
Release Confidence
Competitive Advantage
Customer Trust
Security
Maintenance.
Documentation and Knowledge Sharing