Why Codeless Test Automation Is Dominating QA in 2026?

 Codeless  Test Automation 

 Codeless test automation is transforming the way companies approach software testing by making automation accessible to both technical and non-technical users. Codeless automation testing enables organizations and businesses to deliver user-friendly applications. 

Unlike traditional automation testing, which often requires scripting expertise, codeless platforms provide intuitive drag-and-drop interfaces, reusable workflows, and visual test builders. This allows quality assurance (QA) professionals and even non-technical stakeholders to participate in the testing process. By reducing the dependency on coding skills, companies can improve test creation and deliver high-quality applications in a rapid way.

While complex testing scenarios may still require code-based automation, codeless platforms provide an effective solution for a wide range of functional testing needs, helping organizations improve software reliability, reduce testing costs, and deliver better digital experiences to their customers.

Advantages:

• Supports Agile and DevOps: Codeless test automation integrates seamlessly with CI/CD pipelines, enabling continuous testing, faster feedback, improved software quality, and reliable application delivery.
• No Coding Required: Codeless test automation enables users to create automated test cases using drag-and-drop interfaces and visual workflows, eliminating the need for programming skills.
• Reduced Maintenance Effort: Most codeless automation tools automatically adapt to minor application changes, minimizing test failures and lowering maintenance costs compared to script-based automation.
• Faster Test Execution: It significantly reduces the time required to build, execute, and maintain automated tests, helping teams accelerate software releases.

Disadvantages: 

• Limited Customization: Visual interfaces and background setups restrict deep adjustments, making it hard to handle unique or complex test scenarios.
• Not 100% Codeless:Advanced actions, custom data setups, or complex integrations often still require manual coding or scripting knowledge.
• Scaling and Performance Issues:Large test suites can run slowly or face maintenance challenges as the target application grows and changes.  

How to start Low-Code Test Automation without Coding Experience?

 Low Code Test Automation:

Low-code test automation refers to the process of creating automated tests using tools that require minimal programming knowledge. Instead of writing scripts from scratch, users can design test cases visually through prebuilt components. Various software Tools such as Katalon Studio, TestProject, and Leapwork helps  testing engineers and QA team to create automated test cases with minimal coding knowledge.

Codeless automation is the process of automating software testing or workflows without requiring any programming knowledge. Initially get familiarize with basic software testing concepts such as test cases, test scenarios, bug reports, test plan, SRS and test execution. Select a beginner-friendly automation platform that supports visual test design and built-in integrations. Most  low-code tools also integrate with popular testing frameworks like Selenium to run automated tests on multiple browsers. Practice with sample web applications and gradually explore data-driven testing, test engineers can rapidly build  automation skills for testing an application.

Step by Step Guide:

Step 1: Learn Basic Testing Concepts

Before starting automation, understand basic testing concepts such as:

·         Test cases

·         Test scenarios

•    ReTesting

·         Regression testing

·         Test execution

These fundamentals help you design effective automated tests.

Step 2: Choose a Beginner-Friendly Tool

Select a low-code automation platform that provides visual workflows and easy setup.

Good beginner options include:

·         Katalon Studio

·         Leapwork

·         TestProject

Step 3: Start with Simple Test Cases

Begin with simple automation tasks such as:

·         Login User functionality

·         Form submission

·         Navigation verification

·         Search  Button Functionality

Step 4:  Regular Practice

Practice by automating real applications or demo websites which replicate real world scenarios.

Advantages of Low Code Test Automation:

1.Integration with DevOps: Low-code automation tools integrate with CI/CD platforms like Jenkins, enabling automated testing in continuous integration pipelines.

2.Easy Maintenance: Many low-code platforms include self-healing capabilities that automatically update test scripts when application elements change.

3.Faster Test Creation: Low-code tools allow testers to build automated tests much faster than traditional coding approaches.

What is AI Driven & Autonomous Testing? List Advantages and Disadvantages.

 

Earlier software testing process was more human oriented where testers manually created, designed and executed the tests. The term "AI-Driven & Autonomous Testing" describes the best use of machine learning and artificial intelligence to create, run, manage, and optimize tests with little assistance from humans. AI systems learn from application behavior, previous test results, code modifications, and user input, in contrast to classical automation, which depends on prewritten scripts. When the UI, APIs, or workflows change, they may automatically create test cases, identify trends, and modify tests.

