Siddharth Dubey

QA report. For H1 of 2024. Top 3 automation QA tooling: 🔺 Selenium 🔺 Cypress 🔺 Playwright Top 3 QA methodologies: 🔺 Regression testing 🔺 E2E testing 🔺 Unit testing Top 3 QA hacks: 🔺 Host testing parties before major releases 🔺 Integrate QA into CI/CD 🔺 Aim for 80% automation test coverage Insights from managing QA for dev teams of 5-50.

53

9 Comments

Selenium and Framework Level Interview Questions, Exp: 3 to 8 yrs What is the difference between Page Object Model and Page Factory? Page Object Model (POM):  POM is a Selenium design pattern; we can see it as a repository where we store all the WebElements. This has become very popular in industry these days, because it is very easy to manage, reusability of code and eliminates duplication of code.  The key benefit if UI changes in the future, then we can update WebElements to Page Classes in POM or Object Repository accordingly Page Factory: Page Factory in Selenium WebDriver is an integrated concept or API. Here we follow again the same principle of keeping repository objects or page classes separate from test classes. Here we use @FindBy to find elements and to initialize WebElements using initElements process. What are all the locators that support selenium? Name: Same as ID although it is not unique CSS Selector: Works on element tags and attributes XPath: Searches elements in the DOM, Reliable but slow Class name: Uses the class name attribute TagName: Uses HTML tags to locate web elements LinkText: Uses anchor text to locate web elements Partial Link Text: Uses partial link text to find web elements
ID- How To Overcome StaleElementReferenceException in Selenium? The reference to an element is now "stale"; the element will no longer appear on the page's DOM. In simple words, when you started interacting with it, the element you located using the findElement method disappeared. Add exception handling to your action and, if the exception is stale, try to locate the element after a simple wait for 500 milliseconds and repeat these actions until the action or max iterations have been successful. How to access the CSS selector using the nth element? Here is a syntax for using the CSS selector to access the nth attribute:  <type>:nth-child(n) Ex:  tr:nth-child(2) How to handle alerts in Selenium WebDriver? WebDriver provides an API to handle alert dialogs.  Alerts cannot able to inspect if there is no Alert in the screen, you will get ‘NoAlertPresentException’ The Alert interface contains a number of APIs to execute different actions.  The following list: Alert alert = driver.switchto().alert(); alert.accept(); This is equivalent to the OK button action on the dialog alert.dismiss(); This is equivalent to clicking on the CANCEL action button alert.sendKeys("String"); This will allow to type in some text into the alert  alert.getText(); This will return the text that appears on the dialog -x-x- Get complete list of interview questions answers with Job shortlisting strategies (paid): https://lnkd.in/gJKiRCnB Follow me on Medium to stay sync in Technical QA/Automation Content: https://lnkd.in/dCDi84Q9 #japneetsachdeva

305

15 Comments

8 Types of API Tests every SDET should know! . 1) Smoke Tests: Validating bare minimum crucial API calls are working for application. Tools: Postman, Swagger, Manual Tests 2) Functional Tests: Validating each API for its prominent functionality. Like Post requests for data creation and validating in Database whether data sent is created in right table, structure etc. Tools: RestAssured, Locust, Gatling, Requests, Postman with manual Db validation etc. 3) Integration Tests: Validating multiple requests in sync like calling Post rqst and then Get rqst to validate whether data is created or not. Tools: Postman, Requests, RestAssured, Locust etc. 4) Load Tests: Validating the load capacity of APIs. This is crucial when user footfall increases. Tools: JMeter, LoadRunner, Locust, Gatling etc. 5) Stress Tests: Breaking the APIs. This helps to know about the threshold. Tools: JMeter, LoadRunner, Locust, Gatling etc. 6) Security Testing: Validating external threats if any for APIs. Tools: Pynt, OWASP top 10 vulnerabilities with BurpSuite etc. 7) Fuzz Tests: Validating APIs and servers with sending unexpected data and validate the response received. Tools: Postman, Requests, RestAssured etc. 8) Regression Tests: Validating new changes made in application or APIs should not break existing functionality. Tools: Postman, Requests, RestAssured etc. -x-x- Become SDET & Future SDET Manager + 950+ Q&A Bank, Hero in Gen AI, Job techniques, Interview Prep Q&A Bank: https://lnkd.in/gusymgFi My ATS friendly Resume used to crack 133+ organizations: https://lnkd.in/g9697hy6 #japneetsachdeva

