Currently automated reports run on recurring monitors based on user encounters. At the start the automated errors were for the most part useless because there were 400 low priority bugs, 50 major, two ...
Currently, after every action that adds or changes data, we verify that that data was successfully added/changed in the database by querying the tables directly. I feel this is redundant because that ...
We're working on test code (mainly UI tests with a few different tools). One thing that's really stumping me is how to best separate test data from test scripts. By test data, I mean values that get ...
Currently the way we do this on LedgerSMB is to have SQL scripts which insert records into a test results table. This table is created in a transaction which runs the tests, and the tests always roll ...
I would like to understand Data Validation for Automation in case of (Weekly/ Frequent Builds) In case of frequent code changes (Weekly builds) since the code base would change frequently Automation ...