The use of AI in testing can potentially reduce actual testing time by up to 50% also increases defect detection rates by 35% 

Manual and script-heavy testing is unsustainable in 2026 due to fast-paced DevOps, microservices, and AI-powered applications. Continuous quality assurance at scale is made possible by autonomous testing, which also shortens time-to-market and enables QA teams to transition from execution to strategy. It is particularly useful in complicated systems with frequent and erratic change.

As intelligent agents integrated into CI/CD pipelines, autonomous testing systems function. To determine what to test, when to test, and how thoroughly to test, they examine requirements, code commits, logs, and past defects. These systems have the ability to prioritize high-risk areas, self-heal broken tests, and even halt releases when confidence levels decline. Through feedback loops, the AI progressively increases accuracy over time.

Advantages:

• Better Test Coverage – AI explores edge cases humans may miss.
• Risk-Based Testing – Focuses on high-impact and high-failure areas.
• Scalability – Works well with large, complex systems.
• Reduced Human Effort – Minimal scripting and maintenance.
• Self-Healing Tests – Automatically adapts to UI and API changes.

Disadvantages:

• Complexity  – Complex AI and ML integration.
• High Initial Cost – Tools and setup can be expensive.
• Learning Curve  – Teams need AI and data understanding.
• Data Dependency  – Requires high quality historical data.
• Over Reliance Risk  – Human judgement is essential.

Explain Codeless Automation Testing with its Pros and Cons

 

Codeless automation testing is the fastest-growing trends in QA domain today. Codeless automation testing means creating and running automated test cases without writing any code. Codeless automation testing lets users build automated tests through graphical user interfaces.

With the help of AI, Machine Learning and NLP, these tools can now generate, execute, and maintain tests automatically — making test automation accessible to everyone and everywhere.

According to Expert reports, over 50% to 60% of QA teams plan to adopt codeless automation. Tools like Testsigma, testRigor, Opkey, and Leapwork  provide powerful AI-driven testing platforms that accelerate quality delivery and consistency.

How Codeless Automation Testing Works:

Approach	Description	Example
Record & Playback	Record user actions on the app and play them back automatically.	Selenium IDE, Katalon Recorder
Keyword-Driven Testing	Use predefined keywords like “Click”, “Enter Text”, “Verify” to design steps.	TestComplete
Drag-and-Drop Workflows	Visually connect steps using a workflow builder.	Leapwork
Natural Language Processing (NLP)	Create tests using plain English commands.	Testsigma, testRigor, Autify
AI-Assisted Testing	AI automatically identifies elements, creates or heals test scripts.	Opkey

Pros and Cons of Codeless Automation Testing:

Pros:

1.AI powered Efficiency: Modern tools include object recognition, and auto-update capabilities using AI and ML. These reduce test maintenance and improve reliability.

2. Faster ROI: With quicker test development and execution, organizations see faster automation ROI especially in agile or DevOps environments.

3.Enhanced Productivity: Since less time is spent coding and debugging, QA teams can focus more on test design, coverage, and strategic quality improvement.

4.Speedy Test Creation: Codeless tools use drag-and-drop interfaces and visual workflows, allowing tests to be created within rapid time.

5.Programming: No Coding skills are required.

Cons:

1.Costly: Enterprise level codeless platforms can be expensive, especially when adding AI features or cloud testing support.

2.Less Flexible: Codeless tools often struggle with complex test logic.

3.Vendor Lockin Risk: Many platforms use proprietary test models or cloud environments, making it hard to migrate tests if you switch vendors later.

Difference between Selenium and Cypress?

Automation testing tools  play a crucial role in delivering high-quality software with greater reliability.They execute tests on software products automatically, reducing the need for manual intervention. These tools help improve testing efficiency, accuracy, and coverage by running repetitive and complex test cases quickly. 

They support a range of testing types such as functional, regression, and performance testing, allowing teams to identify defects early and accelerate the development cycle. They can be integrated with development environments and continuous integration pipelines.

Top 5 Automation Testing Tools in 2025:

1.Selenium.

2.Playwright

3.Cypress

4.Appium

5.Katalon studio.

	Selenium	Cypress
Ease of Use	Setup is a bit complex as it requires downloading browser-specific drivers	Setup is simple and does not require additional downloads
Browser Support	Supports almost all browsers	Supports Chrome
Video Support	Not supported	Supported
Language Support	Java,Javascript,Python etc	Javascript
Performance	Slow	Fast
Tab Switch	Supported	Not Supported
Architecture	Web driver interacts with browser	Can run test directly in browser

