Search Results

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 …

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 …

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 …

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 …

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 …

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 …

Prefereably I would like to stop doing that type of debugging You are a tester. You shouldn't do any debugging and investigate what is the root cause of the test failure (the only acceptable type …

This depends on how your devs developed the particular service under test. If we're talking about REST architecture, then there is probably WADL file exists that describes the interface you may use fo …

Here are the steps: Prepare a request returning the data you need Create a Test Suite Create a Test Case within that Test Suite Add that request as the step to the Test Case Open that step editor In …

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 …

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 …

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

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) …