DEV Community: Sujitha

Selenium Architecture

Sujitha — Sun, 17 Dec 2023 08:49:24 +0000

Selenium WebDriver Architecture:

Selenium WebDriver is currently the most widely used component in the Selenium tool suite. Selenium WebDriver: Selenium 2 integrated with WebDriver API provides an understandable programming interface. JAVA and C# languages are mostly preferred to work with Selenium.
Through test scripts, WebDriver simulates user actions, navigates through web pages, interacts with elements (such as button, text, dropdown menu, forms, links, etc), submit forms, perform validations, assertions and many more.

Architecture of Selenium WebDriver (Selenium 3):

In Selenium 3, there is no direct communication between the client libraries (Java, Python, JavaScript, etc) and the browser drivers. The server (browser drivers) does not understand language but only the protocols and on the other hand, client libraries does not understand protocols used by browser drivers.
Therefore, JSON Wire protocol is being used as a mediator between client and server to encode and decode the requests and responses made by client and server respectively. This results in limited browser interaction, inefficient communication and lack of standardization which ultimately led to flaky test and slower test execution.

Architecture of Selenium 4 WebDriver:

The architecture of Selenium is composed of:

1. Selenium IDE:
Selenium IDE (Integrated Development Environment) is primarily a record/run tool that a test case developer uses to develop Selenium Test cases. It is just a web-browser extension.
Selenium IDE is an easy-to-use tool from the Selenium Test Suite and can even be used by someone new to developing automated test cases for their web applications.

2. Selenium Remote Control:
Selenium RC is an important component in the Selenium test suite. It is a testing framework that enables a QA or a developer to write test cases in any programming language in order to automate UI tests for web applications against any HTTP website.

3. Selenium WebDriver:
Selenium WebDriver is a web framework that permits you to execute cross-browser tests. This tool is used for automating web-based application testing to verify that it performs expectedly. Selenium WebDriver allows you to choose a programming language to create test scripts.

Selenium WebDriver Architecture is made up of four major components:

Selenium Client library: Selenium provides support to multiple libraries such as Ruby, Python, Java, etc as language bindings
JSON wire protocol over HTTP: JSON is an acronym for JavaScript Object Notation. It is an open standard that provides a transport mechanism for transferring data between client and server on the web.
Browser Drivers: Selenium browser drivers are native to each browser, interacting with the browser by establishing a secure connection. Selenium supports different browser drivers such as ChromeDriver, GeckoDriver, Microsoft Edge WebDriver, SafariDriver, and InternetExplorerDriver.
Browsers: Selenium provides support for multiple browsers like Chrome, Firefox, Safari, Internet Explorer etc.

4. Selenium Grid
It is used to run parallel tests on multiple devices running different browsers at different geographical locations
We can run multiple test-cases simultaneously at one moment of time
It used the Hub-Node architecture or Master-Slave architecture

Python virtual environment:

Python virtual environments give you the ability to isolate your Python development projects from your system installed Python and other Python environments. This gives you full control of your project and makes it easily reproducible

Usage of Python Virtual Environment

From terminal / command-prompt

Check the version of Python virtual environment

virtualenv --version
Create a Python Virtual environment

virtualenv
Activate your Python Virtual environment
_ Scripts\activate_
Deactivate your Python Virtual environment

Scripts\deactivate

Pycharm:
PyCharm makes it possible to use the virtualenv tool to create a project-specific isolated virtual environment. The main purpose of virtual environments is to manage settings and dependencies of a particular project regardless of other Python projects.

SELENIUM

Sujitha — Thu, 14 Dec 2023 11:06:18 +0000

What is selenium?

Selenium is Automation tool
It is a open source product, and freeware
supprots different platform and browser.
Selenium is used with Java, Python, JavaScript, C#, Ruby, PHP etc.

It has a suite of tools which caters to different needs of organizations. It basically has four different tools:

Selenium RC (which is now deprecated)
Selenium IDE (Selenium Integrated Development Environment)
Selenium Grid
Selenium WebDriver

Why do we use selenium for automation?

The benefits of Selenium Testing with respect to Test Automation are immense.

It enables testers to write automated tests in various programming languages to test the functionality of web applications.
Selenium tests can be run on many different browsers and operating systems
Selenium Testing Tool is an excellent tool for automating web application testing.
It enables record and playback for testing web applications and can _*run multiple scripts *_across various browsers.
Selenium automation test suites are reusable and can be tested across multiple browsers and operating systems.
it helps the developers and testers in quick changes to the code, reducing duplication, minimizing complications and improving maintainability. These features make Selenium more flexible and usable as compared to other automation testing tools and hence helps Selenium to keep an edge.
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.

