New answers tagged api-testing
0
There are many negative scenarios you could test like :
Send a non PDF to client and observe client behaves
Send some corrupted pdf.
Send some exe file and verify that the app does not insecurely deserialise it
Send non supported parameters and see if PDF is getting generated or proper error message is thrown .
Try converting blob to PDF and see you are ...
0
This is from c#
[TestMethod]
public void Get_GetServiceTypeList()
{
string url = "https://XXXX";
string OutPutdata = null;
byte status = 0;
string ResponsCode = null;
var client = new HttpClient();
try
{
var response = client.GetAsync(url).Result;
ResponsCode = ...
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 ...
0
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 ...
0
Yes, as per official cypress documentation, you should avoid using cy.visit() when testing an external site. They also list a bunch of reasons why this is not the best approach:
However, you should never use your UI or visit a 3rd party site when testing because:
It is incredibly time consuming and slows down your tests.
The 3rd party site may ...
1
With JMeter you can do whatever you want, if you need to hit multiple API endpoints with multiple threads (virtual users) at exactly the same moment you need to consider following configuration:
List your endpoints in a CSV file, for example:
http://example.com/endpoint1
http://example.com/endpoint2
http://example.com/endpoint3
Use CSV Data Set Config so ...
1
You can use below code in your pre-requist script
const uuid = require('uuid')
let email=uuid()+'@domain.com'
pm.environment.set('email',email)
and access the same using
{{email}} , in non script locations
pm.environment.get('email') in test scripts
You can also use other unique identifier libraries given below, instead of uuid
const moment = ...
2
Contrary to Pre-request Script, I would suggest using another efficient way to generate a random email:
like qa{{$timestamp}}@gmail.com. Here, {{$timestamp}} will always give you a unique number that never occurred in the past.
Moreover, if you want to stick with the Pre-request Script, then here is the way to do so:
Now, access the environment variable in ...
0
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 ...
2
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 ...
Top 50 recent answers are included