156

7 Comments

Here's how to boost your test automation in 3 steps. Using Playwright Test automation. Playwright Test automation is revolutionizing QA. But many still struggle with reliability. 1. Leverage Cross-Browser Testing ↳ Playwright supports Chromium, Firefox, and WebKit. ↳ Ensure consistent performance across all browsers. ↳ Identify browser-specific issues early. 2. Utilize Auto-Wait Mechanism ↳ Reduces flaky tests. ↳ Automatically waits for elements to be actionable. ↳ Increases test reliability and stability. 3. Adopt Sharding Mode ↳ Run tests without a browser window. ↳ Perfect for CI/CD pipelines. ↳ Speeds up test execution. How I improved our QA efficiency: 1. Integrated Playwright for cross-browser coverage. 2. Reduced test flakiness by 30% with auto-wait. 3. Boosted CI/CD performance with headless mode. I'm writing a detailed Playwright tutorial to help you get started. DM me if you're interested—I’ll send the draft to early adopters. Adopt these strategies to elevate your QA game. Automate smarter, not harder.

1

What's lacking in every QA and SDET that I have interviewed in 2024? . . Not having a QA mindset! Every QA now just wants to work in automation, but why? Do you think developing test automation frameworks will improve your skill? OR having created automation will help you step up the ladder of salary and designation more quickly? No, it doesn't work like this! After interviewing so many candidates I can clearly say, You don't know how to create a Test Strategy, Test Scenarios, Proper Test coverage, Not able to evaluate a system as a End-User, No basic knowledge of concepts like when and where to implement automation? etc. If you are going to give an interviews just by doing "rattafication" then you will not be able to progress your career. QA is not automation only! Also specifically mentioning, showing unwillingness to test the system during development phase and only to work in automation can make you rejected in lots interviews. Lot's of product based organization primarily focus on Shift left manual testing and they don't care about automation. Learning trending technologies is useful but shifting your focus from importance of Quality is going to hamper your growth. Every aspect of Software is judged by its Quality. If you cannot improve it quality then Learning Automation is not going to lead you anywhere. I have seen QA's earning more then 85 LPA INR that too in India. There definitely will be people having much better salaries too. So improve your skills even though its Manual QA. Both are equally important :) Follow for more: Japneet Sachdeva -x-x- Learn and use lots of QA, Automation, API, Docker, SQL, Maven, CI_CD and many more complete questions with answers (paid): https://lnkd.in/gSU-m2F7 Crack Test Automation Interviews using JAVA, Master Package for Clearing QA Automation Interviews: https://lnkd.in/g5hr9bea #japneetsachdeva #falsehopes #sdet

275

13 Comments

Best Practices for Writing Assertions in Selenium Effective assertions are the backbone of reliable automated tests. They verify that your application behaves as expected. Here are some best practices for writing clear and meaningful assertions in Selenium: 1. Use Descriptive Messages: Always include a message in your assertions to provide context when a test fails. This helps in quickly identifying the issue. Assert.assertEquals(actualTitle, expectedTitle, "Page title does not match"); 2. Assert Early and Often: Place assertions immediately after the action they are verifying. This makes it easier to pinpoint the exact location of failures. driver.findElement(By.id("submitButton")).click(); Assert.assertTrue(driver.findElement(By.id("successMessage")).isDisplayed(), "Success message is not displayed"); 3. Avoid Hard-Coded Values: Use constants or variables for expected values to make your tests more maintainable. final String expectedTitle = "Home - My Application"; Assert.assertEquals(driver.getTitle(), expectedTitle, "Page title does not match"); 4. Combine Assertions Logically: Group related assertions together to provide a comprehensive validation of a feature or functionality. Assert.assertTrue(element.isDisplayed(), "Element is not displayed"); Assert.assertEquals(element.getText(), "Expected Text", "Element text does not match"); 5. Use Soft Assertions When Needed: Soft assertions allow tests to continue execution even if one assertion fails, reporting all failures at the end. SoftAssert softAssert = new SoftAssert(); softAssert.assertTrue(element.isDisplayed(), "Element is not displayed"); softAssert.assertEquals(element.getText(), "Expected Text", "Element text does not match"); softAssert.assertAll(); // Reports all failures 6. Keep Assertions Simple and Focused: Each assertion should check a single aspect of the application to make failures easier to diagnose. Assert.assertTrue(driver.getTitle().contains("Dashboard"), "Page title does not contain 'Dashboard'"); By following these best practices, you can ensure that your assertions are clear, reliable, and easy to maintain, leading to more robust automated tests. How do you write effective assertions in your tests? #Selenium #TestAutomation #Assertions #SoftwareTesting #QA #BestPractices

