Seminar Report

on

“Seminar Title”
Submitted to the

Savitribai Phule Pune University

In partial fulfilment for the award of the Degree of

Bachelor of Engineering

in

Information Technology

By

Student Name [Roll No.]

Under the guidance of

Guide Name

Department Of Information Technology

Marathwada Mitra Mandal's College of Engineering

Karvenagar, Pune-411052, Maharashtra, India

2023-24
 CERTIFICATE
This is to certify that the seminar report entitled “Seminar Title” being submitted by Student
Name, Roll Number is a record of bonafide work carried out by her under the supervision and
guidance of Guide Name in partial fulfillment of the requirement for TE (Information
Technology Engineering) – 2019 course of Savitribai Phule Pune University, Pune for the
academic year 2023- 24

Date:
Place: Pune

Dr. R.M.Chopade Dr. R.M.Chopade Dr. V.N.Gohokar

Guide Head of the Department Principal

This project-based seminar report has been examined by us as per the Savitribai Phule Pune
University, Pune, requirements at Marathwada Mitra Mandal's College of Engineering, Pune on Date

2
 ACKNOWLEDGEMENT

I am extremely grateful to Guide Name, Department of Information Technology, for providing all the
required resources for the successful completion of my seminar and for her valuable suggestions and
guidance in the preparation of the seminar report. I express my thanks to all staff members and
friends for all the help and co-ordination extended in bringing out this seminar successfully in time. I
will be failing in duty if I do not acknowledge with grateful thanks to the authors of the references
and other literatures referred to in this seminar.

Isha Agarwal, TI01

 3
Abstract
This report describes Test-Comp 2021, the 3rd edition of the Competition on Software Testing. The
competition is a series of annual comparative evaluations of fully automatic software test generators
for C programs. The competition has a strong focus on reproducibility of its results and its main goal
is to provide an overview of the current state of the art in the area of automatic test-generation. The
competition was based on 3 173 test-generation tasks for C programs. Each test-generation task
consisted of a program and a test specification (error coverage, branch coverage).
Test-Comp 2021 had 11 participating test generators from 6 countries.

4
 Table of Contents

Sr No. Chapter Page no.

1 Introduction of software testing 7

1.2 Introduction to 7

1.3 Introduction to Email Spam Detection 7

1.4 Motivation 8

1.5 Aim & Objectives 8

2 Literature Survey 9

2.1 Study on Literature Survey 10

3 Methodology and Algorithms Used 11

3.1 Formula Used 12

3.1 Example 13

3.2 Algorithms 14

4 Performance Analysis 15

4.1 Performance Comparison of Classifiers 15

5 Outline and Future Scope 16

6 Conclusion 17

7 References 18

5
List of Figures
Figure No. Figure Name Pg No.

1.1 Bayes formula for conditional probability 11

1.2 Flowchart- Naïve Bayes example 12

1.3 Flowchart- Naïve Bayes 13

6
 CHAPTER 1
Introduction

1.1 Introduction to Machine Learning

In a software development project, errors can be creeping at any stage during the development.
For each phase we have discussed different techniques for detecting and eliminating errors that
 originates in that phase. During testing, the program to be tested is executed with a set of test
cases, and the output of the program for the test case is evaluated to determine if the program is
performing as it is expected to. Due to its approach, dynamic testing can only as certain the
presence of error in the program; the exact nature of the error is not usually decided by testing.
Testing forms the first step in determining the errors in a program. Clearly the success of testing
revealing errors in programs depends critically on the test cases.

1.2 Introduction to Email Spam Detection

Testing is the process of running a system with the intention of finding errors.Testing enhances the
integrity of a system by detecting deviations in design and errors in the system. Testing aims at
detecting error-prone areas. This helps in the prevention of errors in a system. Testing also adds
value to the product by conforming to the user requirements. The most common causes of errors in
an e-commerce system are:

• Communication gaps between the developer and the business decision maker.

• Time provided to a developer to complete the project.

• Over commitment by the developer.

1.2 Motivation

Software testing is a critical and integral part of the software development process, and there are
several compelling motivations for it:

Quality Assurance: The primary motivation for software testing is to ensure the quality and
reliability of the software. Testing helps identify and rectify defects, bugs, and vulnerabilities in the
software, ensuring that it meets the desired standards and specifications.
 1. Risk Mitigation: Testing helps identify and mitigate risks associated with software
deployment. By identifying and addressing issues early in the development process, you
can reduce the likelihood of costly and disruptive problems occurring in the production
environment.
2. Customer Satisfaction: Thorough testing leads to a higher quality product, which, in turn,
leads to increased customer satisfaction. When customers encounter fewer issues and
defects, they are more likely to have a positive experience with the software.
3. Legal and Regulatory Compliance: Many industries have strict regulations and legal
requirements that software must adhere to. Effective testing ensures that the software
complies with these regulations, helping organizations avoid legal consequences.

1.3 Aim and Objective(s) of the software testing

The aim and objectives of software testing are to ensure the quality and reliability of software
by systematically and thoroughly evaluating it. This process helps identify defects, bugs, and
vulnerabilities, allowing for their correction before the software is released or deployed. Here are
the key aims and objectives of software testing

