1.

QUALITY ASSURANCE PROCESS

PURPOSE OF THE PROCESS

A detailed/brief guideline for quality control to ensure quality on every project in the organization.

The end goal is to find bugs in product and report to the development team for bug fix.

The vision is to have a running application complying to the customer expectations and organizational standards.

This process is subdivided into three sub-processes.

1.1. Preparation

# Steps Description Responsible Tool

1 Requirement analysis/testing Ensuring if QA team

requirement is
complete, clear,
correct, consistent,
and testable.

2 Writing test plan Writing and sharing QA team Ms Word

test plan document to
dev team and
Business Analyst

3 Writing test scenarios Extraction of what to QA team

test from user
requirements
Microsoft excel/
4 Writing test cases Elaboration of all QA team SpiraTeam
testing steps from
scenario

5 Setting up reporting tool Setting up the QA team SpiraTeam

environment of bug
reporting.

6 Conducting QA meeting Explaining to dev QA team

team about test
strategy, tools, bug
severity, exit criteria,
objective, principles
etc
 1.2. Execution

# Steps Description Responsible Type Tool

1 Performing unit testing Verification of piece of Developer Automation/

code and quality Manual
checking Junit, TestNG,
sonacube etc..

2 Performing integration testing Evaluation of the Developer/Q.A Manual

compliance of a system
or component with
specified functional
requirements

3 Performing smoke testing Ensuring that critical Q.A & Developer Automation/ Selenium
functionalities are Manual
working before diving
into requirement
testing.

4 Performing system testing Verification of the QA team Manual Mantis, excel.

system to ensure if it
meets user
requirement(s), QA
team conduct it on
every release.

5 Performing regression testing Ensuring that new code QA team Automation Selenium
changes should not
have bad effects on the
existing functionalities.

6 Performing UAT (User The main purpose of QA, BA Manual SpiraTeam,

Acceptance Testing)
UAT is to validate the excel.
end-to-end business
flow. It does NOT
focus on Cosmetic
errors, Spelling
mistakes or System
testing. User
Acceptance Testing is
carried out in a
separate testing
environment with
production-like data
setup. It is a kind of
black box testing where
two or more end-users
will be involved
2.3 Defect management
# Steps
1 Opening defect
2 Handling defect
3 Closing defect
4 Reporting
Description Responsible Tool
Clear description of a QA
bug alongside with a
link as well screenshot,
assigning a severity and
key person in charge.
Changing a status of a Developer
defect after putting that
part in a testing
environment.
SpiraTeam
Verification of corrected QA
part and change the
status to “closed” when
defect is not handled
status changed to
“reopen”. After twice
reopen management
take special decision.
Reporting to dedicated QA
stakeholder about
project/feature status