DEV Community: Narasimha Varman J

Task-15-RM-17

Narasimha Varman J — Wed, 08 May 2024 11:19:02 +0000

Selenium
Selenium is an open source framework used to automate the web applications across various browsers.

Selenium is primarily developed using JavaScript.

It has a combination of Tools like;
1) Selenium IDE
a. Selenium IDE is a browser extension for Firefox or Chrome that automates functionality.
b. IDE records user interactions on the browser and exports them as a reusable script.

2) Selenium RC
a. Selenium Remote Control is a server written in Java that makes provision for writing application tests in various programming languages like Java, C#, Perl, PHP, Python, etc.
b. The RC server accepts commands from the user program and passes them to the browser as Selenium-Core JavaScript commands.

3) Selenium WebDriver
a. Selenium WebDriver was the first cross-platform testing framework that could configure and control the browsers on the OS level.
b. It serves as a programming interface to create and run test cases.

4) Selenium Grid
a. Selenium Grid allows the parallel execution of tests on different browsers and different operating systems.
b. Grid is exceptionally flexible and integrates with other suite components for simultaneous execution.
c. The Grid consists of a hub connected to several nodes.
d. It receives the test to be executed along with information about the operating system and browser to be run on and picks a node that conforms to the requirements (browser and platform), passing the test to that node.
e. The node now runs the browser and executes the selenium commands within it.
f. Selenium Grid tests across multiple instances and machines at once.

These tools offer a single interface for inputting test scripts in a number of popular coding languages like Ruby, Java, Python, C#, JavaScript, Perl. It has the ability to create automated tests from these scripts and run them locally or remotely on a range of browsers.

Selenium automation uses the Selenium toolbox to run tests across different browser instances.

Tests that can be performed are:
a) System testing
b) End-to-end testing
c) Compatibility testing
d) Regression testing
e) Integration testing
f) Performance testing

Advantages of Selenium Testing
i) Selenium has proven to be accurate with results thus making it extremely reliable
ii) selenium is open-source and anybody willing to learn testing can begin at no cost
iii) Selenium supports a broad spectrum of programming languages like Python, PHP, Perl, and Ruby
iv) Selenium supports various browsers like Chrome, Firefox, and Opera, among others
v) Selenium is easy to implement and doesn’t require the engineer to have in-depth knowledge of the tool
vi) Selenium has plenty of re-usability and add-ons

Disadvantages of Selenium Testing
i) Limited support for desktop applications
ii) Lack of built-in reporting
iii) Limited support for mobile testing
iv) Lack of Synchronization
v) Requires 3rd Party Tool Bindings
vi) Slow Test Development Due to the Script-Based Approach
vii) Inability to Integrate Continuous Testing / In-sprint Automation

Task-18 RoadMap-18

Narasimha Varman J — Mon, 06 May 2024 11:30:41 +0000

Python Selenium Architecture in Detail

Selenium is used as an Application Programming Interface [API] to automate the test cases of web applications.

Selenium is used as an automation tool for web application testing, using Python programming language. Selenium scripts can be written using only programming languages; the most commonly used programming languages are Java and Python.

Python and Selenium work together to create automation scripts and code that are used to interact with web browsers.

Selenium Suite comprises Selenium IDE, Selenium RC, Selenium Webdriver, and Selenium Grid.

Selenium Webdriver Architecture
Selenium WebDriver architecture is designed to support cross-browser testing and parallel testing. It also supports integration with testing frameworks to improve automation testing and reporting.

Selenium WebDriver Architecture is made up of four major components:

Selenium Client library: (Selenium language Binding)

a. Selenium supports multiple libraries such as Ruby, Python, and Java as language bindings.
b. Selenium commands in the desired programming language in compliance with the W3C Selenium protocol.
c. The selenium client library can be divided into two groups:
i. Web Driver protocol clients - They are thin wrappers around WebDriver protocol HTTP calls.
ii. WebDriver-based tools - These are higher-level libraries that allow us to work with WebDriver automation.
d. Selenium API:
i. Selenium API is a set of rules and regulations that the programs use to communicate with each other.
ii. APIs work as an interface between the program and aid in their interaction without any user knowledge.

