Scribd
Upload
19 views19 pages

SQE 06part1

Uploaded by

M Huzaifa
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
19 views19 pages

SQE 06part1

Uploaded by

M Huzaifa
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
You are on page 1/ 19

INTRODUCTION TO SOFTWARE

TESTING
SOFTWARE TESTING

❖ Testing is the process of executing a program or system


with the intent of finding errors.” by Myers 1979
❖ Software testing is the process of analyzing a software item
to detect the differences between existing and required
conditions (that is, bugs) and to evaluate the features of the
software item (IEEE, 1986; IEEE, 1990).
PRINCIPLES OF TESTING [1]

Glenford Myers in his book “The Art of Software Testing” suggested the
following testing principles:
✓ A necessary part of a test case is a definition of the expected output or result.
✓ A programmer should avoid attempting to test his or her own program.
✓ Thoroughly inspect the results of each test.
✓ Test cases must be written for input conditions that are invalid and unexpected,
as well as for those that are valid and expected.
PRINCIPLES OF TESTING [1]

✓ Avoid throwaway test cases unless the program is truly a throwaway program.
✓ Do not plan a testing effort under the assumption that no errors will be found.
✓ The probability of the existence of more errors in a section of a program is
proportional to the number of errors already found in that section.
✓ Examining a program to see if it does not do what it is supposed to do is only half
the battle; the other half is seeing whether the program does what it is not
supposed to do.
SOFTWARE TESTING ACTIVITIES

❖ Test Planning
• Define a software test plan by specifying a test schedule for a test
process and its activities, as well as assignments test requirements
and items test strategy
❖ Test Design and Specification
• Conduct software design based well-defined test generation
methods.
• Specify test cases to achieve a targeted test coverage.
SOFTWARE TESTING ACTIVITIES

❖ Test Set up
• Testing Lab Space and tools (Environment Set-up)
• Test Suite Set-up
❖ Test Operation and Execution
• Run test cases manually or automatically
❖ Test Result Analysis and Reporting
• Report software testing results and conduct test result
analysis
SOFTWARE TESTING ACTIVITIES

❖ Problem Reporting
• Report program errors using a systematic solution
❖ Test Management and Measurement
• Manage software testing activities, control testing schedule, measure
testing, complexity and cost
❖ Test Automations
• Define software test tools
• Adopt and use software test tools
• Write software test scripts and facility
❖ Test Configuration Management
• Manage and maintain different versions of software test suites, test
environment and tools, and documents for various product versions.
TESTING METHODS

❖ Manual Testing
❖ Automated Testing
MANUAL TESTING

❖ This type includes the testing of the Software manually i.e.


without using any automated tool or any script.
❖ the tester takes over the role of an end user and test the
Software to identify any unexpected behavior or bug.
❖ Testers use test plan, test cases or test scenarios to test the
Software to ensure the completeness of testing.
AUTOMATED TESTING

❖ A process in which software tools execute pre-scripted


tests on a software application.
❖ This process involves automation of a manual process.
❖ Automation is a not a Replacement of Manual Testing
AUTOMATED TESTING

❖ Done properly, automated software testing can help to:


 minimize the variability of results
 speed up the testing process
 increase test coverage, and
 ultimately provide greater confidence in the quality of the
software being tested.
TEST CASE

❖ A test case is a set of conditions or variables under which a


tester will determine whether an application or software
system meets specifications.
❖ A test case has components that describes an input, action
or event and an expected response, to determine if a feature
of an application is working correctly.
❖ A test case may include many subsets.
TEST CASE

❖ Test Case ID: It is unique number given to test case in


order to be identified
❖ Test description: The description of test case you are
going to test
❖ Revision history: Each test case has to have its revision
history in order to know when and by whom it is created or
modified.
❖ Function to be tested: The name of function to be
tested.
❖ Test Setup: Anything you need to set up outside of your
application for example printers, network and so on.
TEST CASE

❖ Test Execution: It is detailed description of every step of


execution.
❖ Expected Results: The description of what you expect the
function to do
❖ Actual Results: pass / failed
• If pass - What actually happens when you run the test
• If failed - put in description of what you've observed.
TEST CASE

• Test case for login creation?


• User name must be of type character and
password must be minimum of length 6.
TESTING TYPES

❖ Black Box Testing


❖ White Box Testing
BLACK BOX TESTING

“Black-box testing is a method of software testing that


examines the functionality of an application without peering
into its internal structures or workings”
WHITE BOX TESTING

❖ “a method of testing software that tests internal


structures or workings of an application”, as opposed to its
functionality.
❖ also known as clear box testing, glassbox testing,
transparent box testing, and structural testing).
REFERENCE

 GlenFord Myers, “The Art of Software Testing” 2nd Edition, chapter 2 (article:
software testing principles)

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy