CHAPTER 6 TESTING

Software Testing: It is the process of testing the functionality and it is the process of executing a program with the intent of finding an error. A good test case is one that has a high probability of finding an as at undiscovered error. A successful test is one that uncovers an as at undiscovered error. Software testing is usually performed for one of two reasons: Defect Detection Reliability estimation

6.1 Black Box Testing: The base of the black box testing [4] strategy lies in the selection of appropriate data as per functionality and testing it against the functional specifications in order to check for normal and abnormal behavior of the system. Now a days, it is becoming to route the testing work to a third party as the developer of the system knows too much of the internal logic and coding of the system, which makes it unfit to test application by the developer. The following are different types of techniques involved in black box testing. They are: Decision Table Testing All pairs testing State transition tables testing Equivalence Partitioning

6.1.1 Decision table testing: In this the variable are tested for both true and false cases. In this all this type of such cases can be tested. In our website, the Albums details can be visible to the users only if they get registered with the website. If they dont get registered only common home page will gets displayed. By applying this test the similar type of test cases are identified and solved the issues. 6.1.2 All pairs testing: In this all the input parameters which are to be filled are checked for all possible combinations. In our website, during different types of registration all the fields that are available in the forms need to be filled by the users. If any one of the field is left unfilled an error message gets displayed. During the code development phase, validation was not written for

forms which led the user to leave some of the fields unfilled. By this test, test case was identified and solved. 6.1.3 State transition tables: By using this current state of the website and to which states the website will move based on input parameters. In our website, after successful registration the users will be redirected to their respective web pages in case of failure will be redirected to home page. In the silimar manner the different test cases are generated and verified. State Registration Books 6.2 White Box testing: White box testing [4] requires access to source code. Though white box testing can be performed any time in the life cycle after the code is developed, it is a good practice to perform white box testing during unit testing phase. In our website, the flow of specific inputs through the code, internal security holes, expected output and the functionality of conditional loops are tested. In our application, the different types of users get their respective ids like cust id, emp id, , Album id and Gift id . The value needs to get updated for every registration.Through this test, the code was written to update the no of ids and the similar test cases are identified and verified. 6.3 Performance Testing: The performance of the application can be tested through this test. Since the no of lines of code is less, performance is good. 6.4 Database Testing: This test involves testing whether the values entered through the form gets stored in the database correctly or not.In our website, test is made on the database to check values are saved or not. 6.5 Compatibility Testing: Testing to ensure compatibility of a website with different browsers, operating systems and hardware platforms. Our website is tested on all different browsers, operating systems and hardware platforms. 6.6 Acceptance Testing: Testing to verify a product meets customer specified requirements. In our website, the acceptance test suite is run against supplied input data. Then the results obtained are compared with the expected results of the client. A correct match was obtained. Input 0 Homepage Registration Input 1 Respective homepage View books