STE Software testing 22518 Micro Project 5th semester MSBTE
program Name and Code: STE Software testing 22518
Course Name and Code: CS 5I
Academic Year :
Semester: Fifth
annexure-I
A MICRO PROJECT ON AN "ONLINE FEEDBACK SYSTEM "
1.0 Aims/Benefits of the micro project
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.
2.0 Course outcome addressed.
a) Apply various software testing methods.
b) Prepare test cases for different types and levels of testing.
c) Prepare test plans and defect bug reports.
d) Discipline knowledge: Apply computer engineering knowledge to solve broad-based
computer engineering-related problems.
e) Engineering tools: Apply appropriate computer engineering-related techniques/tools with
an understanding of the limitations.
f) Communication: Proper communication takes place between students and faculty.
3.0 Proposed methodology
a) Apply different software testing methods.
b) Prepare test cases for different types and levels of testing.
c) Prepare test plans and defect bug reports.
d) Discipline knowledge: Use computer engineering knowledge to solve broad-based computer engineering-related problems.
e) Engineering tools: Apply appropriate computer engineering-related techniques/tools with an understanding of the limitations.
f) Communication: Proper communication takes place between students and faculty.
4.0 Action Plan
| Sr. No. | Detail of activity | Plan start date | Plan finish date | Name of responsible team members |
|---|---|---|---|---|
| 1 | Searching the topic for micro-project | |||
| 2 | collect information from the internet and textbook | |||
| 3 | collect information from the STE Software testing 22518 reference book | |||
| 4 | arrange all information in ms word | |||
| 5 | Prepare a report on it using MS word | |||
| 6 | print micro project |
5.0 Resources used
| Sr. no. | Name of resource material | Specifications | Quantity |
|---|---|---|---|
| 1 | Computer System | 4 GB RAM, Windows 8.1 OS | 1 |
| 2 | Internet | Youtube / Wikipedia | |
| 3 | textbook/manual | STE Software testing 22518 | 1 |
annexure-II
Micro-Project Report
A MICRO PROJECT ON "ONLINE FEEDBACK SYSTEM "
1.0 Brief Introduction/Rationale
In this project, we are going to test an Online Feedback System using Software Testing. The online feedback system is a web-based system that provides a way for colleges to allow students to give feedback to staff online to improve their teaching. Students are required to give feedback using one standard feedback form. In our project, the security is also maintained by the result of feedback being only visible to the authentic users. This project also includes a time portal. This system helps teachers to improve their performance by analyzing the feedback given by students. The above features will be tested using Software testing different techniques in this project. This system is not time-bound due to which students will give monthly feedback.
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 RequirementSpecification
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 disfavor 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 Name | Applicable Roles | Description |
|---|---|---|
| Registration | Students, Faculty,HOD, Principal | Students:A student can register into the college feedback system by entering his Name, then Password again confirm password field, as well as Email ID and Mobile No. will be required here. Either he/she can register or login if he/she has an account already over the system |
| Login | Students, Admin | Students:Only the students who are admitted in that college will be provided with a specific username and password. He/She can login the college online feedback system by entering correct username and password allocated to them. If He/She don‟t have account He/She can register using registration process available in that feedback system and then login to the system. Admin:Admin can login in the Feedback system to see whether how many students have given their feedback and prepare a note on their feedbacks. |
| Feedback | Student | Student: Here in this Feedback module there are number of Feedback partitions.Such as :- 1. Course Feedback, here a student can give a feedback for each subject. 2. Staff feedback, here a student can give feedback on staff. 3. Event Feedback, here a student can give feedback related to all events which are being carried out in the college. 4.College Feedback, here a student can give feedback related to college buildings, water purifiers, washrooms, Office, etc.5. Transport Feedback, here a student can give feedback related to transport system of students such as Bus transport, etc. 6. Canteen Feedback, here a student can give feedback related to canteen, items sold in canteen, their costing more or less, etc. |
| Logout | Students,Admin | Students: Students can logout after giving his feedback on the college online feedback system using Logout option available there. Admin:Admin can logout after he has collected feedback of students. |
1.1.2 Out of Scope
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
1.2 Quality Objective
The test objectives are to verify the functionality of the Online Feedback System the project should focus on testing the Feedbackoperation to guarantee all these operations can work normally in real business environments.
1.3 Roles and Responsibilities
The project should use outsourced members as the tester to save the project cost.
| No. | Member | Tasks |
|---|---|---|
| 1 | Test | Identifying and describing appropriate test techniques/tools/automation architecture Verify and assess the Test Approach Execute the tests, Log results, Report the defects. Outsourced members |
| 2 | Developer in Test | Developer in Test Implement the test cases, test program, test suite etc. |
| 3 | Test Administrator | Builds up and ensures test environment and assets are managed and maintained Support Tester to use the test environment for test execution |
| 4 | SQA members | Take in charge of quality assurance Check to confirm whether the testing process is 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
2.2 Suspension Criteria and Resumption Requirements
If the team members report that there are 40% of test cases failed, suspend testing until the
development team fixes all the failed cases.
2.3 Test Completeness
Specifies the criteria that denote successful completion of a test phase
The run rate is mandatory to be 100% unless a clear reason is given.
The pass rate is 80%, and achieving the pass rate is mandatory
2.4 Project task and estimation and schedule
| Task | Members | Estimate effort |
|---|---|---|
| Create the test specification | Test Designer | 12man-hour |
| Perform Test Execution | Tester, Test Administrator | 10man-hour |
| Test Report | Tester | 6man-hour |
| Total | 28 man-hour |
3) Test Deliverables
Test deliverables are provided below
Before testing phase
Test plans document.
Test cases documents
Test Design specifications.
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
Make a mention of any terms or acronyms used in the project
| TERM/ACRONYM | DEFINITION |
|---|---|
| API | Application Program Interface |
| AUT | Application Under Test |
TEST CASE DESIGN
A test case is a specification of the inputs, execution conditions, testing procedure, and expected results that define a single test to be executed to achieve a particular software testing objective, such as to exercise a particular program path or to verify compliance with a specific requirement.Test cases underlie testing that is methodical rather than haphazard. A battery of test cases can be built to produce the desired coverage of the software being tested. Formally defined test cases allow the same tests to be run repeatedly against successive versions of the software, allowing for effective and consistent regression testing.
Typical Written Test Case Format:-
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.
Additional information that may be included:
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 suites often also contain
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.”
2.0 Actual Resources Use
| Sr. no. | Name of resource material | Specifications | Quantity |
|---|---|---|---|
| 1 | Computer System | 4 GB RAM, Windows 8.1 OS | 1 |
| 2 | Internet | Youtube / Wikipedia | |
| 3 | textbook/manual | STE Software testing 22518 | 1 |