I conduct this testing based on data validation and data integrity.
Data validation means that whether front-end values are correctly getting stored into back tables or not.
Data integrity means that whether impact of front-end operations is working on back end tables or not,
Database testing basically done to test whether data from front end is properly getting inserted in the tables or not.Sometimes one action at front end , has impact on various tables in the database.Like if a user deletes his account from a website, its information saved in more than one tables(user_info,user_company,user_academic etc) gets deleted.
Other example is , if in a website, if u can use a functionality(inviting other users) limited times then every time u invite a user,an entry goes to Invite_info and also an entry in invite_quota table.
Although , i also can verify above mentioned functionalties through front end but sometimes it takes us to wrong results but checking results with database is more reliable.Also it saves more time than front end testing.
Also , in Database testing, we also verify whether data is getting saved with correct type and correct size.
good try...try to cover cases like when the data grows big how will u do "perfromance testing" may due to lack of some indexes on database columns queries can become slower etc.,etc.,
ReplyDelete