Computers

                                   Test Case Study-Project 1.         Wrong informationrmation type: enigma - Through our testing phase of the database we found that we had setup the simple eye Transactions table wrong. The one of the fields that should have been a numerical field was setup as an of importbetical field. force - The fix is to go into the database and go into the design view. Highlight the record Transactions table, right click and go into properties. Once in properties in the design view, we changed the data type to numerical from alpha and the problem was fixed. 2.         Improper field length: Problem early(a) problem was found while entering data in the inventory performance field. Alberto was trying to enter an ID number for a product and the field was to short by twain digits. each(prenominal) transaction ID number consist of a letter and four amount. durati on he tried to enter the last two numbers it would not work. Solution- The solution was to make the field 10 characters in case of expansion. 3.         Unreasonable quantity: 4.         Out-of-range insertionFor example, allowing an put unitedly with a date of May 10, 1932. 5.         Valid data info that is expected to succeed and work in the application. 6.         Invalid dataData that is expected to fail in the application. 7. Date founding for required fieldsFor example, ensuring that information must be in required fields such as a simple key If you want to get a full essay, grade it on our website: OrderCustomPaper.com

If you want to get a full essay, visit our page: write my paper