Types of Testing

Prepared by: Michelle Lagare

Property of QE-360
 Black Box Testing
● Based on requirements and functionality
● Internal system design (code) is not considered in this type of
testing
● Automation candidate? - YES

Property of QE-360
 White Box Testing
● Focuses on the knowledge of the internal logic of an
application’s code
● A.K.A. Glass Box Testing
● Tests are based on coverage of code statements, branches,
paths and conditions
● Automation candidate? - YES

Property of QE-360
 Smoke Testing
● A.K.A. Build Verification Testing
● Non-exhaustive set of tests ensuring most important functions
work but not in depth
PASS? Go ahead with further testing
FAIL? halt testing and ask for new build with the required
fixes
● Done after every build deployment
● Duration – 5 – 15 mins of testing
● Automation candidate? - YES

Property of QE-360
 Unit Testing
● Testing of individual application components or modules
● Requires detailed knowledge of internal program design
● Should be done by developers
● Duration – 5 – 15 mins of testing
● Automation candidate? - YES

Property of QE-360
 Functional Testing
● Focuses on the output if it is the same as the
requirement/acceptance criteria or not
● Done mostly during Story Testing, Story Spot Testing
● A must for first cycle of testing
● Automation candidate? - YES

Property of QE-360
 Backend Testing
● A.K.A. Data Validation Testing
● Checks if the backend (data) matches with the front-end
● Automation candidate? - YES

Property of QE-360
 Network Testing
● Testing different Network / data connections
● 2G / 3G / Wifi connectivity
● Smart / Sun / T&T - supported?
● Other Providers – supported?
● Automation candidate? – YES (for Android)

Property of QE-360
 Integration Testing
● Testing of integrated modules to verify combined functionality
after integration
● Done when 2 or more interdependent modules are done
● Especially relevant to client/server and distributed systems

Property of QE-360
 Regression Testing
● Testing the application as a whole for the modification in any
module or functionality or bug fixes
● Done usually after bug fixes to make sure fixes are working
and didn’t introduce new bugs
● Automation candidate? – a resounding YES

Property of QE-360
 System Testing
● A.K.A. Sanity Testing
● Testing to see if entire system works as per requirements
● Done when minor issues are fixed and new build is
obtained, instead of doing a complete regression
● Automatable – YES

Property of QE-360
 End-to-End Testing
● Done to test real-world scenario, such as interacting with a
database, using network communications, interacting with
other hardware or simply making sure that a record created
can be searched, edited and saved

Property of QE-360
 Compatibility Testing
● Testing how well application performs in a particular hardware
(devices) / software (browser) / OS.
● Done when product increment (target for sprint/release) is
developed for a new platform (web or mobile) or additional
supported device or browser
● Automatable – YES

Property of QE-360
 Interface / Usability Testing
● UI/UX – User Interface / User eXperience
● Testing application’s capability to be learned, understood and
used easily for the end-user
● Is it convenient for targeted users?
● Automatable – NO

Property of QE-360
 Load Testing
● Testing to check system behavior under different loads.
● There should be a specified (target) load and perform
baseline from that
● Done usually when there there server changes, migration, etc

Property of QE-360
 Performance Testing
● Used interchangeably with ‘Stress’ and ‘Load’ testing
● Testing to check whether system meets performance
requirements
● Done with monitors

Property of QE-360
 Security Testing
● Testing to check if application can be penetrated through
hacking
● Testing how well the system protects against unauthorized
internal or external access

Property of QE-360
 User Acceptance Testing
● Normally done to verify if application meets the customer’s
specified requirements
● If there are no clients to do UAT, then Business Analyst or
Product Owner does to see if potentially shippable increment
can be uploaded or released
● Done after QA has given clearance after doing Staging
Testing

Property of QE-360