4

1 Comment

Selenium and Framework Level Interview Questions, Exp: 3 to 8 yrs Q1) What is the difference between Page Object Model and Page Factory? Page Object Model (POM): POM is a Selenium design pattern; we can see it as a repository where we store all the WebElements. This has become very popular in industry these days, because it is very easy to manage, reusability of code and eliminates duplication of code. The key benefit if UI changes in the future, then we can update WebElements to Page Classes in POM or Object Repository accordingly Page Factory: Page Factory in Selenium WebDriver is an integrated concept or API. Here we follow again the same principle of keeping repository objects or page classes separate from test classes. Here we use @FindBy to find elements and to initialize WebElements using initElements process. Q2) What are all the locators that support selenium? Name: Same as ID although it is not unique CSS Selector: Works on element tags and attributes XPath: Searches elements in the DOM, Reliable but slow Class name: Uses the class name attribute TagName: Uses HTML tags to locate web elements LinkText: Uses anchor text to locate web elements Partial Link Text: Uses partial link text to find web elements
ID- Q3) How To Overcome StaleElementReferenceException in Selenium? The reference to an element is now "stale"; the element will no longer appear on the page's DOM. In simple words, when you started interacting with it, the element you located using the findElement method disappeared. Add exception handling to your action and, if the exception is stale, try to locate the element after a simple wait for 500 milliseconds and repeat these actions until the action or max iterations have been successful. Q4) How to access the CSS selector using the nth element? Here is a syntax for using the CSS selector to access the nth attribute: <type>:nth-child(n) Ex: tr:nth-child(2) Q5) How to handle alerts in Selenium WebDriver? WebDriver provides an API to handle alert dialogs. Alerts cannot able to inspect if there is no Alert in the screen, you will get ‘NoAlertPresentException’ The Alert interface contains a number of APIs to execute different actions. The following list: Alert alert = driver.switchto().alert(); alert.accept(); This is equivalent to the OK button action on the dialog alert.dismiss(); This is equivalent to clicking on the CANCEL action button alert.sendKeys("String"); This will allow to type in some text into the alert alert.getText(); This will return the text that appears on the dialog -x-x- Get complete list of interview questions answers with Job shortlisting strategies (paid): https://lnkd.in/gJKiRCnB Follow me on Medium to stay sync in Technical QA/Automation Content: https://lnkd.in/dCDi84Q9 #japneetsachdeva

269

13 Comments

Selenium and Framework Level Interview Questions, Exp: 3 to 8 yrs Q1) What is the difference between Page Object Model and Page Factory? Page Object Model (POM): POM is a Selenium design pattern; we can see it as a repository where we store all the WebElements. This has become very popular in industry these days, because it is very easy to manage, reusability of code and eliminates duplication of code. The key benefit if UI changes in the future, then we can update WebElements to Page Classes in POM or Object Repository accordingly Page Factory: Page Factory in Selenium WebDriver is an integrated concept or API. Here we follow again the same principle of keeping repository objects or page classes separate from test classes. Here we use @FindBy to find elements and to initialize WebElements using initElements process. Q2) What are all the locators that support selenium? Name: Same as ID although it is not unique CSS Selector: Works on element tags and attributes XPath: Searches elements in the DOM, Reliable but slow Class name: Uses the class name attribute TagName: Uses HTML tags to locate web elements LinkText: Uses anchor text to locate web elements Partial Link Text: Uses partial link text to find web elements
ID- Q3) How To Overcome StaleElementReferenceException in Selenium? The reference to an element is now "stale"; the element will no longer appear on the page's DOM. In simple words, when you started interacting with it, the element you located using the findElement method disappeared. Add exception handling to your action and, if the exception is stale, try to locate the element after a simple wait for 500 milliseconds and repeat these actions until the action or max iterations have been successful. Q4) How to access the CSS selector using the nth element? Here is a syntax for using the CSS selector to access the nth attribute: <type>:nth-child(n) Ex: tr:nth-child(2) Q5) How to handle alerts in Selenium WebDriver? WebDriver provides an API to handle alert dialogs. Alerts cannot able to inspect if there is no Alert in the screen, you will get ‘NoAlertPresentException’ The Alert interface contains a number of APIs to execute different actions. The following list: Alert alert = driver.switchto().alert(); alert.accept(); This is equivalent to the OK button action on the dialog alert.dismiss(); This is equivalent to clicking on the CANCEL action button alert.sendKeys("String"); This will allow to type in some text into the alert alert.getText(); This will return the text that appears on the dialog -x-x- Get complete list of interview questions answers with Job shortlisting strategies (paid): https://lnkd.in/gJKiRCnB Follow me on Medium to stay sync in Technical QA/Automation Content: https://lnkd.in/dCDi84Q9 #japneetsachdeva