Manual Testing Benefits & Drawbacks

Sujitha — Mon, 20 Nov 2023 12:32:18 +0000

Manual Testing:

Manual testing is type of software testing which is used to test software product or web applications or mobile applications by manually (Tester) without using any automated tool.
In software testing “100% automation is not possible”.
It checks the quality of the product and deliver the error-free product to client.

Benefits of Manual Testing:

In manual testing there is no environmental limitations.
In manual testing there is no programming knowledge is required.
In manual testing it easy to find the errors in early stage.
In dynamically changing projects and GUI design manual testing plays an important role.

Drawbacks of Manual Testing:

Manual testing needs more time and more resources.
In manual testing executing the same test cases again and again is tedious process.
Testing with large number of data is quite impossible in manual testing.
In manual testing performance testing is not possible.

Example:

For ecommerce website it is not possible to have same UI, in this case manual testing is more preferable.
Load testing and stress testing in not possible in manual testing
To test large number of data is impossible
Executing the same test case in multiple time is tedious process.

Funtional Testing vs Non-Functional Testing

Sujitha — Sat, 18 Nov 2023 10:43:49 +0000

Functional Testing:

Checking the functionality of the application works fine according to the client needs. It verifies that each function of the software application works in conformance with the requirement and specification.

Purpose of Functional Testing

Test each function of the application.
Test primary entry function.
Test flow of the GUI screen.

What to Test in Functional Testing?

Basic Usability.
Mainline functions.
Accessibility.
Error Conditions.

Functional Testing Process

Non-Functional Testing:

Checking how other aspects of the applications working fine. Checking performance, stability, usability of the application.
Helps to reduce production risk and cost associated with non-functional aspects of the product.

Non Functional Test Types

Performance Tests
Load Tests
Stress Tests
Volume Tests
Security Tests
Upgrade & Installation Tests
Recovery Tests

Non-functional testing Parameters

Functional testing vs Non-Functional Testing:

Software Testing Technique

Sujitha — Sat, 18 Nov 2023 09:48:01 +0000

Software Testing Technique:

Software Testing Technique is used to design your test cases in a better way. Even though completing testing is not possible, this test technique helps you to reduce the number of test cases by increasing test coverage. This testing technique makes you to identify test condition easier at the time of difficult to recognize.

Types of Test Case Design Technique:

Boundary Value Analysis
Equivalence Class Partitioning
Decision Table
State Transition
Error Guessing

Boundary Value Analysis:

Boundary Value Analysis is one the testing techniques in Black Box testing which is used to test the values on the boundaries. It usually focused between both the extreme ends or between both the extreme boundary values.
Boundary values like Start-End, Lower- Upper, Maximum-Minimum, Just Inside-Just Outside values.
The basic idea to select input variable values at their:
1. Just below the Minimum
2. Minimum
3. Just above the minimum
4. A nominal value
5. Just below the maximum
6. Maximum
7. Just above the maximum.
Example:
One form that have age field which accepts the person’s age group between 18 to 35. While testing this field as a tester we should write a greater number of test cases to test. With the help of boundary value analysis technique, it reduces the number of test cases with more test coverage.
```
                Application Form

     Name: _____________(_Accepts alpha-numeic_)
     Age: ______________(_must above 18 and below 35_)
```

For the above case, if we apply Boundary Value Testing technique which would involve testing the following values:

Test Case 1: Test a value just below the minimum boundary (17).
Test Case 2: Test the minimum boundary value (18).
Test Case 3: Test a value just above the minimum boundary (19).
Test Case 4: Test a nominal value (22).
Test Case 5: Test a value just below the maximum boundary (34).
Test Case 6: Test the maximum boundary value (35).
Test Case 7: Test a value just beyond the maximum boundary (36).

Decision Table Testing:

Decision Table is one the testing techniques in Black Box testing which is used to test system behaviour for various input combinations. In this technique, the several input combinations and their corresponding system behaviour are picturized in tabular form. It is also known as a cause-effect table.

Use of decision table testing?

Decision tables are an effective tool for managing multiple combinations of conditions and actions, allowing for a comprehensive analysis of all possible scenarios. This inclusive approach minimizes the risk of overlooking critical test cases. Software applications encompass various possible inputs and outputs.

