Scribd
Upload
36 views

ISE Question Bank Answers

The document contains four test cases for a registration or sign up process in a software. It provides the test case ID, title, description, preconditions, test steps and expected result for each test case. The test cases cover successful registration with valid data, registration with an existing email, registration with a weak password, and registration with mismatched passwords.

Uploaded by

chaudharirohan2825
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
36 views

ISE Question Bank Answers

The document contains four test cases for a registration or sign up process in a software. It provides the test case ID, title, description, preconditions, test steps and expected result for each test case. The test cases cover successful registration with valid data, registration with an existing email, registration with a weak password, and registration with mismatched passwords.

Uploaded by

chaudharirohan2825
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

ISE Question Bank Answers

10. Differentiate Unit Testing and Integration testing.


6. Sketch Flow chart for a process of vehicle rental system.
11. Write any four test cases for Registration/Sign Up process in any software.

Test Case 1: Successful Registration with Valid Data

Test Case ID: TC_REG_001


Title: Successful Registration with Valid Data
Description: Verify that a user can successfully register with valid data.
Preconditions: The registration page is accessible.

Test Steps:

1. Navigate to the registration page.


2. Enter a valid username (e.g., "user123").
3. Enter a valid email address (e.g., "[email protected]").
4. Enter a valid password (e.g., "Password123!").
5. Confirm the password.
6. Click the "Register" or "Sign Up" button.

Expected Result: The user is registered successfully, and a confirmation message is displayed. The
user is redirected to the welcome page or login page.

Test Case 2: Registration with Existing Email

Test Case ID: TC_REG_002


Title: Registration with Existing Email
Description: Verify that a user cannot register with an email address that is already in use.
Preconditions: The email address to be tested is already registered in the system.

Test Steps:

1. Navigate to the registration page.


2. Enter a valid username (e.g., "user456").
3. Enter an email address that is already registered (e.g., "[email protected]").
4. Enter a valid password (e.g., "Password123!").
5. Confirm the password.
6. Click the "Register" or "Sign Up" button.

Expected Result: An error message is displayed, indicating that the email address is already in use.
The user remains on the registration page.
Test Case 3: Registration with Weak Password

Test Case ID: TC_REG_003


Title: Registration with Weak Password
Description: Verify that a user cannot register with a password that does not meet the security
requirements.
Preconditions: The registration page is accessible.

Test Steps:

1. Navigate to the registration page.


2. Enter a valid username (e.g., "user789").
3. Enter a valid email address (e.g., "[email protected]").
4. Enter a weak password (e.g., "12345").
5. Confirm the password.
6. Click the "Register" or "Sign Up" button.

Expected Result: An error message is displayed, indicating that the password is too weak or does not
meet the security requirements. The user remains on the registration page.

Test Case 4: Registration with Mismatched Passwords

Test Case ID: TC_REG_004


Title: Registration with Mismatched Passwords
Description: Verify that a user cannot register if the password and password confirmation fields do
not match.
Preconditions: The registration page is accessible.

Test Steps:

1. Navigate to the registration page.


2. Enter a valid username (e.g., "user987").
3. Enter a valid email address (e.g., "[email protected]").
4. Enter a valid password (e.g., "Password123!").
5. Enter a different password in the confirm password field (e.g., "Password321!").
6. Click the "Register" or "Sign Up" button.

Expected Result: An error message is displayed, indicating that the passwords do not match. The
user remains on the registration page.
In table format,
1. Determine equivalence classes and boundary value test suite for a program to
accept any number between 1 and 99.

To determine equivalence classes and boundary value test cases for a program that accepts any
number between 1 and 99, we need to consider both valid and invalid inputs. Here’s how it breaks
down:

Equivalence Classes

1. Valid Equivalence Class:

 Input values between 1 and 99 (inclusive).

2. Invalid Equivalence Classes:

 Input values less than 1.


 Input values greater than 99.
 Non-numeric input values (e.g., characters, symbols).

Boundary Value Test Suite

Boundary value testing involves testing the boundaries between equivalence classes. For the given
range, the boundaries are around 1 and 99.

1. Valid Boundary Values:


 Lower boundary: 1
 Just above lower boundary: 2
 Upper boundary: 99
 Just below upper boundary: 98
2. Invalid Boundary Values:
 Just below the lower boundary: 0
 Just above the upper boundary: 100
Test Cases

These test cases ensure comprehensive coverage of the input space for the program by testing both the
boundaries and typical values within the equivalence classes.
5. Sketch a Gantt chart for the Leave Management System with all SDLC phases
completed in 12 weeks.

SDLC Phases and Tasks:

1. Requirement Analysis (2 weeks)

 Gather requirements
 Analyze requirements
 Document requirements

2. System Design (2 weeks)

 High-level design (architecture)


 Detailed design (database schema, UI/UX design)
 Review and approval

3. Implementation (4 weeks)

 Set up development environment


 Coding (frontend and backend development)
 Unit testing

4. Integration and Testing (2 weeks)

 Integrate modules
 System testing
 Bug fixing

5. Deployment (1 week)

 Prepare deployment environment


 Deploy the system
 Post-deployment testing

6. Maintenance (1 week)

 Monitor system performance


 Fix post-deployment issues
 Provide user training and support
Gantt Chart Representation:

Week 1 2 3 4 5 6 7 8 9 10 11 12
Req. Gathering & Analysis
System Design
Implementation
Integration & Testing
Deployment
Maintenance

You might also like