We Talk Coding
Databases ?
what are some things to consider when doing operational testing.
Public Comments
- Transactions per second. SQL injection.
- Power "on" and ground/gather yourself.
- Volumes - How many queries and new inserts would your database have to handle. You can get high volume simulation software. Multiple queries on the same information at the same time. Multiple inserts at the same time. Multiple edits/amends on the same information at the same time Does your database crash if someone tries to put in information with the same "data id key." If you are doing accounting transactions are both side of the insert mask using the same math's rules. There are certain numbers that if the one side of the transaction rounds down and the other side rounds up the transaction won't balance. Security - can you get someone to hack into the database. Brainstorm some possible glitches that could happen like: * part of a record being input and the rest being lost in transmission * record Keys not matching between all the databases * someone inserting garbage on purpose using all characters on the keyboard *what happens if all necesary databases are not updated when information is inserted See if your input masks and error reports will highlight any of the above. Contingency procedures - do your back up and reinstall processes work.
