0% found this document useful (0 votes)
5 views4 pages

Test Cases for Web and Application Testing

Uploaded by

Manthan Bhavsar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
5 views4 pages

Test Cases for Web and Application Testing

Uploaded by

Manthan Bhavsar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Practical No : 06

Design test cases for Web Pages Testing any Web Sites.

Test Test Case Precondition Input Expected Actual Status


Case Output Output
ID
Check home Browser is Open the Page should Page should
page open, home fully load fully load
TC01 loading time internet page URL within 3 within 3 Pass
connection seconds seconds
is stable
Verify Home page Click on Contact Us Contact Us
redirection is loaded "Contact page should page should
to "Contact Us" link open with open
TC02 Us" page correct Pass
contact
details and
form
Check Home page Click each Each link Each link is
navigation is loaded link in the should not should be
TC03 menu links navigation redirect to the redirect to the
Fail
menu correct correct
corresponding corresponding
page page
Test search Home page loaded Search results Search results
functionality is loaded page displays page displays
Enter a items
TC04 keyword matching the Pass
in search keyword
bar, click
"Search"
Verify Login page is Click on Password Password
"Forgot loaded "Forgot reset link is reset link is
Password" Password," sent to sent to
TC05 Pass
functionality enter registered registered
registered email email
email
Practical No : 07
Design test cases for the following Control and Decision Making
Statement.

Test Case Test Case Precondition Input Expected Actual Status


ID Output Output
Verify the System is
output for ready to number: Even Even
TC01 an even accept an 4 Pass
number integer input

Verify the System is


output for ready to number: Odd Odd
an odd accept an 7
TC02 Pass
number integer input

Check System is
output for ready to number: Even Odd
the accept an 0
TC03 smallest integer input Fail
even
number
(0)
Verify the System is
system ready to number: - Even Even
behavior accept an 6
TC04 for a integer input Pass
negative
even
number
Verify the System is
system ready to number: - Odd Even
behavior accept an 9
TC05 for a integer input Fail
negative
odd
number
Practical No : 10
Prepare defect report after executing test cases for library
management system

Defect Defect Project name Module name Date Severity Priority Descrip Status
ID name & tion
Tester
Book Library Search 2024- High Critical Search
Search Manage Module 11-11 function
Functi ment and 2 ality is
onality Not System broken and
Working does not Open
D-01 return
results for
valid search
terms.

Book Library Checkout 2024- Medium High Checkout


Checkout Manage Module 11-12 page takes
Page Slow Ment and 1 more than
Loading System 10 seconds
D-02 In
to load,
Progress
causing
user
frustration.
Missing Library Catalog 2024- Low Low Some
Book Manage Module 11-11 books in
Details in ment and 4 the catalog
Catalog System are missing
D-03 key details Resolved
like author
and
publication
year.
Login Page Library Authentication 2024- High High The login
Not Management Module 11-11 page is not
D-04 Responsive System and 2 responsive Open
on mobile
devices.
Practical No : 13
Design and run test cases for WordPad (MS Window based). Using an
Automated tool.

Test Test Pre- Steps Input Expected Actual Status


case Case condition data result result
ID Name

[Link]
Application application
New blank
Should be [Link] on file Click on Opening
TC01 New file must Pass
Operate menu “new” new file
be opened
well [Link] "new"
menu
[Link]
application
Existing
Application [Link] on file File
Selected Opening
Should be menu Location
TC02 Open File Selected Pass
Operate [Link] & file
Should be file
well "open" menu name
opened
& browser
Required file.
Application File
Existing Saving
Should be Location
TC03 Save Click - Save File must Selected Pass
Operate & file
Be saved file
well name
Application
Exiting
Should be Exit from
TC04 Exit Click - Exit - From Pass
Operate editor
editor
well
Application
Not exit
Should be Exit from
TC05 Exit Click - Exit - from Fail
Operate editor
editor
well

Common questions

Powered by AI

Systematic use of preconditions ensures that the system is in a suitable state for testing, reducing variability and increasing the accuracy of test outcomes. Preconditions like having the browser open and stable internet enhance effectiveness by ensuring the environment is consistent and conducive to executing test cases like loading time evaluations or navigation checks, which improves the reliability of test results .

The documented failings, such as incorrect page redirection and system's incorrect behavior in handling edge cases like the smallest even number (0), indicate areas where system design needs improvement. These issues suggest the need for more robust handling of navigation and input validation rules to ensure all scenarios are correctly managed. Addressing these failings by revising logic and implementation can prevent similar issues and improve overall system performance .

Executing test cases allows for systematic verification of each system component against expected behaviors, making defect detection more efficient. In a library management system, this approach identifies defects like slow page loading and non-responsiveness, which can then be prioritized and addressed to improve system performance and user experience .

Not conducting proper testing on a WordPad application could lead to missed functionality issues such as failures in saving or opening files which can impede usability and user satisfaction. These challenges can be mitigated by executing thorough test cases that simulate real-world scenarios, thus ensuring the software behaves as expected under different conditions, as demonstrated by the detailed test cases for opening, saving, and exiting functionalities .

Unresolved defects can significantly impair the functionality of a library management system by causing features to malfunction or operate suboptimally. For instance, unresolved defects like a non-responsive login page or broken search functionality can lead to user dissatisfaction, reduced system usability, and can hinder operational efficiency, potentially affecting the credibility and operational capabilities of the system .

The methodology crucial for ensuring a website's user functionality involves designing comprehensive test cases that cover various aspects of the user experience. The test cases include verifying page loading times, redirection links, navigation menus, search functionalities, and login features to ensure that each element performs as expected under specified conditions .

Automated tools enhance testing by allowing repetitive tasks to be executed consistently and efficiently, ensuring comprehensive coverage of test scenarios. For applications like WordPad, they enable the execution of test cases for functionalities such as opening, saving, and exiting files with precision, reducing human error and increasing the reliability of test results .

Severity and priority ratings help in effective defect management by categorizing defects based on their impact on system operations and urgency for resolution. A high-severity defect indicates significant system impact, requiring rapid resolution to prevent major disruptions. Coupled with priority ratings, these assessments guide resource allocation and problem-solving efforts, ensuring that critical defects are addressed promptly to maintain software performance and user satisfaction .

Identification and prioritization of defects are significant because they help developers focus on critical issues that could hinder system functionality. High-priority defects, such as those affecting user login responsiveness or search functionalities, impact user satisfaction and system usability and therefore require immediate attention. Proper identification ensures efficient resource allocation in fixing issues, enhancing the user experience and system reliability .

Results of a failed test case provide insights into weaknesses or logic errors in the system, indicating where design elements might not align with user requirements or specifications. Analyzing these results can inform design adjustments and refinement of testing strategies, ensuring that the system is better aligned to meet functional requirements and providing a feedback loop to enhance future system iterations .

You might also like