Is Cloud based Testing the future of QA in 2025? What are the benefits and challenges of Cloud based Testing

 

In 2025, cloud-based Testing is very crucial for ensuring rapid software delivery in agile and DevOps workflows. It offers highly scalable, cost-effective access to diverse environments and real devices globally.

Cloud-based Testing helps testing teams test faster, from anywhere, and without spending too much on hardware and other resources. If you're working in software or QA, right now is a great time to learn how cloud testing works and use it in your projects and applications. It’ makes tester job easier, more efficient, and ready for the future.

Traditional testing environments often suffer from lot of scalability issues, higher infrastructure costs, and limitations in accessibility. Cloud testing, however, leverages the power of distributed computing to offer on-demand, scalable, and collaborative environments.

Benefits and Challenges of Cloud based Testing:

Benefits:

Accessibility: Test from anywhere, anytime using internet-based platforms.

Cost Savings: Reduces the need for expensive hardware and on-premises infrastructure.

Scalability: Easily scale test environments up or down based on demand.

Real Device Testing: Access a wide range of devices and browsers via cloud platforms.

Faster Test Cycles: Speeds up continuous integration and continuous delivery (CI/CD).

Challenges:

Security Concerns: Risks related to data privacy, especially with sensitive information.

Compliance Issues: Needs alignment with industry and regional regulations (e.g., GDPR).

Latency & Downtime: Internet-based testing can face slow speeds or outages.

Tool Integration: Some legacy tools may not work well in cloud environments.

Learning Curve: Requires knowledge of cloud platforms and configurations.

 

Top 3 Cloud based Software Testing Tools:

1.BrowserStack:

BrowserStack eliminates the need for in-house device labs by offering on-demand access to real environments. BrowserStack enables quick testing of mobile apps for bug-free releases. App Automate is a product that automates real devices in the cloud. It can replicate actual user conditions using more than native device features like GPS, network simulation, and localization.

2.CloudTest:

CloudTest is a performance and load testing tool designed for web and mobile applications. It allows users to simulate thousands of concurrent users in real time to test scalability and reliability. CloudTest provides real-time analytics dashboards for immediate insights during test execution.

3.LambdaTest:

LambdaTest is a cloud-based testing platform that enables users to perform cross-browser and cross-platform testing of web and mobile applications. It supports manual and automated testing using tools like Selenium, Cypress, and Appium. LambdaTest offers real-time testing on a wide range of browsers, operating systems, and devices.

Differentiate between Data Driven Framework and Keyword Driven Framework

A framework in automated testing is a collection of rules, best practices, and resources used to automate software application testing. Frameworks offer an organised method for effectively creating, managing, and organising automated test scripts. They contribute to increased test coverage, better maintainability, reusability, and reduction of redundancy. 

The purpose of the Data-Driven Framework is to isolate the test data from the test logic. It increases the flexibility and reusability of the tests by enabling the execution of the same set of test scripts using several data sets.

Every action (or keyword) in a test is linked to a particular function in the Keyword-Driven Framework, also called the Table-Driven Framework. The test scripts are constructed in a manner that defines and stores the operations (keywords) in an external file or table.

Data Driven Framework	Keyword Driven Framework
Requires understanding of scripting and handling data files.	Can be used by non-programmers once keywords are defined.
Easier to maintain test data separately	complex with a large number of keywords.
One test script is executed with multiple data inputs.	One test script is executed based on a sequence of keywords.
Best suited for Tests with varying data, such as login scenarios with different credentials.	Best suited for Tests with standard actions (e.g., opening a browser, clicking buttons).
Test data is stored separately (e.g., Excel, CSV).	Test steps (keywords) are stored in a data table (e.g., Excel, CSV).
Test scripts are written to handle data inputs.	Test scripts are written to handle keywords (actions).
High reusability by reusing the same test script with different data.	High reusability by reusing the same keywords across multiple test cases.

Top 5 Testing Challenges in Salesforce

Salesforce is a most famous and widely used Customer Relationship Manager(CRM).Salesforce testing is unquestionably a crucial component of the QA team. It is a multi-layered ecosystem of  tools that can be customised to fit an endless number of use cases, in addition to being a very popular CRM solution.

