1. Boutique product development company
It is amazing what you can accomplish when you have a client-centric team to deliver outstanding products.
Name / Job Role

2. Software Testing Concepts and Definition
Presented by Naseer Ahmad / Prepared by Sikandar Ahmed

3. Primary purpose of testing is to detect software
failures, so that defects may be discovered and
corrected.
Items to be covered
• Concepts
• SQA vs Testing
• Test Senario vs Test Cases
• Testing Cycle
• Testing Definitions
• Testing Methods
• Testing Levels
• Testing Types

4. SQA VS Testing
4

5. Software Quality Assurance
• SQA consists of a means of monitoring the software
engineering processes and methods used to ensure quality.
• In SQA, software process specialists and auditors are concerned for the
software development process rather than just the artifacts such as
documentation, code and systems.
• They examine and change the software engineering process itself to
reduce the number of faults that end up in the delivered software
• SQA is the implementation of policies and procedures intended to
prevent defects from occurring in the first place.
5

6. Software Testing
• Software testing is a task intended to detect defects in software by
contrasting a computer program's expected results with its actual
results for a given set of inputs.
• Software testing is a part of the software quality assurance (SQA)
process.
6

7. Test Plan
•A test specification is called a test plan.
•A test plan is a document detailing a systematic approach to testing
a system/software.
•The plan typically contains a detailed understanding of the
eventual workflow.
•There are three major elements that should be described in the test
plan, These are also used in a formal test strategy:
•Test Coverage
•Test Methods
•Test Responsibilities
7

8. Test Scripts
• A test script is a procedure, or programming code that replicates
user actions.
• Test Case will be a baseline to create test scripts using a tool or a
program.
8

9. Traceability Matrix
• A traceability matrix is a table that correlates requirements or
design documents to test documents.
• It is used to change tests when related source documents are
changed
• The Purpose to select test cases for execution when planning for
tests by considering requirement coverage.
9

10. Test Scenario VS Test Case
Test Scenario is “What to be tested”
Test Case is “How to be tested”.
10

11. Test Scenario
• It is also known as Test Suite or less commonly Validation Suite.
• A test scenario is a collection of test cases that are intended to be
used to test a software program
• Purpose is to show that it has some specified set of behaviors.
• It often contains detailed instructions or goals for each collection of
test cases and information on the system configuration to be used
during testing.
11

12. Test Case
• A test case is a set of conditions or variables under which a tester
will determine whether an application, software system or one of its
features is working as it was originally established for it to do.
• A test case is usually a single step, or occasionally a sequence of
steps, to test the correct behavior/functionality, features of an
application.
• For a Test case, an expected result or expected outcome is usually
given.
12

13. Test Data
• In most cases, multiple sets of values or data are used to test the
same functionality of a particular feature.
• All the test values and changeable environmental components are
collected in separate files and stored as test data.
• It is also useful to provide this data to the client and with the
product or a project.
13

14. Example: Login Feature
Test Scenarios of Login Feature:
1) Verify UI components of the Login screen.
2) Verify functionality of Login.
3) Verify functionality of Keep me logged in.
4) Verify functionality of Forget password.
14

15. Example: Login Feature (Cont.)
Test Scenario 2: Verify functionality of Login
List of Test Cases:
1) Click on login button with enter valid username and password.
2) Click on login button with enter username only (Password left empty).
3) Click on login button with enter password only (username left empty).
4) Click on login button without username and password (both are empty).
5) Click on login button with enter invalid username and password.
15

16. Example: Login Feature (Cont.)
Test Case 1: Click on login button with enter the username and password.
Step1: Click in user name text box and enter user name in this field.
Expected Result: It allows to type username.
Step2: Click in password text box and enter password in this field.
Expected Result: It allows to type password and it should not visible to
user.
Step 3: Click on Login button.
Expected Result: System verifies user name and password if both are valid
then user should be logged in successfully.
16

17. Basic Testing Cycle
• Requirements Analysis
• Test Planning
• Test Development
• Test Execution
• Test Reporting
• Test Result Analysis
• Defect Retesting
• Regression Testing
• Test Closure
17

18. Thank You
18