yeti-web
yeti-web copied to clipboard
Spec Improvements: Cleanup API Logs after each controllers test
Clean up the API Logs table after each controller/requests test.
Since we introduced the new feature (YETIWEB-1396, Async writing to API log), the API logs are not reverted by postgres within transaction inside test env because the API log is created within a separate Thread. Therefore, the API logs table grows and the number of records grows during API testing.
I suggest using this cleanup in general for all API specifications to ensure that each test is not affected to another test and its precondition.