Testing Database
Extracts from this document...
Introduction
Testing Testing strategy The basic objective of testing the system is to ensure that everything is working as expected. During the testing we should look out for the following: * Macros should work as expected * Queries should run and return accurate outputs (and store required information property where appropriate) * Forms should display fields correctly * Command buttons should run actions as expected * Report should be printed correctly * Input should be validated correctly where appropriate * Required fields should not be empty. System should detect required fields that are empty The testing of the system will be divided into 3 parts: * Functional - the testing of individual components of the database. This is done when the component is created and will be documented in the implementation * System testing - the testing of the full system from beginning to end. ...read more.
Middle
6 Queries Run all queries in the database All queries in database should run smooth and display the correct data Evidence of Testing Test 1: Switchboard & Switchboard Options Switchboard should load as expected The command buttons opened the correct forms as expected Test 2: Add/Edit customers details in Company's Add/Edit customers details in Company's Record 1: A new record was added and saved correctly to the tables as expected. Record 2: When erroneous data is entered (Postcode was missing 3 characters) the system validation rule showed the following message Record 3 When erroneous data is entered (a mobile number, four digits short) the system validation rule showed the following message. Record 4: When trying to enter extreme data the form (typing "adfgrthjs" into the company phone) The system will not allow me to as I expected. ...read more.
Conclusion
Edit Record 2: When I edited the "Prop data" in record 2, the cells allow me to edit dates and save them as shown below of the Wants table: "Add/EditWants_Exit", marco opened and closed the correct forms as expected. Test 4: Command buttons in the user interfaces Frm company interface The frmCompany loaded as expected All my command buttons in "frmCompany" worked and carried out all tasks as I expected. When manually clicked Interface of frmCampaign All the command buttons in "frmWantsCampaign" worked and carried out all tasks as expected. When click manually clicked. Test 5: Add/edit Wants and campaign Record 1 When editing Wants and Campaign a new record is added Record 2 When adding a text which is not recognised by the system 'Microsoft Access' detected it and a validation message appeared. Test 6: Queries I ran all queries and they run smoothly. Below is a screen shot of all queries. ?? ?? ?? ?? [Type text] Eyram Tetteh Candidate No: Centre No. 12125 ...read more.
This student written piece of work is one of many that can be found in our AS and A Level Information Systems and Communication section.
Found what you're looking for?
- Start learning 29% faster today
- 150,000+ documents available
- Just £6.99 a month

Here's what a star student thought of this essay
Response to the question
The report shows the user clearly testing the database, and explaining why it's necessary for the user to carry out tests on the database. However, in some areas, there could be an improved level of detail. The testing plan states ...
Read full reviewResponse to the question
The report shows the user clearly testing the database, and explaining why it's necessary for the user to carry out tests on the database. However, in some areas, there could be an improved level of detail. The testing plan states a number of key areas where the user is going to test, these are clear and straight to the point.
Level of analysis
When the user was testing the database it may have been useful if the user were to note down the process in more length in undertaking the test. At this stage, the report states what the test should achieve, and whether the test is successful or not. For higher marks, the report could mention the process taken to test the aspect within the database.
Quality of writing
The report clearly states each of three parts of testing the database. The terms 'Functional', System Testing' and 'End-Use Testing' are all explained thoughtfully, and it's clear that the user understands how to test a database using these three aspects. Some of the presentation of the screenshots of the database, could be improved a little. It does appear a little messy and can be quite confusing to follow.
Did you find this review helpful?
Join our team of reviewers and help other students learn
Reviewed by danielbeal 18/02/2012
Read less