238

7 Comments

Such a nice question for Automation Engineer: How to implement reusable wait method for dynamic element using Fluentwait at framework level in Selenium? Instead of asking implement customize arraylist, hashmap, If interviewer ask questions like above, we will have lot of scope for learning from interviews. #AutomationEngineer

21

8 Types of API Tests every SDET should know! . 1) Smoke Tests: Validating bare minimum crucial API calls are working for application. Tools: Postman, Swagger, Manual Tests 2) Functional Tests: Validating each API for its prominent functionality. Like Post requests for data creation and validating in Database whether data sent is created in right table, structure etc. Tools: RestAssured, Locust, Gatling, Requests, Postman with manual Db validation etc. 3) Integration Tests: Validating multiple requests in sync like calling Post rqst and then Get rqst to validate whether data is created or not. Tools: Postman, Requests, RestAssured, Locust etc. 4) Load Tests: Validating the load capacity of APIs. This is crucial when user footfall increases. Tools: JMeter, LoadRunner, Locust, Gatling etc. 5) Stress Tests: Breaking the APIs. This helps to know about the threshold. Tools: JMeter, LoadRunner, Locust, Gatling etc. 6) Security Testing: Validating external threats if any for APIs. Tools: Pynt, OWASP top 10 vulnerabilities with BurpSuite etc. 7) Fuzz Tests: Validating APIs and servers with sending unexpected data and validate the response received. Tools: Postman, Requests, RestAssured etc. 8) Regression Tests: Validating new changes made in application or APIs should not break existing functionality. Tools: Postman, Requests, RestAssured etc.

35

QA Struggles 1on1: writing Smoke vs Regression suites. One of the most frustrating activities of a Manual QA tester is the task of writing, creating from a decisional position the Smoke/Regression suite. Reasons which make it difficult: 1. The pressure of having to be sure that the information adds testing coverage according to the suites nature. a. Smoke suites don't have to be very long and have to cover the core functionality. b. Regression suites are made up from a wide spectrum of testcases with different use-cases. 2. What to do when the app is feature heavy-loaded and the Smoke Suite exceeds a what you would call a Smoke Suite. 3. The better the code-coverage is the better your suite is, meaning less negative financial impact towards the company and less risks. What to do: - No matter which of the two suites you are tasked with providing be it Smoke or be it Regression always treat the idea of how much should you write in it as follows: a. Look at each feature as it were you are looking at a component for example: a searchbar". In doing so the QA has to discuss with the team in order to learn the inner-parts of the code and get used with the platform. b. Treat the core functionality of each component as part of the Smoke Suite. c. Treat all the rest of the scenarios from the core functionality as part of the Regression Suite. Why to do so? Why not to be scared of micro-manage your components? --- Because Smoke and Regression suites always go hand-in-hand with one another. There is no Sprint without executing a Smoke and a few days after a Regression Suite. This happens before delivering (demo meeting) the sprint's activity. By proceeding as such you have a lot of power when it comes with dealing with coverage, how much is too much and how much is too little? And also keep in mind that even if in doing so you find it hard to control the suites contents, then it's probably because the routine or procedures regarding the mandatory need of executing these suites per sprint in the presented order is not fulfilled and you don't have the assurance that you will actually tests those in a couple of days. Thank you for investing in yourself! #qa #newsfeed #news #invest #time #suites #development #java #C# #javascript #python #information #understanding #business #career

1

