Module 5

Validation And Verification

Software Testing

• Testing is intended to show that a program does what it is intended to

do and to discover program defects before it is put into use.

• Developers always are driven by “Delivery” whereas independent

testers by “Quality”.

• “Testing can only show the presence of errors, not their absence.”

• Discover problems
• Testing is a broader process of software verification and validation (V
& V)
• Verification and validation processes are concerned with checking
that software being developed meets its specification and delivers the
functionality expected by the people paying for the software.
• These checking processes start as soon as requirements become
available and continue through all stages of the development process.
• Software verification is the process of checking that the software meets
its stated functional and non-functional requirements.

• Software validation is to ensure that the software meets the customer’s

expectations.

• It goes beyond checking conformance with the specification to

demonstrating that the software does what the customer expects it to
do.
• The goal of verification and validation processes is to establish
confidence that the software system is “fit for purpose.”
• This means that the system must be good enough for its intended
use.
• The level of required confidence depends on the system’s purpose,
the expectations of the system users, and the current marketing
environment for the system
Terminologies in Testing
• Bug
• Defect
• Error
• Fault
• Failure
• Incident
Strategic Approach to Software Testing
Software testing steps
“When are we done testing—how do we know that we’ve
tested enough?”
What guidelines lead to a successful software
testing strategy?
• Specify product requirements in a quantifiable manner long before testing
commences.
• State testing objectives explicitly.
• Understand the users of the software and develop a profile for each user
category.
• Develop a testing plan that emphasizes “rapid cycle testing.”
• Build “robust” software that is designed to test itself.
• Use effective technical reviews as a filter prior to testing
• Conduct technical reviews to assess the test strategy and test cases themselves.
• Develop a continuous improvement approach for the testing process.
TEST STRATEGIES FOR
CONVENTIONAL SOFTWARE
• Unit Testing
Integration testing: Top-down Testing
Integration testing: Bottom-up Testing
Regression testing
Essential tools used for regression testing
• Selenium
• Ranorex Studio
• Quick Test Professional (QTP)
• Rational Functional Tester (RTF)
Smoke testing
• It is designed as a pacing mechanism for time-critical projects,
allowing the software team to assess the project on a frequent basis.
Smoke test for an online shopping platform
1. Verifying user registration and login processes
2. Checking the product catalog and search functionality
3. Adding items to the cart and proceeding to checkout
4. Completing a purchase using different payment methods
5. Ensuring order confirmation and tracking information
TEST STRATEGIES FOR OBJECT-
ORIENTED SOFTWARE
1. Unit Testing in the OO Context
• Class testing for OO software is the equivalent of unit testing for
conventional ware.
• Unlike unit testing, class testing for OO software is driven by the
operations encapsulated by the class and the state behavior of the
class.
Integration Testing in the OO Context
• Thread-based testing, integrates the set of classes required to
respond to one input or event for the system.
• Each thread is integrated and tested individually.
• Regression testing is applied to ensure that no side effect occur.
• The second integration approach i.e. the use-based testing, begins the
construction of the system by testing those classes (called
independent classes) that use very few (if any) of server classes.
• After the Independent classes are tested, the next layer of classes,
called dependent classes, that use the independent classes are tested.
This sequence of testing layers of dependent classes continue until
the entire system is constructed.
Testing strategies(10) for WebApps
1. The content model for the WebApp is reviewed to uncover errors.
2. The interface model is reviewed to ensure that all use cases can be
accommodated.
3. The design model for the WebApp is reviewed to uncover navigation
errors.
4. The user interface is tested to uncover errors in presentation and/or
navigation mechanics.
5. Each functional component is unit tested.
6. Navigation throughout the architecture is tested.
7. The WebApp is implemented in a variety of different environmental
configurations and is tested for compatibility with each
configuration.
8. Security tests are conducted in an attempt to exploit vulnerabilities
in the WebApp or within its environment.
9. Performance tests are conducted.
10. The WebApp is tested by a controlled and monitored population of
end users. The results of their interaction with the system are
evaluated for content and navigation errors, usability concerns,
compatibility concerns, and WebApp reliability and performance.
VALIDATION TESTING
1. Validation-Test Criteria
• After each validation test case has been conducted, one of two
possible conditions exists:
(1) The function or performance characteristic conforms to
specification and is accepted or
(2) a deviation from specification is uncovered and a deficiency
list is created.
2. Configuration Reviews / Audits
3. Alpha and Beta Testing (Customer Acceptance Testing)
System Testing
• fully exercise the computer-based system
1. Recovery Testing
2. Security Testing
3. Stress Testing
4. Performance Testing
5. Deployment Testing / Configuration testing
TEST CASES and TEST
SCENARIOS
• A test case is a set of instructions that describe how to test a
particular feature or functionality of an application. It includes the
following components:
• Pre-conditions: The conditions that must be met before the test can
be executed.
• Test steps: The steps that need to be taken to execute the test.
• Expected results: The results that are expected when the test is
executed.
Test scenarios
• A test scenario is a high-level description of how a particular feature
or functionality of an application should work.
• It is typically written in plain English and is not as detailed as a test
case.
• Test scenarios are often used to create test plans, which are
documents that describe the overall testing strategy for an
application.
• Test cases are used to execute tests, while test scenarios are used to
create test plans.
Example
• "login" feature of an application
Test case for the "login" feature of an
application
Pre-conditions:
• The user must have a valid account.
• The application must be running.
Test steps:
• Enter the user's username and password in the login form.
• Click the "Login" button.
Expected results:
• The user is logged in and redirected to the home page.
• "add to cart" feature of an e-commerce website.
Pre-conditions:
• The user must be logged in to the website.
• The user must have added at least one product to their cart.
Test steps:
• Click on the "Add to Cart" button for a product.
• Verify that the product is added to the cart.
• Click on the "Cart" icon.
• Verify that the product is displayed in the cart.
Expected results:
• The product is added to the cart.
• The product is displayed in the cart.
• Try to write Test Scenario for this.
Test scenario:
• The user is able to log in to the application by entering a valid
username and password.
Example
• Write Test Scenarios For An ECommerce Website
General Test Cases:
• Check if the website links redirect to appropriate category pages/
product pages.
• Check if all the category pages have proper products listed in the
category.
• Check if the count of the total number of products listed on the
category page is right or wrong.
• Check if the products have proper visibility, price, category name,
product description, company logos, and details.
Home Page Test Cases:
A home page on an eCommerce website is much more than a
simple display of products. The page usually is viewed as a
clickable slideshow or an image, more like an auto-scroll that
redirects the user to particular pages. And as this is the hero
section, it becomes a crucial space for marketing as well.
• Check when the image refreshes and see if the page auto-scrolls.

