Design a set of test cases that we can use to test the DB database from unit to

system level. The test cases should:

a. Ensure the following:
v All the users in the source database have migrated successfully
v Privileges and grants for users are correct
v Tables have the correct structure, defaults are functioning correctly,
v and errors did not occur during mapping
b. Validate that the data migrated successfully by doing the following:
v Comparing the number of rows in the DB database with those in the source data
base
v Calculating the sum of numerical columns in the DB database and compare with
those in the source database
c. Ensure that the following
v Constraints: We cannot enter duplicate primary keys
v Foreign keys prevent we from entering inconsistent data
v Check constraints prevent we from entering invalid data
d. Check that indexes and sequences are created successfully
e. Ensure that triggers, procedures, and functions are migrated successfully.
Check that the correct values are returned for triggers and functions
3. Run the test cases against the migrated database.
4. Create a report that evaluates the test case results.
These reports allow evaluating the data to qualify the errors, file problem repo
rts, and provide a customer with a controlled version of the database.
5. If the tests pass, go to Step 7
If all tests in the test cases pass or contain acceptable errors, the test passe
s. If acceptable errors occur, document them in an error report that we can use
for audit purposes.
6. If the test cases fail, do the following:
a. Identify the cause of the error.
b. Identify the test cases needed to check the errors.
c. Log an issue on the controlled version of the migrated database code in the
problem report.
d. Add the test case and a description of the problem to the incident tracking
system of yours organization, which could be a spreadsheet or bug reporting sys
tem. Aside from the test case, the incident log should include the following:
v Provide a clear, concise description of the incident encountered
v Provide a complete description of the environment, such as platform and sourc
e control version
v Attach the output of the test; if useful indicate the frequency and predictab
ility of the incident
v Provide a sequence of events leading to the incident
v Describe the effect on the current test, diagnostic steps taken, and results
noted
e. Attempt to fix the errors.
f. Return to Step 1
7. Identify acceptance tests that we can use to make sure the DB database is a
n acceptable quality level.
4.2. Types of Testing
QA will focus on the following testing types for Data Migration.
1. Functional Testing
a) Data Validation
b) Regression testing
2. Non Functional Testing
a) Performance testing
b) Load testing
3. Integration Testing
4. UAT Testing
4.2.1. Functional Testing
All the functionality testing activities carried out in the Implementation phase
of development would be categorized as Functional testing. Testing team will cr
eate functional test cases and ensure that these test cases are mapped to all th
e test scenarios which in turn are mapped to scope items in the requirements doc
ument. Testing activities in a particular iteration would depend upon the develo
pment stories being delivered.
4.2.1.1. Data Validation Testing Approach and its Activities
Refer to section 4.1 to test the DB database
4.2.1.2. Regression Testing Approach and its Activities
At the end of each iteration, application would be regress tested to ensure that
any change in one part of application does not hamper functionalities of other
areas.
Regression suite will consist of all high priority scenarios of the requ
irements delivered in a given iteration.
Re-validate of existing functionalities after fixes/changes.