#Selenium #Training #New #Batch Register : https://t.ly/kRNPk The popularly asked question in SDET interviews - What is the need of an interface when abstraction can be achieved from an abstract class? To solve the #DiamondProblem. What is Diamond Problem ? Java does not allow is multiple inheritance where one class can inherit properties from more than one class. It is known as the diamond problem. In the below code template, we find that class C is trying to inherit form class B and class A, that is not allowed in Java. Class A { } Class B { } Class C extends A,B { } Solution for Diamond Problem : The solution to the diamond problem is default methods and interfaces. We can achieve multiple inheritance by using these two things. Why interface is widely used : 1. The interface is not only about abstraction. 2. If the functionality we are creating will be useful across a wide range of objects, team prefers to use an interface . 3.The main advantages of interface over abstract class is to achieve multiple inheritance. We may not solve diamond problem using class / abstract class. 4. Interface is more flexible than abstract class because one class can only "extends" one super class, but "implements" multiple interfaces.

228

6 Comments

What kind of APIs can you explore & understand before getting into SDET interviews? 1) Web APIs: These are used to enable communication between web servers and clients. For instance, the Twitter API allows developers to access and interact with Twitter's features, such as retrieving tweets or posting new ones. 2) Operating System APIs: These provide an interface for applications to interact with the underlying operating system. The Windows API, for instance, allows software to access various functionalities of the Windows operating system, like creating windows, managing files, and controlling hardware devices 3) Database APIs: These allow applications to communicate with databases. The Java Database Connectivity (JDBC) API enables Java applications to interact with various databases using a standardized interface. 4) Library APIs: Programming libraries often come with APIs that provide predefined functions and classes. The Python Standard Library, for example, offers various modules with APIs for tasks like file handling, networking, and data manipulation. 5) Remote APIs: These enable remote control of devices or services. The remote API of a smart home system might allow a mobile app to control lights, thermostats, and security cameras from a distance. 6)Third-Party APIs: Many companies offer APIs to allow developers to integrate their services into other applications. The Google Maps API lets developers embed interactive maps into their websites or apps. -x-x- Learn & Use GEN AI, API Testing, Automation & more using an updated course for SDETs: https://lnkd.in/gusymgFi Test Automation Engineer Quiz, Exp: 3 to 8 yrs: https://lnkd.in/gHTH3K_g #japneetsachdeva

80

2 Comments

this is too easy. lets make it a bit more difficult. Q: What are the top 5 disadvantages of Selenium? Q: What are the top 5 disadvantages of TestNG?

14

4 Comments

Maintaining test scripts in Selenium can be a daunting task. But guess what? It doesn't have to be. Break the cycle with these simple steps: 1. Regular Review and Update ↳ Schedule regular reviews of your test scripts. ↳ Check for outdated or redundant scripts and update them as necessary. 2. Modularize Your Code ↳ Break down your test scripts into smaller, reusable modules. ↳ This makes them easier to manage and update. 3. Implement Page Object Model (POM) ↳ Use POM to separate the UI and test logic. ↳ This helps in reducing code duplication and improving test maintenance. 4. Use Version Control ↳ Incorporate a version control system like Git. ↳ This allows you to track changes and roll back if something goes wrong. 5. Refactor with Each Sprint ↳ Make refactoring a part of your sprint planning. ↳ Regular updates ensure that your test scripts remain effective and aligned with your application's current state. Continuous refactoring ensures that your test scripts are always up-to-date, reducing maintenance overhead and improving test reliability. By following these steps, you can create a robust, efficient, and maintainable test automation suite. Share this post with your network to spread the knowledge!

1

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Get SDET Interview ready with my latest updated package (paid): https://lnkd.in/gusymgFi Read & Follow me on Medium for tech related blogs: https://lnkd.in/dCDi84Q9 #japneetsachdeva

260

8 Comments

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Note: All services on TopMate are discounted till 31st May. Use it maximize your learning!! Get SDET Interview ready with my latest updated package (paid): https://lnkd.in/gusymgFi Full Stack QA with Test Architect preparation: https://lnkd.in/dWjpT3-3 Read & Follow me on Medium for tech related blogs: https://lnkd.in/dCDi84Q9 #japneetsachdeva

154

9 Comments

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Get SDET Interview ready with my latest updated package: https://lnkd.in/gusymgFi Become Master in Test Automation Frameworks & Designs: https://lnkd.in/gyFKz5yF My latest course on Udemy, for sale at Rs 399 only, Take a look here: https://lnkd.in/grvCi-ri #japneetsachdeva

145

2 Comments