This document outlines different types of testing applied to business applications including: 1. Static testing involves reviewing documentation and requirements. Dynamic testing validates requirements and includes usability, system integration, and regression testing. 2. Integration testing is done by developers, testers, and QA analysts and includes unit testing tools. Completed test formats are loaded for integration and system testing. 3. Confirmation, usability, and regression testing are performed by QA analysts. Usability testing checks functionality, visual design, and browser compatibility. Regression testing validates that modifications haven't introduced defects. 4. User acceptance testing involves clients accessing applications and APIs to test functionality and provide test results via email.

2. Testing Applied To The Business

3. Review of all
documentation associated
with the applications: user
manuals, thesis.
Review of requirements:
Considerable changes in
the code.
Validate that the requirements for the creation of the
application are fully covered in the pilot application.
Static Test
Existing
Applications
New
Applications
Suggestion
MKT. Study
Report-OTTO
Future clients
Creation

4. Dynamic Test
Existing
Applications
UsabilityConfirmationSystemIntegration Regression
New Applications
User
acceptance
Significant Changes
Without considerable
changes

5. Integration Test
Unit Tests
Test Tool
I
N
T
E
G
R
A
T
I
O
N
T
E
S
T
Unit
Testing
Format
Developer
Tester
QA Analyst
Developer
To define
Unit Testing
Tools
QAAnalyst
Tools
The
completed
format
must be
loaded in
Integration
Testing
Format
The
completed
format
must be
loaded in
All is OK?
Sending of normality through
electronic mail, etc.
Sending of Integration
Testing Format (completed)
to the Developer .

6. S
Y
S
T
E
M
T
E
S
T
System Test
Unit Tests
All is OK?
Sending of normality through
electronic mail, etc.
Sending of Integration
Testing Format (completed)
to the Developer .
Test Tool
QAAnalyst
Unit
Testing
Format
Developer
Tester
QAAnalyst
Developer
To define
Unit Testing
Tools
QAAnalyst
Tools
The
completed
format
must be
loaded in
System
Testing
Format
The
completed
format
must be
loaded in

7. C
O
N
F
I
R
M
A
T
I
O
N
T
E
S
T
Developer
Changes in the
code
New application
development
QA Analyst
All is
OK?
Is
responsible
for applying
functional
tests
+
Is given continuity
to the processes of
test
Confirmation Test
Confirmation Test
(NA)
To define
+
Evidences
Evidences

8. U
S
A
B
I
L
I
T
Y
T
E
S
T
QA Analyst
style.ogangi.com
Browser
Friendly functionality that in each of the
steps to follow does not deliver the
appropriate information presented in an
orderly and clean way.
Visual
and Logic
That complies with the
guidelines established in
the Ogangi style guide.
That the application runs
properly on any browser
(last version) on which it is
tested.

9. R
E
G
R
E
S
S
I
O
N
T
E
S
T
Developer
I made
modifications
on the code.
Before the production pass
+
QA Analyst
Validate that the previously tested
program to which modifications
have been made, ensures that no
defects have been introduced and
continue to perform the correct
functions.
All is OK?
To define
+
PRODUCTION

10. Note
U
S
E
R
A
C
C
E
P
T
A
N
C
E
T
E
S
T
Sales Team/ Product Manager
Customer
Product
All is
OK?
Access to the Ogangi package:
API, OTTO.
O
Creation of
incidence in OTTOModification
Developer
If exist modifications in the code that
affect functions of the packet that
requested client, Ogangi will
communicate to the client about this,
so , the client should applies his
functions inside the application and
communicate to across a email the
results about the test.