java ee - Writing test code for verifying database entries when testing an API -
I am writing a test code to test a client-server application. The test is included in the application
- Tomcat or other Java EE application runs on the server and
- Customers jar to expose APIs
I'm basically writing a test code which uses this client API to connect to the server.
In addition to the large scale testing of API operations, my senior officials have advised me to verify the server and verify that the fields are being properly populated. I have done this for some of my test cases, but it has not really caught any bug during regression.
Bugs are caught when a special functionality fails, but also that code appears in That goes to check the API itself. It seems that DB data validation is not really useful, especially considering the additional efforts required to write and maintain all those code.
My question is this:
Is there any real benefit to join the DB and write test code to confirm the entries in this manner? Is the benefit paid for these types of code writing?
Reading the database is unnecessary.
If you check the database contents, then your test can not be seen to see whether any change in the database works, because the expected examination of a certain position Has the database If this changes, your test fails, even if the system works.
Comments
Post a Comment