Search Results

Apart from the fact your second piece of code will not even be compiled and also pretty much not representative since you're not showing us how exactly you would use the information of which particula …

Depends on what your resources are you might want to use either online service like either https://www.mocky.io/ or https://www.mockable.io/ or https://get.mocklab.io/ (that is build on top of wiremo …

If you have no other options except of performing your tests in prod, you should avoid using the methods which change the application state. Here are few sides you can look at the issue from: HTTP st …

Answering your particular question, I'd like to spotlight that there are several ways to assert headers. And ("Key","value") is one of those ways. You can also find the methods which allow you to appl …

What you are showing is called a JSON object. Unless you're in JavaScript (that can natively parse JSON data) you can use a jsonpath language that is very similar to xpath (serves for similar purpose) …

Going through your particular points I would say that This is the valid observation since this is improperly configured request (aka client error) so it has to be responded with 4xx status code. In …

Use the following jsonpath query: serviceLines[0].customerProducts.findAll{product -> product.highLevelProduct == 'HSI'}.customerProductIdentifier Test: System.out.println(js.get("serviceLines[0]. …

To make it valuable for the entire team I would suggest to: Integrate your tests into CI process. So you need to take a role of devops or help your devops to do that Design your tests in BDD style ( …

This depends on what type of testing you implement: If it is a component testing (or if your goal is to test the particular end-point) you should isolate your component from the possible impact of o …

GraphQL endpoint is just a REST endpoint that returns you some data in response to some input data. So in this abstract there is no any specific things to test. Like in any other endpoint there is som …

You should approach with REST Assured one more time. Actually it should perfectly fit your needs. When you run GraphQL service you basically run a REST end-point where you send some query and receive …

Check if your API tests with rest-assured operate with all the possible parameters (not just end-points) that could run your API in all possible ways Do not ignore negative tests. In my experience we …

I prefer to segregate the projects. There are few pros for doing so: If there is quite a lot of code in your project then you'll have to wait while all your code will get consistent (compiled, addre …

Answering your questions It doesn't really matter and depends on the test implementation and execution complexity, skills of dev and test people, their current tasks and tasks' priorities. Integrati …

That depends on what exactly you're going to test. If you're going to test only API logic, then you should assert Response codes Response body (since API methods often return objects within the body …