Professional Documents
Culture Documents
A PROJECT REPORT
Integrated M.Tech
in
Software Testing
By
VINITHA REDDY
(21MIS0156)
AASMITHA.B.G
(21MIS0046)
VINEELA ARANI
(21MIS0166)
Dr.K.Uma
Use Case ID: 1
Actors: People
Description: The securtiy can know whether the person has mask on his face or not via online catalog.
Trigger security wants to know whether the person has mask on him or not.
Includes: None
Priority: High
Special Requirements: Security can view number of people entering in one frame.
Assumptions: None
Actors: People
Description: The security can check how many people are there in one frame.
Includes: None
Priority: High
Assumptions: None
Actors: People
Description: The security can check how many people are there in one frame.
Normal Flow .
• The system displays count of number of people not deetected
• Then the checks it.
Includes: None
Priority: High
Assumptions: None
Actors: people
Description: People will come in and the security gets an image from that mask detection is
done.
Includes: None
Priority: High
Assumptions: None
Normal Flow • When the person enters the image is displayed after 15 seconds
• The count of the people is detected.
• The system detects the mask.
• The mask is detected and the green label is displayed.
If the some other object is detected other than mask, system displays error
message.
Includes: None
Priority: High
Special None.
Requirements:
Assumptions: None
Normal Flow • When the person enters the image is displayed after 15 seconds
• The count of the people is detected.
• The system detects the mask.
• The mask is not detected and the red label is displayed.
Alternative None
Flows:
Includes: None
Priority: High
Business None
Rules:
Special None.
Requirements:
Assumptions: none
Actors: People,security
Description: After receiving the signals we will get to know the number of people wearing mask
Post conditions: Accordings to signals received the people are divided into two categories mask and no
mask people
Normal Flow 1. On the request of the manager campares the signals provided by the people to
system
2. Count will be displayed
None.
Includes: None
Priority: High
Assumptions: none
Actors: people
Post conditions: -
Wrong information’s
Includes: None
Priority: High
Assumptions: None
Overview
Test plan objectives To ensure that the Smart Mask Detection System will:
- To design a hands-free entry system using a face mask detector
in surveillance to combat the further spread of virus.
- This will ensure to reduce the transmission of pathogens on high
touch surfaces and to prevent entry in a community area without
a face mask.
- Will be fine-tuning the resnet architecture,which will help us in
training hundreds of layers quickly and making sure that there
won’t be a drop in training percentage.
Testing Assumptions - It is assumed that camera can click the images which is already
tested.
Risks & Contingencies The following risks apply to the testing process :
- Non uniformity of sizes of different kinds of images of colour
eaxh pixel has huge amount of information which is difficult to
process disturbances in images like poor contrast due to glare.
- Labels are in textual form which were not understood by model.
- The camera focus on the entire image to detect mask,this makes
the program time consuming and inefficient
- The raw video footage size also effected the performance.
Test Scope
Features to be Tested All features, forms, reports and interfaces affected by the smart mask
detection system will be tested. These include:
- Login forms
- User manual
- Image clarity
- Online help
- Search information
- Database used for store the people information.
Features Not to be - Image and system functionality contained within the
Tested Conventional applications and which is not online system
dependant, will not be tested under the scope of this project.
Test Methodologies
Testing Approach The following approach will be used to test the Smart Mask detection
System
- Smart Mask detection system integration & system testing will
be conducted to provide an initial stable testing environment as
follows:
• Integration Testing: Ensure operability of online detection
application within each of the new modules.
• System Testing: Ensure that all the test databases are
accessible for testing.
- Test cases and associated scripts for user acceptance testing are
created.
- For testing the functional specification the unit testing is
performed by the developer using JUnit.
Test Documents The following test documents will be created and maintained
throughout the project lifecycle:
Smart Mask Detection system Test Plan
- Master test case lists for each of the following functional units:
face detector, mask detection , view respective label, add alert
system.
- Test case scripts for each test case recorded in the master test
case list
Test Case Pass/Fail Each Test Case will be evaluated against the acceptance criteria as
Criteria outlined in the test case scripts to determine if the test passed or
failed. In the case of a failure, the tester will assign a severity to the
problem using the appropriate priority rating system established
within Tracker for each application.
Suspension/Resumption Test Cases that do not run to completion will be evaluated on a case
Criteria by case basis to determine if the testing must start over or resume at
the point where the failure occurred. In extremely long test cases,
checkpoints will be established for resumption in the middle of a test
case where appropriate. In general, a test may be resumed in the
middle when the error is not critical.
Problem Errors identified through testing will be logged. Resolve the problem
Logging/Resolution according to the deemed severity level, and update the master test
case list. Once the problem has been fixed, record the resolution into
the database. The failed test case will then be retested using the same
test case script that detected the error in order to verify that the
problem has been rectified.
Resources
Environmental Needs In order to conduct comprehensive end-to-end system and user testing
are the networked system where the functional and non-functional
testing is performed.
Staffing Requirements Developer