Browse over 20 million
homework answers & study documents

Discussion Question

Rating

Showing Page:
1/3
Database testing
The data is stored in the database in tables. However, tables may not be the only objects in the
database. A database may have other objects like views, stored procedures and functions.
These other objects help the users access the data in required forms. The data itself is stored in
the tables. Database testing involves finding out the answers to the following questions:
Questions related to database structure
1. Is the data organized well logically?
2. Does the database perform well?
3. Do the database objects like views, triggers, stored procedures, functions and jobs work
correctly?
4. Does the database implement constraints to allow only correct data to be stored in it?
5. Is the data secure from unauthorized access?
Questions related to data
1. Is the data complete?
2. Is all data factually correct i.e. in sync with its source, for example the data entered by a user
via the application UI?
3. Is there any unnecessary data present?
Now that we understand database testing, it is important to know about the 5 common
challenges seen before or during database testing:
1. Large scope of testing
It is important to identify the test items in database testing. Otherwise, you may not have a clear
understanding of what you would test and what you would not test. You could run out of time
much before finishing the database test.
Once you have the list of test items, you should estimate the effort required to design the tests
and execute the tests for each test item. Depending on their design and data size, some
database tests may take a long time to execute. Look at the test estimates in light of the
available time. If you do not have enough time, you should select only the important test items for
your database test.
2. Incorrect/ scaled-down test databases
You may be given a copy of the development database to test. This database may only have
little data (the data required to run the application and some sample data to show in the
application UI). Testing the development or test or staging databases may not be sufficient. You
should also be testing a copy of the production database.
3. Changes in database schema and data
This is a particularly nasty challenge. You may find that after you design a test (or even after you
execute a test), the database structure (the schema) has been changed. This means that you
should be aware of the changes made to the database during testing. Once the database
structure changes, you should analyze the impact of the changes and modify any impacted tests.
Further, if your test database is being used by other users, you would not be sure about your test
results. Therefore, you should ensure that the test database is used for testing purpose only.
You may also see this problem if you run multiple tests at the same time. You should run one test

Sign up to view the full document!

lock_open Sign Up

Sign up to view the full document!

lock_open Sign Up

Sign up to view the full document!

lock_open Sign Up

Anonymous
I was on a very tight deadline but thanks to Studypool I was able to deliver my assignment on time.

Anonymous
Heard about Studypool for a while and finally tried it. Glad I did caus this was really helpful.

Anonymous
I always get good papers on this site. They are detailed and address all the requirements I need.

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4