1、Discuss your test plan
Our project is to build a student management system website.
Our website architecture and general websites same basic architecture consists of three parts: interactive modules, control modules, and database modules. For our customers requirements, we at interface, control module, as well as the design database module function has also been emphasized. These features will be reflected in our test plan.
- Testing purposes
Student management system project all software testing activities, including testing schedule, and coordination between resources, issues, risks and test group and other groups to assess and summarize the successful experience of inadequate testing activities in order to better carry out future testing. Proficiency in software testing activities, as well as learning the Java programming exercises. Student management system uses a new performance management philosophy, systems based on sound information management, and to create a new user, enter performance data has been created, modify, view, and statistics functions operate, and can basically meet the university teachers demands . All software testing activities for the project, including the test content, progress, and problems, which risks might produce a detailed understanding conducive to the future to avoid or correct such errors do the project.
- Test Range
Student management system testing project management of major achievements of students and archiving information, only the time function and system testing, its performance is not within the scope of the test. Key features include: user management, query management, performance management entry / update management, statistics management, registration management.
User management: Set permissions management capabilities, users can query student achievement information, administrators can perform other operations.
Query management: basic operations, including queries and results. A record may be displayed alone, all the information may be displayed.
Input performance management: including query results and basic information. It can be a single record, all the information may be displayed.
Update Management: At the time when needed, the administrator can delete and modify operations and performance information.
Statistics management: statistics on the number of students, the number of absent, grade point average and the number of failing
- Test Type
function test
Test content
Reception: Enter the student number, enter the name and the OK or Cancel performance query and add a personal message
Background: modify user information, change passwords, role management, information browsing, an increase of course increase performance, increase the information.
Test methods used tools and methods
Using black-box testing, the test using the boundary value, the equality test, and other tests equivalence partitioning method, manual testing.
User interface testing
Test content
Including the login page to test the background, font color button name
The method used
Manual testing
Security Access Control Testing
Test content
User name, password, login, user role, access
Test methods used tools and methods
Black box testing, manual testing
- Test Summary of issues
In addition to the program substantially meet the functional requirements, the presence of defects and deficiencies in a number of performance and interface. Jump whole system sometimes can not directly jump such as when students log in, the need to manually jump. Overall interface landscaping deficiencies.
2、Do we need to test until our software is PERFECT？
After time collaboration and project development group of developers, test group staff and related personnel of the week, student management system project completed on schedule and meet the required standards, the program is basically enough to meet the students into the student management system and query performance and personal information case query and modify information, and add information.
We need to test until we complete the program, but not necessarily required to achieve perfect, because there are no software bug, the bug as long as we try to control the range we can control on the line, to do this, we must pass test, test in order to better discover more bug, then solve the bug, bug control number.
3、What is "good enough"for testing?
For the test case in terms of "good" test case must have a complete set of
"Good" test which features must have?
① overall completeness
② accuracy of equivalence partitioning
Completeness set of equivalence classes ③
When you can do the above three points and be sure to test fully complete, that is, to do a complete test coverage needs.