1. Defect Detection: The main objective is to detect defects, bugs, and errors in the software.
This includes identifying issues related to functionality, performance, security, and usability.
2. Validation of Requirements: Software testing aims to validate that the software meets the
specified requirements and that it functions as intended.
3. Performance Assessment: Testing evaluates the software's performance, scalability, and
responsiveness under various conditions to ensure it can handle expected workloads.
4. Security Verification: The objective is to identify and address security vulnerabilities and
weaknesses in the software to protect it from potential threats.
5. Usability Testing: This aims to assess the software's user-friendliness and how well it meets
the needs of its intended users.
6. Compatibility Testing: Ensure the software works correctly on different platforms, browsers,
and devices to reach a wider audience.
7. Regression Testing: The objective is to ensure that new changes or updates do not
introduce new defects and do not adversely affect existing functionalities.
8. Documentation and Reporting : Software testing generates documentation and reports that
capture the testing process, results, and any issues found. This objective helps in tracking
and managing the testing effort.

1.4 Software reliability

E-commerce requires software that performs critical tasks. Such as creating storefront and a
shopping cart, collecting customer data, and providing the payment gateway. This software needs
to function correctly. Testing assures the organization of the quality and integrity of the e-
commerce solution
CHAPTER 2
LITERATURE SURVEY

STUDY OF LITERATURE SURVEY

Table 1.1
Sr Paper Title Publicati Authors Findings
No. on &
Year

1 Design and code IBM - 22 (IBM Engineer) Introduced the concept of

Inspections to Septemb Michael Fagan ‘Fagan Inspection’, which
reduce Errors in er 1976 were considered good practice
Program but extremely burdensome
development

10
 CHAPTER 3
Methodology & Algorithms Used

3.1) Methodology :

Software testing methods are traditionally divided into two parts. These are :-

1. White box testing

2. Black-box testing

These two approaches are used to describe the point of view that a test engineer takes when
designing test cases.

1. WHITE BOX TESTING

White box testing is when the tester has access to the internal data structures and algorithms
including the code that implement these
 All independent paths within a module have been exercised at least once
 Exercise all logical decisions on their true and false sides
 Execute all loops at their boundaries and within their operational bounds
 Exercise internal data structures to ensure their validity

2. BLACK BOX TESTING

Black box testing treats the software as a "black box"—without any knowledge of internal
implementation. Black box testing methods include: equivalence partitioning, boundary value
analysis, all-pairs testing, fuzz testing, model-based testing, exploratory testing and
specification-based testing.

 Based on requirements and functionality

 Not based on any knowledge of internal design or code

 Covers all combined parts of a system

 Tests are data driven

Specification-based testing
Specification-based testing aims to test the functionality of software according to the applicable
requirements. Thus, the tester nputs data into, and only sees the output from, the test object. This
level of testing usually requires thorough test cases to be provided to the tester, who then can
simply verify that for a given input, the output value (or behavior), either "is" or "is not" the same
as the expected value specified in the test case. Specification-based testing is necessary, but it is
insufficient to guard against certain risks.

Advantages and disadvantages:

The black box tester has no "bonds" with the code, and a tester's perception is very simple: a
code must have bugs. Using the principle, "Ask and you shall receive," black box testers find
bugs where programmers do not. On the other hand, black box testing has been said to be "like a
walk in a dark labyrinth without a flashlight," because the tester doesn't know how the software
being tested was actually constructed. As a result, there are situations when
(1) a tester writes many test cases to check something that could have been tested by only one
test case, (2) some parts of the back-end are not tested at all. Therefore, black box testing has
the advantage of "an unaffiliated opinion", on the one hand, and the disadvantage of "blind
exploring", on the other.
 11

Bayes Formula for conditional probability-

12
Example

Algorithms Used

Fig 1.3

14
CHAPTER 4
Performance Analysis
 15

CHAPTER 5
Outline and Future Scope
 16

CHAPTER 6
 CONCLUSION
.
 REFERENCES

1. A. Karim, S. Azam, B. Shanmugam, K. Kannoorpatti, and M. Alazab, ‘‘A comprehensive survey

for intelligent spam email detection,’’ IEEE Access, vol. 7, pp. 168261–168295, 2019 2. E. Bauer. 15
Outrageous Email Spam Statistics That Still Ring True in 2018, RSS. Accessed: Oct. 10, 2020.
[Online].
3. R. M. Ravindran and D. A. S. Thanamani, ‘‘K-means document clustering using vector space
model,’’ Bonfring Int. J. Data Mining, vol. 5, no. 2, pp. 10–14, Jul. 2015
4. S. Halder, R. Tiwari, and A. Sprague, ‘‘Information extraction from spam emails using stylistic
and semantic features to identify spammers,’’ in Proc. IEEE Int. Conf. Inf. Reuse Integr., Aug.
2011
5. D. Hao, L. Zhang, J. Sumkin, A. Mohamed, and S. Wu, ‘‘Inaccurate labels in weakly-supervised
deep learning: Automatic identification and correction and their impact on classification
performance,’’ IEEE J. Biomed. Health Informat., vol. 24, no. 9, pp. 2701–2710, Sep. 2020
18