Ste Pracs Solved
Ste Pracs Solved
1. User A sends
Both users "Hello" to User User B should see User B did not
Send a
TC01 are logged B. the "Hello" receive the Fail
message
in. 2. User B opens message. message.
the chat.
1. User A sends a
Send an Both users are smiley emoji. User B should see Emoji was not
TC02 Fail
emoji logged in. 2. User B checks the smiley emoji. delivered.
the chat.
1. User A starts
Both users typing. "User A is Indicator
Check typing
TC03 are logged 2. User B typing..." is appeared as Pass
indicator
in. observes the chat visible. expected.
window.
1. Open app.
Valid 2. Enter correct User logs in
Login with Login
TC04 account username and and sees the Pass
credentials successful.
exists. password. chat list.
3. Click login.
Test Case ID Description Preconditions Test Steps Expected Result Actual Result Status
1. Click on the
The Find dialog
Open Find Notepad is "Edit" menu. The Find dialog opens
TC01 opened without Pass
Dialog opened 2. Select "Find" or successfully.
issues.
press "Ctrl + F".
1. Open Notepad.
2. Type some
text.
Search for a non- Notepad is 3. Press "Ctrl + F". A message "Word not No message
TC02 Fail
existing word open 4. Enter a non- found" should appear. appeared.
existing word.
5. Click "Find
Next".
1. Open
Notepad.
2. Type the
Search for an Notepad is word "apple". The word "apple" The word "apple"
TC03 Pass
existing word open 3. Press "Ctrl + should be highlighted. was highlighted.
F".
4. Search for
"apple".
Find 1. Click on the "Cancel" The Find dialog
Cancel Find The Find dialog
TC04 dialog is button in the Find closes without Pass
Operation closed successfully.
open dialog. errors.
Test
Description Preconditions Test Steps Expected Result Actual Result Status
Case ID
1. Input 5.
2. Press the The result
Test addition Calculator is Result
TC01 + button. displayed should Pass
functionality on displayed is 8.
3. Input 3. be 8.
4. Press =.
1. Input 10.
2. Press the - The result
Test subtraction Calculator is Result
TC02 button. displayed should Pass
functionality on displayed is 6.
3. Input 4. be 6.
4. Press =.
1. Input 7.
2. Press the The result Result
Test multiplication Calculator is
TC03 * button. displayed should displayed is Pass
functionality on
3. Input 6. be 42. 42.
4. Press =.
Test
Description Preconditions Test Steps Expected Result Actual Result Status
Case ID
1. Input 12.
2. Press the / The result
Test division Calculator is Result
TC04 button. displayed should Fail
functionality on displayed is 5.
3. Input 4. be 3.
4. Press =.
Password User is on the login 1. Click on the "Forgot User is redirected to the
TC003 Recovery Link page. Password?" link. password recovery page.
Reusable Test Cases: One of the greatest advantages of automation is that once a test script is
created, it can be reused multiple times throughout the software development lifecycle. Automated
tests can be reused during different testing phases, such as unit testing, integration testing, and
regression testing. This reduces the need to rewrite test cases and saves time and effort, making the
testing process more efficient
(Test cases in manual testing need to be recreated or re-executed from scratch during different
phases of testing, such as unit testing, integration testing, and regression testing. This lack of
reusability increases the time and effort required, making the process less efficient.)!!!
More Accuracy and constintency: Automation testing is less prone to human error, leading to
consistencies and accuracies in results.
(Less Accuracy and…: Manual testing is prone to human error, leading to inconsistencies and
inaccuracies in results.)!!
Manual tests are not easily scalable. manual testing become harder to manage as software
complexity increases. It increase time ,cost and efforts required for testsing ,making it difficult to
handle large or complex projects effectively.
Highly Scalable: Automated testing is easily scalable, even as software complexity increases. It
reduces the time, cost, and effort required for testing, making it efficient and effective for handling
large or complex projects.
Automated testing is more reliable suitable for complex and large projects due to more efficiency in
testing process. (opposite)!!
Disadvantages of automated :
Requires high Expertise: Once automated test scripts are created, they cannot be executed
by team members since it requires high-level expertise. This increase the need for highly
skilled testers during execution.
High cost: Automation tests have a high cost of implementation as tools are required for
testing, thus adding the cost to the project budget.
Costly Test Maintenance: Maintaining test scripts is expensive, especially when the
application undergoes frequent changes.
Trained employees required: For conducting automated tests, trained employees with
knowledge of programming languages and testing knowledge are required.
Proficiency Required for Writing Automated Test Scripts: Writing automated test scripts
demands proficiency in programming and testing knowledge.
Exploratory testing is not possible since exploratory testing involves exploring the system
deeply without test scripts.
A test plan is a document that describes the scope, approach, resources and schedule required for
conducting testing activities
The test plan acts as the anchor for the execution, tracking and reporting of the entire testing
project.
3. Setting up criteria for testing: There must be clear entry and exit criteria for different phases
of testing. The test strategies for the various features and combinations determined how these
features and combinations would be tested.
1. New: When a defect is first discovered, it is reported and marked as "New." The defect is
logged in the defect tracking system with details like severity, priority, etc.
2. Assigned: Once the defect is reviewed, it is assigned to a developer for resolution. The
developer is responsible for fixing the defect.
3. Open: The developer starts working on the defect to analyze and resolve it. During this
phase, they either fix the bug or mark it as invalid or deferred if it's not a defect or should
be fixed later.
4. Fixed: After the defect is resolved by the developer, it is marked as "Fixed" and sent to the
testing team for retesting.
5. Retest: The tester retests the defect to ensure that it has been correctly fixed.
6. Reopen: If the defect persists after the retesting, it is marked as "Reopened" and sent back
to the developer for further analysis.
7. Verified: If the defect is fixed and works as expected, the tester marks it as "Verified."
8. Closed: If the defect is no longer reproducible and the fix works as expected, it is marked
as "Closed." This indicates that the defect has been successfully resolved.
9. Deferred: If the defect is valid but not critical to fix immediately (e.g., planned for a future
release), it is deferred for later.
10. Rejected: If the defect is not valid, misunderstood, or does not need any fix, it is rejected
by the development team.
1. Defect ID
Description: A unique identifier assigned to each defect for easy tracking and reference.
2. Defect Description
Description: A detailed explanation of the defect, including the problem observed and the
expected behavior.
Example: "The login page allows access even with an incorrect password. Expected behavior:
Access should be granted only with the correct password."
3. Severity
Description: Indicates the impact of the defect on the system, ranging from Critical to Low.
Example: Severity: Critical for a defect that crashes the system when trying to load the
homepage.
4. Priority
Description: Specifies the urgency with which the defect should be resolved, ranging from
High to Low.
5. Steps to Reproduce
Description: Detailed steps to recreate the defect so developers can fix it efficiently.
Example:
6. Environment
Description: The environment in which the defect was found, including the operating
system, browser, or application version.
Description: The current stage of the defect in its lifecycle (e.g., Open, In Progress, Resolved,
Closed).
Example: Status: Open for a newly reported bug not yet addressed.
8. Assigned To
Description: The name or ID of the developer or team responsible for fixing the defect.
9. Defect Type
Description: Categorizes the defect (e.g., Functional, Performance, UI, or Security defect).
Example: Defect Type: Functional, for a defect where the "Submit" button fails to save the
form data.
10. Attachments
Description: Additional files, such as screenshots, logs, or videos, that provide evidence of
the defect.
o Verify that users can register with their phone number and receive a verification
code successfully.
3. Group Messaging
o Test sending messages to a group and ensuring all members receive them.
4. Media Sharing
o Test the file size limit and ensure proper compression without data corruption.
6. Status Updates
o Verify that users can upload text, images, or videos as a status update.
7. Search Functionality
o Verify the ability to search for messages, chats, or contacts within the app.
o Verify that users can back up chats to cloud storage (Google Drive or iCloud).
User Login
Check if a user can log in using a valid phone number and verification code.
Sending Messages
Receiving Messages
Group Chats
Media Sharing
Voice Calls
Status Update
Ensure users can add a status update and view others' statuses.
Search Feature
Severity Medium
Priority Medium
Summary Forgot Password link fails to redirect to the password recovery page.
When a user clicks on the "Forgot Password?" link on the login page, the link does not
Description function correctly, and the user remains on the login page instead of being redirected to
the password recovery page.
Status Open
Actual Result The user remains on the login page after clicking the "Forgot Password?" link.
Expected The user should be redirected to the password recovery page upon clicking the
Result "Forgot Password?" link.