Testing in Salesforce application can present unique and complex challenges. 

The top 5 Testing challenges in Salesforce Applications:

1.Integration with Third Party Applications:

Salesforce's ability to integrate with third-party apps, ranging from data storage options to marketing automation tools, is one of its most significant features. To make sure that systems operate correctly and that the client experience is uninterrupted, testing these integrations are essential. Integration testing is an ongoing and essential component of the testing process since changes made to one system frequently affect other applications.

2.Frequent Updates and Releases:

With frequent upgrades and the introduction of new features, Salesforce is a platform that is always changing. This implies that regular testing is necessary to make sure the system is operating as intended.

3.Data Security and Privacy:

Thorough security testing will be a primary priority because cyber threats and data breaches remain serious issues. Companies will concentrate on carrying out thorough security audits in order to find weaknesses in their Salesforce apps and safeguard private client information.Salesforce handles private client and business information in highly regulated sectors. As a result, privacy and security are important factors. To protect their Salesforce environments from attacks, data breaches, and unwanted access, organisations need to implement stringent security testing procedures and perform frequent security audits.

4.Complex Applications:

Basic Salesforce settings may be simple to test, but more intricate setups will be more difficult. Think of a platform similar to Visual force, where developers create unique user interfaces for web or mobile applications. Because you need full coverage, testing this can be somewhat challenging.

5.Data Migration:

Data transfers to or between Salesforce instances are essential processes that need to be managed precisely and carefully. Operational problems brought on by poor data quality may result in lost revenue, harm to one's reputation, and occasionally even expensive fines. Data consistency and integrity are guaranteed by thorough testing during data movement.

 

What is the role of Test Manager in Agile Projects?

 The ways that waterfall and agile approaches organize, manage the teams and communicate are different. Test teams in traditional waterfall models are managed by a test manager and kept apart from the development team. The test manager would normally allocate work, oversee progress in meetings, evaluate and approve estimates, and offer technical advice.

 Test Manager's role adapts in Agile environments:

1.Collaboration and Communication:

Cross-functional Team Member: Ensures that requirements and quality standards are understood clearly by collaborating closely with developers, product owners, and other stakeholders.

Facilitator: Assists team members in communicating with one another to resolve problems, make requirements clear, and guarantee that testing objectives are being met.

2.Test Planning and Strategy:

Adaptive test planning creates adaptable test techniques that can adjust to shifting priorities and requirements. Agile test plans are iterative and more dynamic.

Test Coverage: Works with the team to identify important areas for testing, such as functional, non-functional, and exploratory tests, in order to ensure thorough test coverage.

3.Test Execution and Automation:

Test Case Execution Oversight: Ensures that manual and automated test cases are carried out in accordance with Agile sprints and iterations.

Automation Advocate: Encourages and backs automated testing where it makes sense, incorporating it into the continuous integration and delivery (CI/CD) pipeline to facilitate frequent and quick releases.

4. Continuous Improvement:

Feedback Loop: Utilizes feedback from test results and team retrospectives to continuously improve testing practices and processes.

5. Risk Management:

Risk Identification: Identifies and manages risks related to software quality and testing. Works with the team to address potential issues early in the development cycle.                                            Contingency Planning: Develops contingency plans for addressing critical issues or delays that may impact the project timeline or quality.

What is API Testing? Types of API Testing

 API(Application Programming Interface) Testing is the process of sending request to an API with or without test parameters and verifying the response.It is basically an interface testing.This type of testing involves sending requests to the server and analyze the response for its correctness.

Types of API Testing:

The different types of API testing are:

1.Security Testing:It is the process of checking the vulnerabilities in API.The security testing identifies the flaws in the infrastructure such as weak passwords,default credentials.It identifies the security vulnerabilities in the software application.It is one of the important API testing type.

2.Functional Testing:This testing ensures that the newly added functionality and the existing functionality works correctly as per requirement.It can be performed by sending requests and validating the responses.

3.Performance Testing:This type of testing is performed to ensure that application handles large volumes of data without impacting the performance of an application.The different parameters considered for measurement are throughput and response time along with uptime.

4.Reliability Testing:It ensures API can produce correct and consistent results and the connection between client and server is reliable when sending the request from the client and receiving the response from the server.

Benefits of API Testing:

• GUI independent testing.
• Early validations.
• Enhance security by checking API authentication.
• Reduced testing cost.
• Better Integration.

