SQA - Testing Types

Question 1

Functional Testing

Answer 1

“How” the system works?
Reliability, usability, maintainability, compatibility, response times, capacity for performance testing, etc.

Positive:aimed at showing that software handles properly situations in which user acts as expected (verification);

runs to verify that a software works, as expected when user conducts a correct actions.
Positive testing = Validation.

Ad hoc
Smoke
Acceptance 
Regression 
Boundary 
Alpha
Beta

Negative:aimed at showing that software handles properly situations in which user acts not as user is supposed to act (error detection)

Testing runs to verify that a software
handles exceptions properly (invalid actions, inputs,
settings…)

Negative testing = Handling Exceptions (falsification ; break the system)

Error handling

Question 2

Non Functional

Answer 2

“What” the system does?
Typically described in requirements, but can be undocumented;
Verify that functions of a system are working as specified.
May occur at all test levels.

Performance
Load
Stress
Security
Compatibility
System
Usability
Recovery
Installation

Question 3

Ad Hoc - Functional Positive

Answer 3

performed without planning and documentation

Question 4

Smoke - Functional Positive

Answer 4

A sanity （健全）check to see if the software functions on the most basic level. Identify simple failure.

Main features don’t work, severe bugs are not fixed, etc;

Example:
Does the program run?
Does it open a window?
Does clicking the main button do anything?

Question 5

Acceptance-Functional Positive

Answer 5

to determine if the requirements of a specification are met (main flows of the application are functional)

Question 6

Regression回歸測試-Functional Positive

Answer 6

partial retesting of a
modified program to make sure that no new
errors were introduced while making changes to
the code (developing new or fixing existing one)
should be done for each new release (build)

*What is the most frequently executed type of testing?
release/build acceptance (each & every build)
next one is regression

Question 7

Boundary condition- Functional Positive

Answer 7

using the extremes of the input domain (min,max)

Question 8

Alpha - Functional Positive

Answer 8

simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site

Question 9

Error handling -Negative

Answer 9

to determine the response of the system outside of what is defined

Question 10

Security - Non Functional

Answer 10

Is System data protected?
How the system prevents hackers intrusion?

Confidentiality: data security (SSN, salary, medical data, etc.);

Authentication: is it a trusted computer? program?

Authorization: user’s identification (id/password); access control (read/write/delete), etc

Question 11

Load - Non Functional Performance

Answer 11

(simplest) – system behavior under an
expected load.
Example: 50 users perform 100 transactions every 1 minute;
Load test will give out the response times of all the transactions and point to system “bottlenecks” (database, server, etc).

Question 12

Performance - Non Functional

Answer 12

Testing if application meets the performance criteria;

Compare two systems to find which performs better;

Measure what parts of the system causes poor performance;

Need a stable build and environment, closest to production

Question 13

Stress - Non Functional Performance

Answer 13

system behavior under an extreme load.
Example: the current load goes well above the expected
maximum (very high number of users, transactions, etc).
Will the system performs sufficiently “under stress”?

Question 14

Compatibility - Non Functional

Answer 14

conducted on the application to evaluate the application’s compatibility with the computing environment

Examples:
Hardware platform: Desktop, Laptop, Mobile
Browser:is conducted to ensures that application look, behave, and respond the same way across different browsers
Operation System
Database: Orcale, DB2, Sybase
Mobile Carrier: Verizon, Tmobile, ATT

Question 15

Recovery - Non Functional Performance

Answer 15

how well the application is able to recover fro crashes, hardware failures and other similar problems

Question 16

Usability - Non Functional

Answer 16

measuring a human-made product’s capacity to meet its intended purpose

Question 17

System - Non Functional

Answer 17

conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements

Question 18

Black box Testing

Answer 18

testing done without access to the source code

Question 19

Whit box Testing

Answer 19

testing done with access to the source code. Bugs are reported at the source code level, not behavioral.

Question 20

Gray box Testing

Answer 20

testing using structural, design, and environment information (complete or incomplete) to expand or focus black box testing and to enhance testing productivity by using appropriate methods and tools

Question 21

Manual Testing

Answer 21

• Manually testing software for defects;
• Tester plays the role of an end user;
• Test all features to ensure the correct behavior.

When to conduct the Manual Testing?

• Expensive to do automation;
• Need for human judgment;
• Ongoing need for human intervention.

Question 22

Automated Testing

Answer 22

Test Script is an instructions for particular test, that
will be carried out by an automated test tool.

Higher upfront costs- Lower costs to repeat the test

When to automate?
Regression, not expected to change;
Repetitive tests;
Structured data/data driven;
Static, complex but static;
Load, volume, capacity
Performance, reliability;

Question 23

Testing Level

Answer 23

1. Unit testing
2. Integration testing
3. System Testing
4. Acceptance testing

Question 24

Unit (smallest testable part) Testing

Answer 24

verifies that units of source code with
associated data, etc are fit for use

Unit tests are usually created/run by developers (or
white box testers) during the development process to
ensure that code meets its design and behaves as
intended.

Question 25

Integration testing

Answer 25

the phase of testing when
individual software modules are combined and
tested as a group.

Unit Testing ->Integration Testing

Integration testing:
Take few unit tested modules;
Group them (functionally) in a larger group;
Test based on the requirements;
Deliver the output for further system testing

Question 26

System Testing

Answer 26

is conducted on a complete
system to evaluate it’s compliance with the
requirements.

System testing is a black box testing;
You need to know the design or logic.