This technique is used to pick the test cases in a systematic manner

Example:

Let’s take a login page with user name and password. If both user name and password are correctly matched, the user will be directed to the landing page; otherwise, it will come back to the login page with an error message like "Incorrect User Name" or "Incorrect Password."
Decision table for the login functionality in which we can log in by using user name and password. Both the user name and the password are the conditions, and the expected result is action.

In the table, there are four conditions or test cases to test the login function. In the first condition if both user name and password are correct, then the user should be directed to Landing page.
In the second, third and final condition if both user name and password are in correct or either user name/password is incorrect, then it should display Incorrect user name or password.
In order to find the number of all possible conditions, tester uses 2n formula where n denotes the number of inputs; in the example there is the number of inputs is 2 (one is true and second is false).

Number of possible conditions = 2^ Number of Values of the second condition
Number of possible conditions =2^2 = 4

Use Case Testing:

Use Case Testing is a functional black box testing technique that helps testers to identify test scenarios that exercise the whole system on each transaction basis from start to finish. Test cases are the interactions between users and software application.

Benefits of Use Case Testing:

Helps manage complexity.
Testing from the user’s perspective.
Reduced complexity of test cases.
Test functional requirements.
Starts from a simple view of the system.

Drawbacks of Use Case Testing:

Missing use case.
Cover only functional requirements.
Use cases are from the user’s perspective.

Use Case Example:

Case for ‘Login’ to a ‘School Management System’.

LCSAJ Testing:

LCSAJ means Linear Code Sequence and Jump. LCSAJ testing is a white-box testing technique used to determine the code coverage.

Software Testing - Introduction

Sujitha — Wed, 15 Nov 2023 07:12:41 +0000

What is Software Testing?

The process of evaluating the software product or web application or mobile app to ensure that should be functionally working fine and meet the client needs.
Testing is done to make sure if the product is doing what it is supposed to and what it's not supposed to do.
Gap between the actual to expected result is analysed.
Testing process involves verification and validation Verification: Are we building the product, right? _ Validation:_ Are we building the right product?

Why Software Testing?

The main aim of the software testing is to give quality product to its clients and quality of product is measured by how the product is bug-free and meet the client's requirements.
Customer satisfaction is fulfilled by 100 % defect free product and trust will be increased and will get more projects.
By finding the bugs in early stage reduces the time and cost. Brings more profit.
Performance of the software product will get improved.

When to start software Testing ?

Once we get the requirement document, we can start software testing process side by side parallelly when software development life cycle stared.

When to stop software Testing?

When all the major and critical bugs are fixed and executed all the test cases and the functionality works as per the client's need, then we can stop software Testing.

What should we do in software Testing?

Gathering the requirements and step-up testing environment
Create Test scenarios and write test scripts
Should concentrate on both positive and negative aspects
Preparing test data
Executes the test cases and prepare test summary report
Raise bugs with proper documents and monitor the status of the big

What should not we do in software Testing?

Should not make assumptions at the time of execution
Should not start the test process without knowing the scope of the product and proper test plan
Should not neglect any defects
Should not sign off the test process until all major functionalities are tested and no open bug is there.

Kinds of Software Testing:

Manual testing: Testing any software product or application according to the client need by manually without using any automation tool.
Automation Testing: With the help of specific tools to automate manual design test case without human interference. It is used to re-run the test scripts quickly and repeatedly which increases the productivity and efficiency.

Classifications of manual testing

White Box Testing: It checks the structure of the code and it is also called as structural testing
Black Box Testing: Checking the functionality of application without concerning about structure of the code.
Grey Box Testing: Combination of both white box testing and black box testing.

Types of Testing:

Functional Testing: Checking the functionality of the application works fine according to the client needs.
Non-Functional Testing: Checking how other aspects of the applications working fine. Checking performance, stability, usability of the application.

Levels of Testing:

Unit Testing: It is the initial stage of testing which is used to verify the logics of each and every individual module or component. Unit testing is done by developer
Integration Testing: It is the next stage of testing which is used to check the data flow and communication flow between two or more related individual modules or components.
System Testing: Checking the functionality and behaviour of the application as whole.
Acceptance Testing: Checking the functionality and behaviour of the application by the customer or end user.

We need to know about Software Testing:

First, we need to know about basic testing process.
Know about basic Testing concepts.
Know about basic Testing methodologies.
Know about basic Product and domain knowledge.
Know how to write a TestCase
Know how to execute a TestCase
Know how to report and track bugs.