Tools for API Testing:

The different tools that can help perform API testing are:

• Postman.
• SoapUI.
• Swagger.
• API Fortress.
• SOAtest.

How to write a good and effective Bug Report

Bug Reporting is an important and most essential part of a software testing activity. It provides information about an issue in an application or product. An effective bug report  can help address the issue. It can include various parameters like Title, Bug  description ,Steps to reproduce and many more. Bug report also assist the development team.

For the development team to address a bug precisely and on time, effective bug reporting is necessary. A well-written bug report should be clear, detailed, and easy to read.

How to write a good and effective Bug Report:

Following steps can help to write an effective bug report:

1.Attempt to replicate the bug clearly.

2.Gather environmental data like the Operating system, browser, application software, tools if any.

3.Insert exact steps  to reproduce the bug.

4.Attach screenshots, images or videos for clear understanding.

5.Clearly highlight the expected result which is deviating from the actual result.

6.Add any relevant information required to understand the bug and its severity.

What does a bug report consist of ?

1.Bug ID:A unique number generated by the bug reporting software.

2.Title:Brief and precise information about the bug.

3.Environment:Specify the exact environment details like operating system,browser type,software application version,hardware details.

4.Steps to reproduce:Clearly provide a step by step guide to reproduce the bug.

5.Expected Result:Clearly specify the expected result as per the business requirements or functional requirements.

6.Actual Result: Write the actual result which the software application produced.

7.Severity: Specify the level of severity considering the impact.

Switching from Manual to Automation Testing Career

Transiting from Manual Testing to Automation Testing has been a need of time.Automation Testing offers lot of advantages over Manual Testing.Manual Testers familiar with some programming languages like Java,Python can easily migrate into Automation Testing.

Manual Testing is performing all the testing activities without the help of third party tool.Hence can prove to be time consuming.Automation Testing on other hand is the testing performed with the help of third party tools like Selenium,QTP etc. 

Switching the role from Manual to Automation Testing requires dedication and continuous learning.

Following are some of the guidelines one can follow :

1.Get familarize with some basic programming concepts.Learn the core concepts of languages like Java,Python to easily understand  automation tools like Selenium ,Appium and Cypress.Understand the importance of tool ,its features and limitations.Online tutorials and free courses can help gain hands on practical knowledge and frameworks of these tools.

2. Next Seek opportunities in your current organization and assist the automation teams to gain real time knowledge.Demonstrate your interest in learning new technologies and tools.Understand and build the frameworks.

3.Join online testing communities and forums where you can get insights about latest updations in the field of automation testing.Improve your engagement with automation testers so that they can offer guidance and mentorship.

4.Tailor your resume on job portals like Naukri,Sine and LinkedIn with newly learned testing tools.

5.Consider to enroll yourself in certification testing programs if any.Certification offers added advantage to resume.

What is Continuous Integration (CI) and Continuous Delivery (CD), and how do they relate to automation testing?

 Continuous Integration and Continuous Delivery are the set of practices that development teams use to handle code changes in reliable and efficient way.It is generally used by Devops team.Continuous  Integration is a practice of automating the integration of code. Continuous Delivery is a process carried away after Continuous Integration to make sure we can release the new changes error free to the customer.

Benefits of CI/CD:

1.Risk Reduction:It reduces the risk of major failures and downtime as continuous deployment process allows developer to fix issues early.

2.Quality Improvement:It improves the overall quality of software.Automated testing in CI/CD pipelines helps identify bugs, regressions, and integration issues early in the development cycle.

3.Enhanced Security:Security updates and patches can be applied more quickly.

4.Increased Collaboration: CI/CD promotes collaboration among development, testing, and operations teams.

5.Rollback and Recovery:CI/CD pipelines include rollback mechanisms allowing the user to revert to previous version of application.

Automation Testing and CI/CD:

Automation Testing in CI:

Unit,Integration and other types of testing are executed automatically whenever any changes in code are integrated.In case of failure CI can block thecode integration process.

Automation Testing and CD:

Automation testing can be performed for system testing and user acceptance testing.It can also perform security testing and non functional testing.

Thus automation testing plays a vital role in CI/CD process.

AI's Impact on Software Testing: A Beginner's Path to Efficiency and Smarter Software Testing

