Scribd
Upload
13 views

Types of Testing

Uploaded by

thinh.bp00245
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
13 views

Types of Testing

Uploaded by

thinh.bp00245
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Software Testing

Types of Testing
• ISTQB / ISEB Foundation Exam Practice
• https://www.guru99.com/software-testing.html
Contents

Unit Testing
Integration Testing
System Testing
Regression Testing
Unit Testing

 individual units of a software are tested


- a line of code, a method, or a class
 to validate that each unit performs as expected
 done by the developers who writes the code.
UT Example (1)

a=? b=?
UT Example (2)
1.
2.
3.
4.
5.

Hãy liệt kê các trường hợp test?


UT Example (3)
Integration Testing

 what the set can perform that is not possible


individually
 more than one (tested) component
 communication between components
 done by designers, analysts, or
independent testers
Big-Bang Integration

 All the components or modules are integrated


together at once and then tested as a unit
 If all of the components in the unit are not
completed, the integration process will not
execute.
Top-Down Integration
 Baselines:
- baseline 0: component a
a
- baseline 1: a + b
- baseline 2: a + b + c b c
- baseline 3: a + b + c + d
- etc. d e f g
 Need to call to lower
level components not h i j k l m
yet integrated
 Stubs: simulate missing n o
components
Bottom-up Integration

 Baselines: a
- baseline 0: component n
- baseline 1: n + i b c
- baseline 2: n + i + o
- baseline 3: n + i + o + d d e f g
- etc.
 Needs drivers to call h i j k l m
the baseline configuration
 Also needs stubs n o
for some baselines
Stubs and Drivers

 Stubs and Drivers: substitutes for the missing models.


 Stub: Is called by the Module under Test.
 Driver: Calls the Module to be tested.
System testing
 functional
 non-functional
 done by independent test group
Non-functional system testing

 performance: speed, response time,


 security
 stability
 reliability
 scalability
 ...
Performance Test Cases

1. Verify response time is not more than 4 secs when 1000


users access the website simultaneously.
2. Verify response time of the Application Under Load is
within an acceptable range when the network
connectivity is slow
3. Check the maximum number of users that the application
can handle before it crashes.
4. Check database execution time when 500 records are
read/written simultaneously.
5. Check CPU and memory usage of the application and
the database server under peak load conditions
Software Requirements Specification
User Acceptance Testing

 Final stage of validation


 Acceptance testing conducted to enable the
customer to determine whether or not to accept
the system
 User Acceptance Testing is performed by
- the end user
- or the client
User Acceptance Testing
Acceptance testing
distributed over
this line

80% of function
by 20% of code
20% of function
by 80% of code

System testing
distributed over
this line
Alpha and Beta Testing

 Alpha/Beta Testing is a type of acceptance


testing
Alpha and Beta Testing: differences

 Alpha Testing is performed  Beta Testing is performed


by the Testers within the by the end users (real
organization users, real environment)
 Alpha Testing is performed  Beta Testing is performed
at Developer’s site at Client’s location.
 The main focus of alpha  Beta Testing is the final
testing is to simulate real test before shipping a
users product to the customers
Bài tập thực hành

1. Cho ví dụ về Stubs và Drivers trong kiểm thử


phần mềm
2. Mô tả Alpha tests và Beta tests mà bạn đã từng
trãi nghiệm
3. Hiện thực hàm IsValidDate theo sơ đồ giải thuật
slides 6 bằng ngôn ngữ C/C++/C#/Java. Liệt kê
các trường hợp để kiểm thử hàm này sao cho
tất cả các dòng code đều được thực thi ít nhất 1
lần

You might also like