Book Management system--testing and debugging

1 Debugging methods
The system is run and debugged on the local server, and the system is white-box and black-box tested due to the complete understanding of the internal structure and processing algorithms of the system and the complete mastery of the system functions.
In the process of developing the software system, it is necessary to face the complicated problems, so the error will inevitably occur at every stage of the software life cycle. The purpose of testing is to discover errors and execute a program, the most important purpose of which is to discover errors that have not been found.
In order to design an effective test plan according to the following guidelines to test: All testing should be traced back to the user requirements, in the completion of the requirements model will be set up a test plan, before coding all the testing work planning and design; The Queen Pareto principle focuses on the error 20% that accounts for errors 89% Modules are tested, starting from a small scale, and gradually conducting large-scale testing, usually first focus on testing individual program modules and then to integrated modules, carefully design test plans, as much as possible to cover the program logic to meet the requirements of the possibility.

2 Test Cases
2.1 Login Module Test
Enter the system, enter the user name and password, according to the user's identity, the display of the Operation menu is different, the general reader can only view the book information and personal information, and can query their own history of borrowing books; Librarians can view and manage the book information, reader information and borrowing information. A login error is displayed when the wrong user name password is entered and the login window is returned automatically.

2.2 Book Management test

After the librarian enters the system book Management module, the book can be added, modified, deleted.

(1) Add a book, fill in the basic information of the book, click the OK button to add a successful jump to the success page
Side and prompt to add success, can continue to add, add failed to jump to failure page and prompt to add failed, please re-add. When the information is incomplete, click the OK button to give a hint based on the information that is not filled in.
(2) Delete the book, a single deletion, click Delete according to the book's ID to delete this book information, success is returned to the list, unsuccessful is not the reason to delete the success, multi-select Delete also according to the book ID array to delete multiple books, and jump to the corresponding prompt page.
(3) Modify the book information, click to view the book information, you can modify the book information, modify the success or failure to jump to the corresponding prompt page.
2.3 Student Management Test

When the librarian enters the system library card management module, it can be added, modified, cancelled, etc.
Operation.
(1) to handle the library card, fill in the basic information of the reader, click the OK button, add the successful jump to the success page and prompt to add the success, you can continue to add, add failure to jump to the failure page and prompt to add the failure, please re-add. When the information is incomplete, click the OK button to give a hint based on the information that is not filled in.
(2) The cancellation of the library card, a single deletion, click on the deletion of the library card according to the number of the debit card, the success of the return list, unsuccessful is not the reason to delete the success, the multi-select Delete is also based on the library card ID array delete multiple library card, and jump to the corresponding prompt page.
(3) Modify the reader information, click to view the reader's library information, modify it and follow the results of success or failure to jump to the corresponding prompt page.

2.4 Lending Information Management test

When the librarian enters the system borrowing information management module, it can manage the borrowing information.

(1) for borrowing, according to the Reader Library card number and book number for readers to borrow this book, if the figure
The remaining quantity of the book is 0, the hint can not borrow, the number of books is not enough, so the library card has borrowed this book, the hint can not borrow the same books, if the borrowing success to the success of the interface.
(2) book return, according to the reader's library card number and book number for the return of books, borrowing information must have this information, or can not be returned, jump tips page. After the successful return of the book, the loan information is no longer available, the number of books plus 1, and the calculation of the lack of fees.
(3) Check lending information, can be based on the book number or library card number to inquire about borrowing information. (4) to handle the repayment, according to the reader to borrow the card number for the reader to handle the repayment business, according to the results can jump to the corresponding prompt page.

3 Reviews
The testing process is conducted in strict accordance with the testing process, through unit testing, subsystem testing and system testing. Through the unit test, we find out the errors in each module of the system, and through the subsystem test, we find the mutual coordination and communication errors, and through the system integration test, we find the errors in the software design process. By correcting the design and implementation of the errors, the book Lending management system can fulfill the requirements specified in the requirement analysis.
As can be seen from the above test, this system can complete user login, System setup, book management, reader management, loan management and system query functions. Readers in the application of the system can be implemented in a variety of ways (such as: title, number, author) query library books, convenient borrowing books, return books, can check their own borrowing books. Library staff can easily query the book, convenient for readers to borrow information, convenient to do book books and so on, convenient to add, modify, delete, classify management and other operations, to the system users to add, modify, delete, permission settings and other operations, The library's certification parameters to modify maintenance and other operational functions. The work of the testing phase discovers the errors of the system, and on the other hand verifies that the modified system can realize the anticipated goal of improving the efficiency of the library.

4. The test results are as follows:

Book Management system--testing and debugging