Software Testing plays a vital role in software development process. Artificial Intelligence can be a game changer in software testing or quality assurance field. As a beginner in software testing, it's crucial to explore and adopt AI-driven testing solutions to stay competitive in this rapidly evolving field.

In this blog post, we'll explore the transformative effects of AI in software testing and how it can benefit newcomers to the world of testing and quality assurance.

1.Efficient Testcase Generation:

One of the most time-consuming tasks in software testing is the creation of test cases. AI can assist beginners by generating test cases based on various parameters and specifications. These AI algorithms analyze the application's behavior and identify potential areas of concern, making it easier for testers to cover critical test scenarios.

2.Enhanced Test Automation

For beginners in software testing, test automation can be a challenging but essential aspect of their work. AI-driven test automation tools have revolutionized this space. These tools can automatically create and execute test cases, significantly reducing the manual effort required. Beginners can leverage AI-driven automation to quickly identify bugs and issues, allowing them to focus on more complex testing scenarios.

3.Early Detection of Bugs

AI-powered anomaly detection can help beginners identify irregularities or issues within the software early in the development process. By continuously monitoring the application's behavior, AI can quickly flag deviations from expected patterns, enabling testers to address potential problems before they escalate.

4.Enhanced Test Reporting

For beginners, reporting and communicating test results effectively can be a daunting task. AI can simplify this process by automatically generating comprehensive test reports. These reports can include detailed information about test coverage, bug tracking, and overall test quality, making it easier for testers to convey their findings to development teams..

5.Reduced Testing Costs

Cost-effectiveness is a critical concern for both newcomers and established professionals in software testing. AI-driven testing tools can significantly reduce testing costs by automating repetitive tasks and optimizing resource allocation. This allows beginners to work more efficiently and maximize the value they provide to their organizations.

What is Shift Right Testing?

 Shift-Right Testing is a testing approach which focuses on gathering feedback from the production environment to improve the current testing process.It is basically performing the testing later once code is deployed in production environment.It is also referred as Testing in Production.

Combining right shit testing and left shift testing can give better results that helps to improve the performance and user satisfaction.This approach is mainly used in Devops. By incorporating real-world feedback and monitoring data, organizations can improve the quality, reliability, and performance of their software applications thus resulting in great user satisfaction.

Benefits of Shift Right Testing:

1.Continuous Improvement: The information gathered through Shift-Right Testing is used to continuously improve the software development process, testing strategies, and overall quality of the application.

2.Production Monitoring: The application is actively monitored in the production environment to detect any anomalies, performance issues, or other issues that might not have been identified during development or traditional testing phases.

3.Feedback: Feedback from end-users and other stakeholders is collected to identify potential issues or areas for improvement. This can be done through feedback channels, customer support tickets, user surveys, or social media monitoring.

Types of Shift Right Testing:

1.Fault Injection Testing:Purposely introducing errors into  software to see how it performs.

2.A/B testing: Two versions of the same features are released to test the responses and identify which version works better.

3.Canary Testing:It is a testing approach in which we test a new software version in production environment by pushing some code changes. 

What is Xpath in Selenium?

XPaths in Selenium:

Selenium is a popular tool for automating web browsers, and it supports XPath as a way to locate elements on a web page. XPath is a powerful tool for selecting elements and data from an XML or HTML document, and it's widely used in development and testing.XPath is an important and core component of XSLT standard. It is used to traverse the elements and attributes in an XML document.

XPath is a language used to select elements in an XML or HTML document. XPath is used to locate elements on a web page. Selenium provides a find_element_by_xpath() method that allows you to locate an element using an XPath expression. We can select elements based on their attributes, their position in the document hierarchy, or their relationship to other elements.

Syntax:

1.Launching a web browser

driver = webdriver.Chrome()

2.Navigate to a web page:

driver.get('https://example1.com')

3.Locate an element using XPath:

element = driver.find_element_by_xpath('//tagname[@attribute="value"]'

where

The XPath expression consists of the following components:

• tagname: The name of the HTML tag of the element you want to select. For example, div, a, input, etc.

• @attribute: The name of the attribute you want to use to select the element. For example, class, id, name, value, etc.

• "value": The value of the attribute you want to use to select the element.

4.Locate an element with class attribute:

//div[@class='topic']

where 

// selects any element in the document hierarchy.

div selects all div elements.

[@class='topic'] selects only div elements that have a class attribute equal to "topic".