STE Software Testing 22518 Micro Project 5th Semester MSBTE
STE Software Testing 22518 Micro Project 5th Semester MSBTE
Academic Year :
Semester: Fifth
Annexure-I
In today's software environment writing bug-free code is a challenging task, which makes software testing an
important tool to get quality software. Testing techniques include the process of executing a program or
application with the intent of finding software bugs and verifying that the software product is fit for use. Students
will learn the way to find bugs by applying types, levels, and methods of software testing on applications with
an effective test planning approach. It also covers manual testing.
1
3 textbook/manual STE Software testing 22518
annexure-II
Micro-Project Report
In this project, the Online Feedback System will be tested by employing different parameters. Firstly, SRS
(Software Requirement Specification) will be made i.e. it includes all the functional and non-functional needs.
It will be more effortless to use SRS to test the application and find bugs. A Test Plan with a standard format
will be created for this application. Test Cases will be designed to test the functionality of the software. And at
last the Summary Report with a conclusion.
Functionality Requirement Specification
Student Module:
First, the student has to register. Only registered Students will log in by their username and password. In the
dashboard, all the contents of the student’s feedback forms will be shown. There would be an option for student
feedback in this there would be questions associated with how students can make the teaching quality better.
Students can tell their liking and disfavour of the teachers by attending to every question.
Faculty Module:
Here faculty will first log in to this section. The faculty will enter their user name and password if the faculties
do not have an account they have to sign up in order to make an account. As the details are filled the faculty
dashboard appears in which they can fill self-appraisal and peer appraisal. The faculty should first fill the self-
appraisal in which they have to rate themselves on some criteria. The peer faculty has to click on the peer
appraisal in order to fill the form as they click on peer appraisal.
Principal/H.O.D’s Module:
HOD user cannot sign up for the feedback system since she is the only one to access the feature the login is
pre-defined in the code itself. Once the HOD logins into her portal she can perform various tasks like Giving
authority appraisals also reviewing forms no one is duly filled by faculty after verifying that only then the HOD
can further proceed with the summary form. In summary, the total of all marks will be calculated and according
to it, the percentage is calculated also the grades are calculated on this percentage basis also she can take a
printout of the summary list and keep a backup of it.
TEST PLAN
Prepare Test Plan for Online Feedback System
1 Introduction
The Test Plan is prepared to define the scope, approach, resources, and schedule of all testing activities of
the project Online Feedback System. The plan identified the items to be tested, the features to be tested, the
kinds of testing to be performed, the personnel responsible for testing, the resources and schedule needed to
complete testing, and the risks associated with the plan.
1.1 Scope
1.1.1 In Scope
All the features of the Online Feedback System which were defined in software necessity specs are
require to bested
Module
Applicable Roles Description
Name
Students: Students can logout after giving his feedback on the college
Logout Students,Admin online feedback system using Logout option available there.
Admin:Admin can logout after he has collected feedback of students.
These features are not be tested because they are not included in the software requirement specs
User Interfaces
Hardware Interfaces
Software Interfaces
Database logical
Communications Interfaces
Website Security and Performance
Developer in
2 Developer in Test Implement the test cases, test program, test suite etc.
Test
Test Builds up and ensures test environment and assets are managed and maintained
3
Administrator Support Tester to use the test environment for test execution
Take in charge of quality assurance Check to confirm whether the testing process is
4 SQA members
meeting specified requirements
2 Test Methodology
2.1 Test Levels
In the project Online Feedback System, there're 3 types of testing that should be conducted.
Integration Testing (Individual software modules are combined and tested as a group)
System Testing: Conducted on a complete, integrated system to evaluate the system's
compliance with its specified requirements
API testing: Test all the APIs create for the software under tested
If the team members report that there are 40% of test cases failed, suspend testing until the
development team fixes all the failed cases.
Total 28 man-hour
3) Test Deliverables
4) Test Environment
It mentions the minimum hardware requirements that will be used to test the Application. Following software's
required in addition to client-specific software.
Windows 8 and above
Office 2013 and above
5) Terms/Acronyms
TERM/ACRONYM DEFINITION
A test case is usually a single step, or occasionally a sequence of steps, to test the correct
behavior/functionality, and features of an application. An expected result or expected outcome is usually given.
Test Scenario ID
Test Scenario
Test Case ID
Test Case Description
Test Steps
Pre-Conditions
Test Data
Post Conditions
Expected Result
Actual Result
Status
Executed By
Comments if Any
Larger test cases may also contain prerequisite states or steps, and descriptions. A written test case should
also contain a place for the actual result. These steps can be stored in a word processor document,
spreadsheet, database, or another common repository.
In a database system, you may also be able to see past test results and who generated the results, and the
system configuration used to generate those results. These past results would usually be stored in a separate
table.
Test summary
Configuration.
DEFECT REPORT
Application Test Scenario
In our Online Feedback System there is a “Transport Feedback Issue” Module. In that module, the user enters
all details in that form that are required. When a user clicks on submit button it displays a message that the
“Form should be filled completely”, even if the form is filled correctly. Now, we
should report this bug. Now here is how a bug is reported on the basis of the above scenario:
Bug Name: The application crash on clicking the Submit button after filling the Transport Feedback form.
Bug ID:BG_LMS_001
Area Path: Feedback Module.
Build Number:Version Number 9.0.0.1.2
Severity: HIGH
Priority: HIGH (High/Medium/Low)
Assigned to:Pawar.Akanksha.Janardhan
Created By: Pawar.Disha.Sagar
Created On: 22th September 2019.
Reason: Defect
Status: Active
Environment: Windows 2003/SQL Server 2005.
Description:
Application crash on clicking the Submit button after filling Transport Feedback form.
Steps to reproduce:
1. log in to the application.
2. Click on the Feedback Option.
3. Enter the Transport Feedback option.
4. Fill in the details correctly and click on Submit button.
5. Seen an error message.
6. See the attached logs for more information.
7. See the attached screenshots of error the error message for reference. Expected: On clicking the “Submit”
button user should be able to view the message “Transport Feedback Form Registered Successfully.”
1
3 textbook/manual STE Software testing 22518
Conclusion
Software testing is the procedure of estimating and verifying that a software product or
application does what it is supposed to do. The advantages of testing include averting bugs,
lowering development costs, and improving performance.