• Check if clicks are taking you to the right page and product deal.

• Check the loading time of the pages.

• Check if the content like banners, footer, newsletter, social media

links, and more are correctly visible and clickable.

• Check if the homepage is looking and performing in the same manner

in different browsers and screen resolutions
Search Test Cases:

• The moment one opens an eCommerce site, they go right to the

opinion in search for the products, so make sure it works as expected.
• Check if the right search results view properly when typed with their
product name, brand name, and more.

• Check if the right number of results are projected per page.

• Check if different options are available based on the brand, price,

ratings, reviews, etc.

• Check if, in the case of multiple-page results, there are many options
available to navigate between them.
Payments Test Cases:

• Most of the customers quit the site once they fail to make a payment.
So, this is another area to test rigorously.
• Check if all the payment options are working fine as anticipated.
• Check if customers can checkout as mere guests for making a
payment.
• Check if there are returning customers. Does the page prompt them
to sign in?
• Perform security tests for the storage of users’ credit card
information. (it’s at all costs, and is quintessential to secure the
customer’s sensitive information)
• Check what the return page shows after the payment is completed.
• Check if the customer receives a message after making the payment.
Shopping Cart Page Test Case:

• A shopping cart is what makes an eCommerce website complete. And

special attention there is very much recommended. So, the customer
can swiftly select, store many items in their shopping cart, and buy
them.
• Check if all item’s costs are correctly displayed in the shopping cart.
• Check if the options work, let the user add items to the cart, and
proceed to the checkout.
• Check if the options of adding more items are working correctly.
• Check if the to remove items works in the checkout.
• Check if the taxes are charged as per the location.
• Check if the option of applying for coupons works.
• Check if the shipping costs are accurate as per the selected shipping
options.