What is Manual Testing

Manual testing is a technique to test the software that is carried out using the functions and features of an application. In manual software testing, a tester tests the software by following predefined test cases. In this testing, testers make test cases for the codes, test the software, and give the final report about that software. Manual testing is time-consuming because it is done by humans, and there is a chance of human errors.

Every new application must be manually tested before its testing can be automated. Manual Testing requires more effort than automation testing but is necessary to check automation feasibility. There is no requirement for knowledge of any testing tool in manual testing.

Q. What is Testing?

-Testing is the process in that we have to check given software or application is generating desired output or not.

Q. What is Software Testing?

- Software Testing is the process of checking the completeness and correctness of the software with respect to customer expectations.

-Software Testing is an activity to detect and identify the defects in the software.

-The main purpose of testing is to release quality product to the client.

Q. Why there is a need of Testing?

-The objective of Testing is, we have to deliver high quality, reliable and efficient product to the customer

-It is a systematic and disciplined approach that aims to identify and rectify defects, errors, and potential issues within the software during its development lifecycle

-The primary goals of software testing are to validate the software’s functionality, enhance its performance, and improve the overall user experience.

Playwright:

Playwright is an open-source framework for automating and testing web applications across Chromium, Firefox Due to its cross-browser support, fast execution, and robust API, it enables reliable Playwright testing across modern browsers and platforms.

Key Features of Playwright

Below are some of the key features of the Playwright testing tool

1.     Cross Browser Testing: Playwright supports all major browsers out of the box, including Chromium, Firefox, and WebKit (Safari). This cross-browser support allows you to write tests once and run them across multiple browsers without any additional configuration or setup. Playwright ensures consistent behaviour and API across all supported browsers, making it easier to maintain and scale your test suite. Playwright provides built-in support for device emulation using browsers like Safari and Chrome.

2.     Headless and Headful Modes: Playwright allows you to run tests in headless mode (without a visible browser window) or headful mode (with a visible browser window). Headless mode is useful for running tests in CI/CD pipelines. Headful mode is beneficial for debugging, visual inspection, or when you need to interact with the browser during test execution.

3.     Automatic Waiting: Playwright automatically waits for elements to be ready before interacting with them, reducing the risk of test flakiness caused by timing issues. It employs intelligent waiting strategies, such as waiting for network requests to complete or DOM mutations to occur, ensuring that tests are executed reliably and consistently.

4.     Network Interception: Playwright provides powerful network interception capabilities, allowing you to intercept and modify network requests and responses during test execution. This feature is useful for testing scenarios involving APIs, mocking responses, simulating network conditions, or bypassing authentication mechanisms.

5.     Multiple Contexts: Playwright allows you to create multiple browser contexts within a single test run, effectively simulating different user sessions or environments. This feature is particularly useful for testing scenarios involving multi-user interactions, such as chat applications or collaborative tools.

6.     Powerful Selectors: Playwright offers a rich set of selector strategies, including CSS selectors, XPath, text selectors, and more. It also provides advanced selector options, such as handling dynamic elements, selecting elements based on their visibility or accessibility, and selecting elements within iframes and shadow DOMs, which are common in modern web applications.

7.     Screenshot and Video Capture: Playwright enables you to capture screenshots and record videos of your test runs with a single line of code. This feature is invaluable for debugging, visual regression testing, and generating visual artifacts for documentation or reporting purposes.

8.     Isolation and Parallelism: Playwright provides built-in support for running tests in isolation and in parallel. Test isolation ensures that each test run is independent and doesn’t interfere with other tests, preventing state pollution and improving test reliability. Parallel test execution can significantly speed up your test suite by utilizing multiple CPU cores or machines, reducing overall test execution time.

API Testing:

An API is code that enables the communication exchange of data between two software programs. An application typically consists of multiple layers, including an API layer. API layers focus on the business logic in applications, defining requests such as how to create them and the data formats used.

API-Application Programming Interface

-API is use to communicate between two systems

-It is simply known as sending the request from one system to another and getting the required response

-Ex: communication between IRCTC and OTP ,Here we send request from IRCTC app to get the response as OTP

microservices

SYSTEM-2

-In API Developer already created a Replica’s of Micro services which helps to increase the performance of the system by sharing the request with replicas in case of load on system 2 increases ,Here API will decide how much load to be shared with each micro services and replicas

-As this balances the load ,the performance will get automatically increases

-API helps in data hiding

-API helps for proper communication between two systems

-when first system is sending the request to second system ,the request should go for second system only not the third one

-Ex: user wants to do a payment for Amazon order by using Gpay app then the payment request should go for Gpay only

-This is nothing but the proper communication process ,API will provide API layer for security purpose

-API also checks and authenticates the data which we are passing

-API tests core functionality

-API is time effective

-we can hit lot of API’s at a time with less time

-Language Independent

-API is language independent i.e. API reads multiple languages like XML, JSON,HTML,TEXT etc

-Easy interaction with GUI

 Do visit our channel to know more: SevenMentor

Author:-

Laxmi Kamble