12

You should always pick tests carefully when it comes to test automation. :) One of the reasons, as you said, is overlap (and with that, execution time and robustness). An example to clarify: Your API has 10 endpoints which might return several different error messages each. Don't test each error as a UI test: this will take up lots of runtime and will also ...


6

There is no concept of overlapping testcases in different test levels, Both are completely isolated Just because API works fine you cannot guarantee UI works fine. Imagine all your API tests passing but user not able to use the UI , Imagine all your UI working due to cached information but actual backend is failing. Ensure more low level coverage like unit ...


3

I definitely understand the want to do it through the UI. Seems so much easier. I think that you're on the right track though to start doing it with the UI. The data will be much closer to what you actually need to test. But, this should only be a start for you. Ideally, these dumps are there for good and never change. Here's a couple of ideas. In all ...


3

Try the petstore - it's a common API used in examples. I used it when working with JMeter and it's a useful API to practice with. https://petstore3.swagger.io/ You can do all sorts of different things there.


3

TL;DR: you will have overlap between E2E and API integration test cases, in terms of the same endpoints being exercised in both and that's OK - it helps you figure out where the problem is if (...when) something goes wrong. When working with a codebase that doesn't currently have comprehensive automated testing, start with the E2E(/functional/UI) tests. Why? ...


2

The file path should be relative to class path , try statusCode(200).and().body(matchesJsonSchemaInClasspath("\\test\\java\\com\\rest\\api\\schema\\getuserschema.json")); or statusCode(200).and().body(matchesJsonSchemaInClasspath(".\\test\\java\\com\\rest\\api\\schema\\getuserschema.json")); or statusCode(200).and().body(...


2

make sure you are importing org.testng.annotations.Test and not org.junit.Test


2

Reading your question it seems you have a messed up DevOps pipeline. The fix should not be for the testing strategy but the DevOps implementation itself. Few things that needs to be restructured are: Why are you automatically syncing staging data to Production? The purpose of staging is to mimic the production environment and make sure things work in ...


2

Restful-Booker is purpose made for learning to test an API. You can either use the online version, or you can check out the repo and run it locally if you prefer. I think it's a pretty useful site to practice with, and it does seem to be actively maintained - the author has written a couple of courses on API testing which are pretty useful (linked from the ...


1

Seems your switching tab is not working properly. Please check that new tab handler is okay. # collects handle ID of current window first_tab_handle = driver.current_window_handle print("first_tab_handle : "+str(first_tab_handle)) # collects handle ID after new tab is opened print("current window handle : "+ str(...


1

For loops are problematic in Cypress because they run run faster than the Cypress command queue. You don't show the Cypress commands above, but I assume they are following the warmup loop and are only called when healthStatusCode === 200. You might find Test Retries will work better for you. Individual Test(s) If you want to configure retry attempts on a ...


1

https://explore.postman.com/templates/1692/working-with-graphql This is a postman example , just click try with postman and it opens up postman with collection and everything set up You add test scripts as same like you do for rest api, there is no difference:


1

This and this GitHub repositories provide a curated list of service projects, many open source, and buildable by running a couple of Docker commands. You may also want to visit this site. As an example of a simple API from a "real site" is Trello. I've written a blog post showing a CRUD cycle in it for Postman. Nonetheless, it's direct to ...


1

There is no need to test the same thing with API and UI tests. Start with API (keeping in mind the test pyramid), provided code is sufficiently covered with unit tests, and automate certain e2e scenarios that would cover cases not covered by individual API.


1

JMeter threads are absolutely independent, their context (session state, variables, etc) are stored locally hence each thread represents an individual virtual user. Each thread executes samplers upside down (or according to Logic Controllers), this way you can pass the variables from one request to another within one thread As you can see in below example ...


1

Why not just stub out the database and deal only with Entities? Databases are details which you can: (1) - Check behavior independently; (2) - Isolate your use cases from. If you want to set up a component check for a service, all you need to do is boot up the service, create the necessary Entities and perform a call to its endpoints. If you want to ...


1

You can Extracting data from responses and chaining requests in postman tool. Please refer below links which may be helpful. Extracting data from responses and chaining requests For a dynamic parameter, you can also create any Random function and you can create and set it in environment variable if require. You can use chain request and Next request ...


1

This what the Postman variables do, Assuming that your response data is: { name: "something" user:{ id:"12" } } in the test script section, add below command let jsonData = JSON.parse(responseBody); pm.environment.set("id", jsonData.user.id) //this stores the id to env variable 'id' now you can access the id value from the next ...


Only top voted, non community-wiki answers of a minimum length are eligible