I'm using jmeter and performed the following procedure:
Occurred:
When writing the test the user was saved normally in the database. I deleted the user and executed the saved script. There were no errors in the script, but the user was not saved. Can someone give me some help?
It is possible that the functionality in question would get serious data in another table (s) and there is some record. The system, seeing that something already exists, does not record the user.
Another possibility is that there is an error, but your test is not picking it up.
It would be interesting to look carefully at the return log of each request.
If the system has some type of cache, it may have a version of the user in memory and think that it already exists.
This scenario is rather strange, but may occur depending on how the system manages its entities. Incorrect logic using the Java JPA API can lead to this kind of problem.
There are also times when we look at the incorrect database or table.
If in doubt, check with the person in charge of the environment if there is any change. It may be that someone has set up the system to use another instance of the database server.
Another possibility is that the user was recorded during the second test, but you could not find it because the ID or some field used in the query criteria has changed.
This is common to occur if there are fields generated automatically by the system.
I tried to enumerate the most common problems that occur in scenarios where there does not seem to be a reasonable explanation
However, the problem may be in the most basic misconception, such as looking at the wrong bank, as in the more "obscure" details of the system architecture.
If none of these help you, you have to work with the system developer, who can debug the exact behavior of the program. Remembering that in such situations it is essential to detail the procedure for reproducing the problem.
