Software Testing Vs White Box Testing

Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs, errors or other defects.

Software testing can be stated as the process of validating and verifying that a computer program/application/product meets the requirements that guided its design and development, works as expected, can be implemented with the same characteristics, and satisfies the needs

Input:

Name: varchar

Email id: varchar

Password : varchar

Login As: teacher or a student or a admin

Output: After the login by the above credentials it will redirect the page to user profile page

7.2 STRUCTURAL TESTING

Structural testing also called white-box testing tests internal structures or workings of a program, as opposed to the functionality exposed to the end-user. In white-box testing an internal perspective of the system, as well as programming skills, are used to design test cases. The tester chooses inputs to exercise paths through the code and determine the appropriate outputs.

Statement Coverage

1. Visit website and view details of departments, gallery, recent events, upcoming events.

2. Now login to website to register for events.

3. If student, then register for event else if

4. teacher then add a event.

5. If organizer then he/she can mark attendance.

6. Admin can login to add or delete departments.

7. If done registration, and other things logout else goto user profile.

8.

The main levels during the development process are unit, integration, and system testing that are distinguished by the test target without implying a specific process model. Other test levels are classified by the testing objective.

 Unit testing:

First we checked each and every module independently, whether it is working properly or not. Verification of all the validations are done in each of the indivisual module. Example : event registration, attendance, add event, add departments, view departments.

 Integration testing:

After validating each and every module, modules are now integrated together to test it for some more errors. This kind of testing is done so that no module could contradict the functioning of other. Modules must be checked after integration which gives us exact output or desired output with minimum errors.

 System testing

This is the next level in the testing and test the system as a whole. Once all the components are integrated, the application as a whole is tested rigorously to see that it meets quality standards. This type of testing is performed by a specialized