Sipna College of Engineering & Technology, Amravati.
Department of Computer Science & Engineering
Branch :- Computer Sci. & Engg. Class :- III Year
Subject :- Software Engineering Lab Sem :- VI
Manual
PRACTICAL NO 9
Aim: Write Down the Test Case scenario for Login page authentication.
Theory:
Case Study
Let us see how we can design test cases to verify the "User Login" feature. The simplest scenario
is when both user name and password have been typed in correctly. The outcome will be that the
user could then avail all features of LIS. However, there could be multiple unsuccessful
conditions:
User ID is wrong
Password is wrong
User ID & password are wrong
Wrong password given twice consecutively
CSE/SEM-VI/SE Lab/PR
Sipna College of Engineering & Technology, Amravati.
Department of Computer Science & Engineering
Wrong password given thrice consecutively
Wrong password given thrice consecutively, and security question answered correctly
Wrong password given thrice consecutively, and security question answered incorrectly
We would create test case for the above stated login scenarios. These test cases together would
constitute a test suite to verify the concerned requirement. Table 1 shows the details of this test
suite.
Table 1: A test suite to verify the "User Login" feature
# TS1
Title Verify "User Login" functionality
Description To test the different scenarios that might arise while an user is trying to login
Post-
# Summary Dependency Pre-condition Execution Steps Expected Output
condition
Verify that
user already Employee 1. Type in employee ID
registered ID 149405 is a as 149405
with the LIS registered user of 2. Type in
User is "Home" page for the
TC1 is able to LIS; user's password this_is_pass
logged in user is displayed
login with password word
correct user is this_is_passwor 3. Click on the 'Login'
ID and d button
password
1. Type in employee ID
Verify that an The "Login" dialog is
Employee as 149405xx
unregistered User is shown with a "Login
ID 149405xx is not 2. Type in
TC2 user of LIS is not failed! Check your user
a registered user of password whatever
unable to logged in ID and
LIS 3. Click on the 'Login'
login password" message
button
Verify that
Employee
user already 1. Type in employee ID
ID 149405 is a The "Login" dialog is
registered as 149405
registered user of User is shown with a "Login
with the LIS 2. Type in
TC3 LIS; user's not failed! Check your
is unable to password whatever
password logged in user ID and
login with 3. Click on the 'Login'
is this_is_passwor password" message
incorrect button
d
password
TC4 Verify that TC3 This test case is User is 1. Type in employee ID The "Login" dialog is
user already executed after not as 149405 shown with a "Login
registered execution of TC3 logged in 2. Type in failed! Check your user
with the LIS before executing password whatever2 ID and
is unable to any other test case 3. Click on the 'Login' password" message
CSE/SEM-VI/SE Lab/PR
Sipna College of Engineering & Technology, Amravati.
Department of Computer Science & Engineering
Table 1: A test suite to verify the "User Login" feature
# TS1
Title Verify "User Login" functionality
Description To test the different scenarios that might arise while an user is trying to login
Post-
# Summary Dependency Pre-condition Execution Steps Expected Output
condition
login with
incorrect
password give
button
n twice
consecutively
Verify that
user already The "Login" dialog is
registered 1. Type in employee ID shown with a "Login
This test case is
with the LIS as 149405 failed! Check your
executed after User is
is unable to 2. Type in user ID and
TC5 TC4 execution of TC4 not
login with password whatever3 password" message;
before executing logged in
incorrect 3. Click on the 'Login' the security question
any other test case
password button and input box for the
given thrice answer are displayed
consecutively
Email
Verify that a sent
registered This test case is containing
user can login executed after new
after three execution of TC6 password. 1. Type in the answer Login dialog is
consecutive before executing The email as my_answer displayed; an email
TC6 TC5
failures by any other test case. is 2. Click on the 'Email containing the new
correctly Answer to the expected Password' button password is received
answering the security question to be
security is my_answer. received
question within 2
minute.
TC7 Verify that a Execute the test User 1. Type in the answer The message "Your
registered cases TC3, TC4, account as not_my_answer account has been
user's and TC5 once has been 2. Click on the 'Email blocked! Please
account is again (in order) blocked Password' button contact the
blocked after before executing administrator." appears
three this test case
consecutive
failures and
answering
the security
CSE/SEM-VI/SE Lab/PR
Sipna College of Engineering & Technology, Amravati.
Department of Computer Science & Engineering
Table 1: A test suite to verify the "User Login" feature
# TS1
Title Verify "User Login" functionality
Description To test the different scenarios that might arise while an user is trying to login
Post-
# Summary Dependency Pre-condition Execution Steps Expected Output
condition
question
incorrectly
In a similar way, test suites corresponding to other user requirements could be created as well. A
good test plan can reduce the burden of testing team by specifying what exactly they should
focus on.
Conclusion: Thus we have studied designing a test cases and test suites.
Branch :- Computer Sci. & Engg. Class :- III Year
Subject :- Software Engineering Lab Sem :- VI
Manual
PRACTICAL NO 10
Aim : Introduction to Agile Methodology
Theory :
An agile methodology is an iterative approach to software development. Each iteration of agile
methodology takes a short time interval of 1 to 4 weeks. The agile development process is
aligned to deliver the changing business requirement. It distributes the software with faster and
fewer changes.
The single-phase software development takes 6 to 18 months. In single-phase development, all
the requirement gathering and risks management factors are predicted initially.
The agile software development process frequently takes the feedback of workable product. The
workable product is delivered within 1 to 4 weeks of iteration.
CSE/SEM-VI/SE Lab/PR
Sipna College of Engineering & Technology, Amravati.
Department of Computer Science & Engineering
A Scrum Team is made up of three roles:
the Product Owner, Scrum Master, and Development Team. These teams are self-organizing
(they decide how to work) and cross-functional (they have all the skills needed to complete a
CSE/SEM-VI/SE Lab/PR
Sipna College of Engineering & Technology, Amravati.
Department of Computer Science & Engineering
task without external help).
Scrum teams work in sprints, which are short, fixed periods during which a “Done” product
increment is created. Feedback is gathered at each step to improve the product continuously. Key
Scrum values that guide team behavior include Courage, Focus, Commitment, Respect, and
Openness.
Scrum Roles:
Product Owner: Manages the product backlog, prioritizes work, and maximizes product value.
Scrum Master: Ensures Scrum practices are followed, helps remove roadblocks, and supports
the team and organization.
Development Team: Builds the product. They are self-managed and accountable as a group.
Scrum Events:
Sprint: Time-boxed development cycle.
Sprint Planning: Decide what to do in the Sprint.
Daily Scrum: Short daily team meeting.
Sprint Review: Review completed work.
Sprint Retrospective: Reflect and improve.
Scrum Artifacts:
Product Backlog: List of work to be done.
Sprint Backlog: Tasks selected for the current sprint.
zncrement: Completed, usable product output.
Scrum promotes a transparent, adaptive, and team-driven approach to product development,
focusing on collaboration and continuous improvement.
Scrum Lifecycle
CSE/SEM-VI/SE Lab/PR
Sipna College of Engineering & Technology, Amravati.
Department of Computer Science & Engineering
The Scrum Lifecycle starts with a prioritized backlog, but does not provide any guidance as to
how that backlog is developed or prioritized, which consists of a series of Sprints that yield the
end result as a potentially shippable product increment as shown in the Figure below.
Inside of these sprints, all of the activities necessary for the development of the product occur
on a small subset of the overall product. Below is a description of the key steps in the Scrum
Lifecycle:
Th
The agile scrum framework
The business sets priorities; the team self-organizes to deliver them.
The Product Owner manages the product backlog and sets feature priorities.
In Sprint Planning, the team selects top-priority tasks to work on (sprint backlog).
Work is done in Sprints (2–4 weeks), with daily Scrum meetings to track progress.
The Scrum Master ensures the team stays on track.
Each sprint ends with a review and retrospective.
After each sprint, a new set of tasks is chosen from the backlog.
The cycle continues until the project is complete or time/budget runs out.
CSE/SEM-VI/SE Lab/PR
Sipna College of Engineering & Technology, Amravati.
Department of Computer Science & Engineering
Conclusion: Thus we have studied the concept of Agile Methodology
CSE/SEM-VI/SE Lab/PR
