Black box Testing TechniquesBY : Sampath kumar MDATE : 16-09-2015

Agenda

Overview of Quality Assurance and Testing Black Box Testing Black Box - Test Design Techniques Live Examples in Test Design techniques (TalentOz)

Testing Overview

FUNCTIONAL• COMPONENT (UNIT) TESTING• INTEGRATION TESTING• SYSTEM / END-TO-END TESTING

NON-FUNCTIONAL• PERFORMANCE• SECURITY• COMPATIBILITY• USABILITY• LOCALIZATION

Classification Of TestingBy the object of testing: Functional Testing Performance Testing Load testing/Stress testing

(stability / endurance / soak testing) Usability Testing Testing the user interface (UI testing) Security Testing Localization Testing Compatibility Testing

By the basis of positive scenario: Positive testing Negative testing

➢ Smoke Testing➢ New feature Testing➢ Regression Testing➢ Acceptance Testing➢ Alpha Testing➢ Beta Testing

By the time of testing:

According to the degree of automation Manual testing Automation Testing Semi-automated testingBy degree of preparedness to be tested Documentation Testing (formal testing) Test Ad-hoc or Intuitive Testing (Ad-hoc

Testing)

By the knowledge of the system:

Testing the black box

Testing the white box

Testing the grey box

✓ TESTING OF FUNCTIONAL PART OF THE APPLICATION

✓ NEED NOT HAVE ANY FORMAL STRUCTURAL KNOWLEDGE OF THE CODE

✓ TESTING ENGINEERS✓ WHY NO DEVELOPERS DO

THIS TESTING ????What is Black Box Testing ?

Test Design Techniques

Typical black-box test design techniques include:✓ State Transition✓ Equivalence Partitioning✓ Boundary Value analysis✓ Decision Table testing (Cause effect

graph)✓ Error guessing

Equivalence Partitioning Live TalentOz Example

Invalid Salary Field

Valid Salary field

Invalid Salary field

Invalid Salary Field

Invalid Salary Field

A,B,C……Z 1,2,3,……. a,b,c,d,….z !,@,#..... -1,-2,-3…..

Considering Gross Salary as input field, which accepts only Positive numbers

Boundary Value AnalysisLive TalentOz Example

Considering Day, Month As input possibilitiesInvalid – Valid boundary

Day field (Lower)Invalid – Valid boundary

Day field (Upper)Below Boundary Above Boundary Below Boundary Above Boundary

0 1 31 33

Invalid – Valid boundary Month field (Lower)

Invalid – Valid boundary Month field (Upper)

Below Boundary Above Boundary Below Boundary Above Boundary

0 1 12 13

▪ Most of errors occurs at boundary▪ You test boundaries between equivalence partitions

Decision Table TestingLive TalentOz Example

This Decision Table explains about the Competency Assessment in Live Talentoz.

Test Combination of inputs that produce different results.

Also called as Cause-effect testing

Created Combination of conditions that might get grayed out during ad-hoc testing methodology

Rule 1 Rule 2 Rule 3Cause 1Cause 2Cause 3Effect 1Effect 2

1. Identify cause & effect2. Establish relation relation between cause

and effect3. Add constraints between cause and effect

4. Convert graph as table5. Generate Test Case

Error Guessing

Assumptions and Guessing

The success of error guessing is very much dependent on the skill of the tester

 Blank (or no) input, empty files and the wrong kind of data (e.g. alphabetic characters where numeric are required)

For E.g.From the requirement tester should be able to guess the error possibility1. Requirement : Employee Status Inactive expected

employee should not be allowed to login Error guess : Login Authentication one of the critical error occurring area

2. Requirement : Employee with Approved leave will not fall in learning recommendation Error Guess : Integration between one module & another may cause regression due to new requirements

Q&A

Thank you