This document outlines the roles, processes, and issues related to quality assurance testing. It describes four roles: UI verification, scripts validation, services verification using SOAP UI, and DB validation. Five processes are defined for scripts verification, services verification, UI verification, RO API testing, and DB validation. Each process includes steps for requirement analysis, clarification, development, testing, bug fixing, and verification. Potential issues are also monitored.

1. Once upon a time
QA Team:
Tetiana Gorbachova
Tetiana Terentieva
Alexsander Lyvin
Marina Kishkan

2. Application structure

3. Roles
 UI Verification

Scripts Validation

Services Verification (by using SOAP UI)

DB Validation

4. Processes
1) Scripts verification:









requirement analysis
details clarification
preview script
searching potential issues
running script
sending email with issues
verification fixes
merge to master branch
deploy2db

5. Processes
2) Services verification:









requirement analysis
details clarification
development
deploy server
create test in SOAP UI
run test
check public method in JMX
bug fixing(if it needed)
final verification(if it needed)

6. Processes
3) UI verification:







requirement analysis
details clarification
development
deploy client and server changes
verification
bug fixing(if it needed)
final verification(if it needed)

7. Processes
4) RO API:







requirement analysis
details clarification
development
preparation script with test data
test creation
bug fixing
run test on TeamCity

8. Processes
5) DB Validation:
 test creation by using SQL query
 tests running
 inform customer about problem in
database
 disable failed tests
 integrate to TeamCity
 trigger after deploy server
 if we have a problem we write email
and disable test

10. Issues





