Scribd
Upload
4 views

Assignment 2

The document outlines the differences between errors, defects, and failures in software development, explaining how coding mistakes lead to errors, which can result in defects and ultimately failures when the software does not meet user expectations. It describes the Software Requirements Specification (SRS) as a black box specification, focusing on system functionality without revealing internal details. Additionally, it provides detailed test cases for a signup page and user login validation for the KIET ERP system.

Uploaded by

rahul.2024cs1043
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4 views

Assignment 2

The document outlines the differences between errors, defects, and failures in software development, explaining how coding mistakes lead to errors, which can result in defects and ultimately failures when the software does not meet user expectations. It describes the Software Requirements Specification (SRS) as a black box specification, focusing on system functionality without revealing internal details. Additionally, it provides detailed test cases for a signup page and user login validation for the KIET ERP system.

Uploaded by

rahul.2024cs1043
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Assignment-2

Q1. Difference between Error vs Defects vs failures.


The Problem in code leads to errors, which means that a mistake can occur due
to the developer's coding error as the developer misunderstood the requirement
or the requirement was not defined correctly. The developers use the term error.

When the application is not working as per the requirement is knows as defects.
It is specified as the aberration from the actual and expected result of the
application or software.

In other words, we can say that the bug announced by the programmer and
inside the code is called a Defect.

Many defects lead to the software's failure, which means that a loss specifies a
fatal issue in software/ application or in its module, which makes the system
unresponsive or broken.

In other words, we can say that if an end-user detects an issue in the product,
then that particular issue is called a failure.

Q2. Why is SRS also known as the black box specification of system?
SRS is also known as the black box specification of system because it describes
the system’s functionality and behavior without revealing its internal structure
or implementation details. It focuses on what the system does rather than how it
does it. A black box is a device or system that can be viewed in terms of its
inputs and outputs, without any knowledge of its internal workings. Similarly,
an SRS document specifies the inputs and outputs of the software system, as
well as the constraints and requirements that govern its operation, without
exposing the underlying code or design.
Q3. Wite test cases for testing a signup page of KIET ERP.
Here are some possible test cases for testing a signup page of KIET ERP:

 Verify that the signup page has the following input fields: username,
email, password, confirm password, role, department, and captcha.
 Verify that the signup page has the following buttons: sign up, cancel,
and login.
 Verify that the signup page has the following links: terms of service,
privacy policy, and forgot password.
 Verify that the username field accepts alphanumeric characters and
underscores, and has a minimum length of 4 and a maximum length of 20
characters.
 Verify that the email field accepts valid email addresses in the format
[email protected], and does not allow duplicate email addresses.
 Verify that the password field accepts alphanumeric characters and
special symbols, and has a minimum length of 8 and a maximum length
of 16 characters.
 Verify that the confirm password field matches the password field, and
shows an error message if they do not match.
 Verify that the role field has a drop-down list of predefined roles, such as
student, faculty, staff, or admin.
 Verify that the department field has a drop-down list of predefined
departments, such as CSE, ECE, ME, or CE.
 Verify that the captcha field displays a random image of alphanumeric
characters, and requires the user to enter the same characters in the text
box.
 Verify that the sign up button is enabled only when all the input fields are
filled with valid data, and disabled otherwise.
 Verify that the cancel button clears all the input fields and redirects the
user to the home page.
 Verify that the login button redirects the user to the login page.
 Verify that the terms of service link opens a new tab with the terms of
service document.
 Verify that the privacy policy link opens a new tab with the privacy
policy document.
 Verify that the forgot password link redirects the user to the password
recovery page.
 Verify that the signup page has a logo, a title, and a footer with the KIET
ERP name and contact information.
 Verify that the signup page is responsive and adapts to different screen
sizes and orientations.
 Verify that the signup page is accessible and follows the web content
accessibility guidelines (WCAG).
 Verify that the signup page is secure and uses HTTPS protocol.

Q4. Write test cases for verifying a user id and password , Also write the
validation cases.
 Verify that the user id and password fields are visible and enabled on the
login page.
 Verify that the user id field accepts alphanumeric characters and
underscores, and has a minimum length of 4 and a maximum length of 20
characters.
 Verify that the password field accepts alphanumeric characters and
special symbols, and has a minimum length of 8 and a maximum length
of 16 characters.
 Verify that the user id and password fields are case-sensitive, and do not
allow leading or trailing spaces.
 Verify that the user can log in with a valid user id and password, and is
redirected to the home page or dashboard.
 Verify that the user cannot log in with an invalid user id or password, and
is shown an error message.
 Verify that the user cannot log in with a blank user id or password, and is
shown an error message.

You might also like