I am trying to automate integration testing in our team, and I am wondering if making tests with parameters is good or bad design.
My problem is that the integration tests should run some perl scripts from our codebase that work with database and compare the data in database before and after the test. I would like to set a flag for all automated tests to revert the database changes, so different tests will not interact with each other. But I also want to disable the flag on purpose, so I will be able to manually check the data so the test does not overwrite them back immediately after finishing.
Is there some cleaner/more common solution for this? I know about database and data mocking, but I can not use that.