I'm writing some end-to-end automated tests for a
CRM-alike web application. One of the development team leaders is asking me to do something that I've never done before.
The problem is that the data that is being displayed in the views of the application is sometimes different after each
synchronization/deployment, but the data should always be the same.
The data comes from different stored procedures inside a
SQL Server database, and they are using some kind of soft coding solution to develop the application and connect it to these stored procedures. I would like to know if it is possible and advisable to include this data verification in the automation process (as they are asking me to do) and what solutions would be appropriate for this.
We are using
Cypress as our automation tool. The idea would be to somehow store the data after running the automated tests, and then the next time we run the tests again, the stored data is compared against the data of the current execution. If the data is different, that should cause the tests to fail.
This is my first time asking a question here, any ideas?