JSON wire protocol over HTTP:

a. JSON is an acronym for JavaScript Object Notation
b. The Selenium WebDriver uses JSON to communicate between client libraries and drivers.
c. The JSON requests sent by the client are converted into HTTP requests for the server’s understanding and again converted back to JSON format while sending it to the client again.
d. This data transfer process is serialization.
e. By this method, the internal logic of the browser is not revealed, and the server can communicate with the client libraries, even if it is not aware of any programming language.

3) Browser Drivers

a. Browser drivers act as a bridge between the Selenium libraries and the browsers.
b. They help to run Selenium commands on the browser.

4) Browsers
a. Selenium test scripts can be run across various browsers like Chrome, Safari, Firefox, Opera, and Internet Explorer and operating systems like Windows, Mac OS, Linux, and Solaris.

> Significance of the Python Virtual Environment with Examples

Python virtual environments are the light version of the conda environments.

Virtual environments are a native tool to Python developers, and they provide functionality similar to that of the conda environments.
The main difference is that they rely on the Python package manager.

A virtual environment is created on top of an existing Python installation, known as the virtual environment's “base” Python, and may optionally be isolated from the packages in the base environment, so only those explicitly installed in the virtual environment are available.

It contains a specific Python interpreter and software libraries and binaries that are needed to support a project (library or application) Isolated from software in other virtual environments and Python interpreters and libraries installed in the operating system.

Contained in a directory, conventionally either named venv or .venv in the project directory, or under a container directory for lots of virtual environments, such as ~/.virtualenvs.

It does not check into source control systems such as Git.

Considered as disposable – it is simple to delete and recreate it from scratch. project code not required in the environment

Not considered as movable or copyable – it is re creatable in the same environment in the target location.

Email, chat, and web-based document-sharing applications are all examples of virtual environments. Simply put, it is a networked common operating space.

Task-4

Narasimha Varman J — Tue, 27 Feb 2024 16:18:26 +0000

Manual Testing
Software Testing is part of the Software Development Life Cycle. Manual Testing is a part of the Software Testing. A Tester tests software for defects without using any automated test tools.
Manual Testing is a process in which test cases are executed manually without any automation tools. It helps in detection of defect, verification, and testing user scenarios from user perspective.
Manual Testing identifies defects and ensure software applications is free from defects and bugs.
Manual Tester creates and executes test cases, identifying and documenting defects and working closely with the development team to resolve issues.
Water Fall Model is best suited when there are defined requirements.
Agile Methodology is best suited when the requirements keeps changing or not standard.
1) Plan
2) Design
3) Develop
4) Test
5) Release

Software Testing Life Cycle

1) Requirement Analysis
a. In requirement analysis tester checks and analyse the requirements of the document
b. The entry criteria , environment setup and deliverables are analysed
c. Automation Feasibility report and requirement traceability is analysed
2) Test Planning
a. Based on the requirement specification test strategy and effort estimation will be planned
b. Test plan document
3) Test Design
a. Defining the test technique, test scenario, test cases, test data and expected test results
4) Test Environment
a. Setting up the testing environment will be carried by the senior developers
5) Test Execution
a. Detailed test case execution and the required test data
6) Defect Tracking
a. All the identified defects are recorded, reproduced and tracked
b. After the defects is being fixed retesting will be done
c. Test cycle closure
7) Test Reporting
a. This test cycle closure report includes all the documentation related to software design, development, testing results and defect reports

Types of Manual Testing

1) Black Box Testing
a. Checking the functionality of the product
b. Checks only the front end of the product
2) White Box Testing
a. Checking the codes of the product
b. Checks only the back end of the product
Unit Testing
1. Use to evaluate the performance of individual units of an application to confirm the functions work as expected
2. Performed by developers or QA Professionals
3) Grey Box Testing
a. It is a technique of combining white box and black box testing
b. It will be performed by developer and the specialized tester
Integration Testing
a. To evaluate an application with two or more components to check how it interacts with one another and how the process flow is completed.
System Testing
a. Used to evaluate the software performance from start to end of all unit and integration tests of how it performs.
Usability Testing
a. Performed by non-technical or without prior knowledge of the software based on the usage and feedback.
User Acceptance Testing
a. Performed by the end user to confirm that the software meets the required output and the user can perform all the required operations as per the specification

