Dynamic Analysis: Test Design Techniques for Software Testing, Lecture notes of Software Engineering

Download Dynamic Analysis: Test Design Techniques for Software Testing and more Lecture notes Software Engineering in PDF only on Docsity!

Chapter 5:

Dynamic Analysis-Test Design Techniques

Software Testing

Lecture 2

Agenda for Today

Test Object Execution

Test Bed and why it’s necessary

Systematic and Stepwise Approach for Test cases

Test Design Techniques

Static and Dynamic Testing

Introduction to Black box Testing

Why Test Bed?

Test object will call parts of program.

Not ready

Stubs simulate the input/output

Test bed configured ap per need of AUT

Right environment ensures success

Testers must expand or modify the test bed

Flaws lead to extra cost and time

Fig. Test Bed

Systematic and Stepwise approach for

determining test cases

Systematic Approach:

 Many requirements should be checked.

 Little cost

 This goal requires systematic approach

Stepwise Approach:

 Determine conditions and preconditions

 Specify the individual test cases

 Determine how to execute the tests

Software Test Design Techniques

First of all we should know

 Technique?

• Efficient way

 Tester design technique?

• Select good set of tests

 Why we need to use the tester design technique?

• Exhaustive testing not possible
• Intelligent process needed for selection

Static vs Dynamic Testing

 Static Testing

• Without execution
• Verification process
• Prevention of defects
• Defects finding cost is less
• Loads of meetings
• Walkthrough, Inspection, reviews etc.

 Dynamic Testing

• With execution
• Validation process
• Finding and fixing defects
• Defects finding cost is high
• Lesser meetings
• Specification based, structure based, Experience based, unit testing, integration testing etc.

Static vs Dynamic Testing

Categories of Test Design Techniques

Typically we have 3 categories:

 Black-box (specification-based)

 White-box (structured-based)

 Experience-based

Black Box Testing Example

This form of testing technique will check the input and output.

• A user logged in when inputs correct username and correct password
• A user receives an error message when enters username and incorrect password

Black box testing checks scenarios where the system can break.

Black Box Testing

Point of observation and Point of control situated at outside the test object.

Test object can be your module/component, System.

PoC are appropriate test data, appropriate test precondition.

PoO is output, result

Testing Approaches

 Manual Testing:

• Checks the system as a user.
• Processing time
• Not much reliable
• UI change
• Suitable when the test cases are run once or twice

 Automated UI Testing:

• user interaction with the system is recorded to find errors
• Reliable
• Processing time
• Time required for automated testing is less
• Testing Tools: selenium, Quick Test Professional (QTP) , Cross-Browser testing,

Loadrunner, JMeter etc

White Box Testing

Internal structure needed

It focuses primarily on verifying the flow of inputs and outputs through

the application, improving design and usability, strengthening security.

Black and White Box

Testing

Black Box Testing White Box Testing

Black box testing is the Software testing

method which is used to test the software

without knowing the internal structure of

the program.

White box testing is the software testing

method in which internal structure is

being known to tester who is going to test

the software.

This type of testing is carried out by

testers.

Generally, this type of testing is carried

out by software developers.

Implementation Knowledge is not

required to carry out Black Box Testing.

Implementation Knowledge is required to

carry out White Box Testing.

Programming Knowledge is not required

to carry out Black Box Testing.

Programming Knowledge is required to

carry out White Box Testing.

Thank you