You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"codigo": "JDPICHV004",
"mensagem": "The entered key already exists in the database!"
}
Actual behavior
When a execute a test that call criaChaveEmail the result are:
{
"chave": "[email protected]",
"dtHrCriacaoChave": "2025-01-09T16:27:32.921Z",
"dtHrInicioPosseChave": "2025-01-09T16:09:55.790Z"
}
but i know it not true, the time returned is a old one of my first execussion and i already have the registry on database:
The expected result are a error: 400 Bad Request
{
"codigo": "JDPICHV004",
"mensagem": "The entered key already exists in the database!"
}
On postman i receive it.
Its like the first execution response is in cache and it return every time. i close ui and open and have same result. using $ npx playwright test
same result.
See a using "Cache-Control": 'no-store'
I have a second test for another url, its like the one but it not apresent the problem:
this always reach the server and give me correct info, i know because os return date time of the info.
Please i need help.
Additional context
No response
Environment
$ npx envinfo --preset playwright
npm ERR! code ENOENT
npm ERR! syscall lstat
npm ERR! path C:\Users\ggaldin\AppData\Roaming\npm
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, lstat 'C:\Users\ggaldin\AppData\Roaming\npm'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in: C:\Users\ggaldin\AppData\Local\npm-cache\_logs\2025-01-09T19_30_04_855Z-debug-0.log
The text was updated successfully, but these errors were encountered:
This issue is not following the bug template. Please provide a self-contained reproduction, which we can run locally to reproduce your issue. Thanks for your understanding!
Version
1.49.1
Steps to reproduce
async criaChaveEmail(chave) {
Expected behavior
{
"codigo": "JDPICHV004",
"mensagem": "The entered key already exists in the database!"
}
Actual behavior
When a execute a test that call criaChaveEmail the result are:
{
"chave": "[email protected]",
"dtHrCriacaoChave": "2025-01-09T16:27:32.921Z",
"dtHrInicioPosseChave": "2025-01-09T16:09:55.790Z"
}
but i know it not true, the time returned is a old one of my first execussion and i already have the registry on database:
The expected result are a error: 400 Bad Request
{
"codigo": "JDPICHV004",
"mensagem": "The entered key already exists in the database!"
}
On postman i receive it.
Its like the first execution response is in cache and it return every time. i close ui and open and have same result. using $ npx playwright test
same result.
See a using "Cache-Control": 'no-store'
I have a second test for another url, its like the one but it not apresent the problem:
async consultaChave() {
this always reach the server and give me correct info, i know because os return date time of the info.
Please i need help.
Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: