-Table: Tables are created according to the scenario provided and consist of six different tables.
-Customers tables
... [Show More] (CustId,Custname,DoB,Gender,Address,Custphone,CustEmail)
-Supplier tables (SupId,Supname,SupAddress,SupPhone,SupEmail)
-Items (ItemId,Itemname,Unitprice,SupId(FK))
-Salesperson tables (SalesId,SalesName,DoB,SalesAddress,SalesPhone, Bonus)
-Orders (OrderId,Itemname,Unitprice,Date_order,CustId(FK),SalesId(FK))
-Orders_detail (OrderId(PK,FK),ItemId(PK,FK),Quantity)
What types of testing will be carried out (e.g. White Box test, Black Box test)
Black Box testing in database testing:
The ELECTRO SHOP database system is testing with the white box test and black box test a white box
testing involves testing interface and the integration of the database and the black box testing mainly
deals with the internal structure of the database
Black box testing involves testing interfaces and the integration of the database, which includes:
1. Mapping of data (including metadata)
2. Verifying incoming data
3. Verifying outgoing data from query functions
4. Various techniques such as Cause effect graphing technique, equivalence
partitioning and boundary-value analysis.
With the help of these techniques, the functionality of the database can be tested thoroughly.
Pros and Cons of black box testing include: Test case generation in black box testing is fairly simple. Their
generation is completely independent of software development and can be done in an early stage of
development. As a consequence, the programmer has better knowledge of how to design the database
application and uses less time for debugging. Cost for development of black box test cases is lower than
development of white box test cases. The major drawback of black box testing is that it is unknown how
much of the program is being tested. Also, certain errors cannot be detected.
o White Box Testing in database testing
White box testing mainly deals with the internal structure of the database. The specification details are
hidden from the user.
1. It involves the testing of database triggers and logical views which are going to support database
refactoring. [Show Less]