Manual Testing Process
1) Understanding the software requirement
2) Test Plan Creation
3) Write Test cases which covers all the requirement of the document
4) Execute Test Cases
5) Defect Logging
6) Defect Fixing and Re verification
Benefits
Human Intelligence
Adaptability
Cost-Effective
Early Detection
Simplicity
Best suited for small projects
Testers can perform live testing even at customer site
Execute the test cases
While user acceptance testing is performed tester or the customer can perform the tests.
Any irrelevant happenings can be observed and noted and communicated
Drawback
Manual testing is time consuming
Manual Testing is expensive
Human errors can happen
Load Testing and Stress testing cannot be performed in single instance for long hours or continuous testing is not possible from a single tester at a stretch
If customer request to perform test at their site, it takes time and cost to perform it.

Examples
We want to check the working Function of the Login Button of a page

Requirement Analysis
To Perform the Login Button function of the given Home page using Valid and Invalid username and password.
Test Scenario-1
1) Checking Login Button on google chrome browser
2) Checking Login Button on safari browser
Test Case-1
1) Open google chrome and safari browser separately
2) Input valid username in the user name field
3) Input valid password in the password field
4) Click the Login button
Test Case-1 Input
1) User name = john and Password = I@john
Test Case-2 Input
1) User name = genita and Password = I@john
Test Case-1 Output
1) Login page should allow the user to login
Test Case-2 Output
1) Login Page should allow the user to login
Test Case-1 Result
1) If the Login button accepts user Test Case Pass
2) If the Login button does not accept, Test Case Fail
Test Case-2 Result
1) If the Login button accepts user Test Case Pass
2) If the Login button does not accept, Test Case Fail

Test Scenario-2
1) Checking Login Button on google chrome browser
2) Checking Login Button on safari browser
Test Case-1
1) Open google chrome and safari browser separately
2) Input Invalid username in the user name field
3) Input valid password in the password field
4) Click the Login button
Test Case-1 Input
1) User name = Jesintha and Password = I@john
Test Case-2 Input
1) User name = Alex and Password = I@john
Test Case-1 Output
1) Login page should disallow the user
Test Case-2 Output
1) Login Page should disallow the user
Test Case-1 Result
1) If the Login button accepts user Test Case Fail
2) If the Login button does not accept, Test Case Pass
Test Case-2 Result
1) If the Login button accepts user Test Case Fail
2) If the Login button does not accept, Test Case Pass

Task-3

Narasimha Varman J — Sun, 18 Feb 2024 14:12:42 +0000

Functional Testing
Functional Testing is a black box testing performed to check all the functions are performed as per the software requirement specification and working as expected.
Different types of Testing are 1) Manual Testing and 2) Automation Testing
Manual Testing are carried out by the coder or the tester
Automation Testing are performed by the tester
Functional Testing involves Manual intervention and a manual process
Types of Functional Testing are:
Unit Testing – Performed on the codes being written
Smoke Testing – performed to confirm whether the software can be sent for next phase
Integration Testing – Performed while integrating different unts
System Testing - Performed while integrating different modules
Regression Testing – Repeated or performed when a error is fixed and validated
Performance and Load Testing – performed on the system performance and the load on the product
User Acceptance Testing – performed in the real time environment at the end user sytem or environment

Non Functional Testing
Non Functional Testing are performed to ensure all the aspects of application are tested and accepted in all varying experiments.
It is tested about the readiness of the system as per non-functional parameters which are not covered in Functional testing.
Types of Non Functional Testing are:
Portability testing – performed whether it can run on different operating systems
Reliability testing – performed using set parameters and confirm the expected outputs
Security testing- performed to withstand security threats
Volume testing- performed using big volume on the system
Accountability testing- performed to confirm the desired functions are achieved as per the standards

