Questionnaire: Requirements, Test Cases & Bug Reporting

Question 1: Write test cases for the login functionality in HRIS. You need to cover "Remember me" and
"Forgot Password" functionality

Ans: Login page should have the following things-a)Username Textbox b)Password Textbox c)Sign in
Button d)Remember Me Box e) Forgot Password Link

Test Cases for Login functionality in HRIS are : 1) Verify if the username textbox is working

2) Verify if the login page contains elements such as username, password, sign in , remember me box,
forgot password link.

3)Verify if the Enter key works as the substitute of sign in button.

4)Verify that fields such as username, password has the right authority.

5)Verify if the user is able to login with the valid credentials and is not able to login with the wrong
credentials.

6)Verify that the user is not able to login with the inactive credentials or blank credentials.

7)Verify that the password is stored in the database in the encrypted form, and when entered is also in
encrypted form.

8)Verify that the user should also be able to login ,after changing the password.

9)Verify the remember password checkbox is unselected by default.(Should depend on the user )

10)Verify that the user is redirected to forgot password page when clicking on the forgot password link .

Question 2: What is the difference between Requirement Based Test Cases and Scenario Based Test
Cases?

Ans:

TEST CASE TEST SCENARIO

1.It consists of -test case name, Preconditions,
steps/input condition, expected results.
2. Test cases are low level actions and it can be
derived from test scenarios.
3. Test case are set of steps which performed on
system to verify the expected output.
4. Test case means detailed documenting the
cases which help in executing while testing.
1.Test scenario consists of a detailed test
procedure.
Test scenario also has many test cases associated
with it. Before execution of the test scenario, we
need to think of test cases for each scenario.
2. Test scenarios are the high level classification
of test requirements grouped depending on the
functionality of a module and it can be derived
from use case.
3. Test scenario are thread of operations .
4. Test scenario means talking and thinking
requirements in detail.
Question 3: What is Equivalence Partitioning and Boundary Value Analysis? Please explain with
examples.

Ans: Boundary Value Analysis: It is a form of Black Box Testing technique, used to find errors at the
boundaries of the input domain, rather than finding these errors at the center of input. Its basic aim is to
select input variable values at their minimum, just above the minimum, just below the minimum, a
nominal value ,just below the maximum ,maximum and just above the maximum.

This means for each range there are two boundaries , the lower boundary and the upper boundary and
these boundaries are the beginning and end of each valid partition.

EXAMPLE: suppose , if the input is a set of values between A and B, then design test cases for A,A+1,A-1
and B,B+1,B-1.

AGE (enter age in the box) *Accepts any value from 18 to 56

Equivalence Partitioning: It is also known as equivalence class partitioning . In this method, the input
domain data is divided into different equivalence data classes- which is termed as Valid and Invalid.

EXAMPLE: Suppose the application you are testing accept values in the character limit of 1-100 only.

Here there would be three partitions: One valid partition and two invalid partitions.

Question 4: What is the difference between Priority & Severity? Please provide examples of:

Ans:

Priority Severity
It is defined as the impact on the application Defined by the impact on business
functionality.
Deals with technical aspects of the application Deals with the timeframe or the order to fix the
defects
Category is decided by testers Category decided by the developers or the
product owners

 High Severity / High Priority -A site maintaining the details of the student (on saving details if it
doesn’t save details then it is ) high severity/high priority bug
 High Severity / Low Priority- If an application or the web page crashes so the severity is high
and priority becomes low.
 Low Severity / High Priority-
 Low Severity / Low Priority

Questions 5: What is the difference between Functional and Non-Functional requirements? Give an
example of each type of requirement.

Ans -

Functional Non-Functional
It defines a system or its component It defines the quality attribute of a software
system
It specifies What should the system do ?
It is mandatory
It is captured in use case
Example – authentication of user whenever
he/she logs into the system
It specifies How should the software system fulfill
the functional requirements?
It is not mandatory
It is captured as a quality attribute
Example-Emails should be sent with a latency of
no greater than 12 hours from such an activity