Task-2

Narasimha Varman J — Sun, 18 Feb 2024 13:12:30 +0000

1) Boundary Value Analysis
As the word “Boundary” denotes edge or corner. In testing the input values used for the testing purpose is taken from the boundary.
Example:1
If we have to check the value of mobile numbers in india, it should have ten digits.
So the number should be between, 1 and 9
Here the Boundary values are-1, 0, 1, 8,9,-9
To validate the phone numbers separate function should be implemented
The Boundary value testing should pass in as per the requirement.
Any failure in above case will be “Test Case Failure”

2) Decision Table Testing
This type of technique is used to identify and observe how the system performs when a combined inputs are given to the system for processing.
This type of testing is performed during the black box design technique
A decision table is prepared with all the possible inputs
Example:2 Checking Indian Mobile Numbers
Conditions 1 2 3 4 Actions
Valid Mobile Number Numbers length should be 10 digits Numbers ranging from 1 to 9 Pass
In Valid Mobile Number Numbers start from 0 Numbers start from 1.0 Numbers with +, - or ends +, - Numbers having 000000000 at the end Fail

3) Use Case Testing
Use case testing is a black box testing technique
In Use Case Testing the user performs the test whether the system behaves in the intended way which is designed for the user.
The Use Case Testing will be performed by the user or the customer at the client place before its deployment.
It is performed on how well the system performs in the real time environment.
All the conditions are checked for the valid and the invalid inputs.
All the functionality will be checked based on the inputs provided by the user.
Example:3 Performing the Indian Mobile number inputs
Condition Input Actual Expected Result
Input 10 digits number 4072863866 Accept Accept Pass
Input 9 digit numbers 543675324 Reject Reject Pass
Input numbers starting with 0 0235467421 Reject Reject Pass
Input numbers starting with 1 followed by 000000000 1000000000 Accept Reject Failure

4) LCSAJ Testing
Linear Code Sequence and Jump is a white Box testing technique, which are being performed on the code of the product.
LCSAJ Testing is used to validate the coding of the program from the beginning to the end of the code which is being executed.
It is used to confirm that full statement of coverage is performed.
It is used to confirm that full branch coverage is performed.
It is used to confirm that full function coverage is performed.
It is used to confirm that full condition coverage is performed.
Example : 4 Performing the valid Indian Mobile number from the Inputs
Coverage Statement Branch Function Condition Condition Result
Executed Yes Yes Yes Yes Yes Pass
Not Executed Yes No Yes Yes Yes Failure
Not Executed No No No No No Failure
Not Executed Yes Yes No Yes Yes Failure
Not Executed Yes Yes Yes No Yes Failure
Not Executed Yes Yes Yes Yes No Failure

Task-1

Narasimha Varman J — Sun, 18 Feb 2024 09:53:44 +0000

What is software Testing?
Software Testing is a process of ensuring the designed product is free of bugs which is designed for the intended usage.
Software Testing is carried out on a piece of code block or a program or for a build.
Software testing is normally carried out while designing a product.
Testing is carried out to find the known bugs and the software is free from errors.
Testing can be done simultaneously when a product is designed called unit testing by the developer.
After or during the product is designed testing will be carried out by the tester.
Requirements of Software Testing:
First the requirement for software testing is analysed and documented.
Software testing has Black box testing, white box testing and grey box testing.
Black box testing can also be called as functional testing.
White box testing is implemented during the coding phase by the developer.
White box testing is used to find whether the software is designed as per the requirement.
Grey box testing is a combination of black box and white box testing
Relevance of Software Testing
Software Testing is used to validate and verify whether the designed software performs the expected and the accepted tasks.
Software testing is performed inorder to confirm the software is working properly.
Software testing is performed inorder to prevent the developed product from failing.
If a product confirms the quality standards then it is accepted that the product will perform flawlessly.
Software Testing not only used while developing new products but also during a change in the code or the module of the product.
Software Testing can be classified as smoke testing, sanitary testing, regression testing, performance testing, user acceptance testing and unit testing.