QA Onboarding

PROPERTY BY: ORANGE AND CRANE INNOVATIONS, INC.

Responsibilities of a QA
✓ Analyze business requirements and approved UI/UX designs
✓ Prepare test plan and test cases
✓ Prepare test data for execution
✓ Execute manual execution or testing of web application and mobile applications.
➢ Execution of:
➢ Functional Testing
➢ Non-Functional Testing (UI, responsiveness,
➢ Environments:
➢ QA Server or QA Environment for internal testing
➢ Production Server for smoke testing
✓ Ensure all issues and bugs are appropriately identified, documented, validated, and resolved in a timely manner
✓ Support dev teams for bug investigation
✓ Prepare and document User Manuals
✓ Maintain the projects smooth and functional
 As a QA you should be…
➢ Responsible and a LEADER
➢ Initiative
➢ Hard working
➢ Deadline oriented or strong attention to details
➢ Committed
➢ Organized
➢ Can do multitasking
➢ Good communicator
➢ Explorer
Development Process
I. Requirements Gathering
Persons Involved:
1. Business Owners
2. Clients
3. Team Lead / Senior Developers
4. UI/UX

1. List of functional requirements (interactions between system and environment)

2. Quality requirements – usability, reliability, performance and maintainability
3. Constraints or pseudo requirements – implementation (tool, languages), interface (UI),
operation (admin, management), packaging and legal
4. Validate and verify requirements (complete, consistent, definite, correct)
Development Process
II. Planning Phase
Persons Involved:
1. Business Owners
2. Team Lead / Senior Developers
3. UI/UX
1. Scope – items or list to be prioritized for current sprint and for back logs:
a. Identify User stories
b. Forecast the items that can accommodate for current sprint and next sprints
c. Identify list of backlogs
d. Team capacity - (how confident the team to complete the sprint or meet the
deadlines)
e. Risk Management (this is to prevent risks from happening in the future):
The process of identifying, analyzing and then responding to any risk that arises over
the life cycle of a project to help the project remain on track and meet its goal. It should be
part of the planning process to figure out risk that might happen in the project and how to
control that risk if it in fact occurs.
3. Production deployment date:
a. Set a schedule at least 1 day.
b. Ready or prepare the servers, database, front-end and mobile apps at least 3 days before the actual
date of deployment.
4. UI/UX planning and review:
a. Research and UI design implementation
b. Approval and Revision process
c. Discussion or introducing process of approved UI design with the Team
5. Dev Planning and review:
a. Architectural design, Schema design, Logic design, process flow
b. Scrum poker:
a. This is the timeline completion of the task but make sure to consider the positive and negative side
effects that might occur before and during build.
b. Identify their timeline on each assigned tasks (how long does it take for them to finish an item)
c. Identify the issues that may encounter before and during the build code phase
6. QA Test Planning
a. Test scenarios must be based on sprint user stories and UI design
Development Process
III. Build / Code Phase
Persons Involved:
1. Team Lead / Senior Developers
2. Backend, Frontend and Mobile App Developers

1. Build / code
2. Status report
3. Code implementation to Dev, Test and Prod servers
4. Fix defects/issues:
Make sure to allocate schedule or time for fixing defects so that it may not affect the
production deployment
Development Process
IV. System or Functional testing
Persons Involved:
1. Tester/s
2. Backend, Frontend and Mobile App Developers
1. Execute test cases
2. Review test results
3. Log / report and monitor defects
4. Retest defects
5. Send and monitor status report
6. Regression testing
7. Product demo
1. Must be done at the end of the sprint
Development Process
IV. System or Functional testing

1. Prepare Release Management Document

2. Send an Email notification for Deployed items
3. Smoke testing (Prod server)
1. Must be done after the production deployment. To validate that all changes
made from the current sprint are working properly in prod. This is not a
thorough testing.
Sign-off:
2. Make sure to give approval to developers once the defects are fixed.
3. Provide recommendation only for items to be deployed in prod
4. Provide lists of working and non-working items.
5. This sign-off means that requirements and changes made for the current
sprint are tested, working properly and ready for live production.
Development Process
V. Production deployment
Persons Involved:
1. Tester/s
2. Backend, Frontend and Mobile App Developers
1. Log a production deployment plan
This document will be use as document tracker for every production deployment. This includes –
system or app version, services, database, servers, connection and functionalities included for production.
If there is/are issues or risk encountered during the prod deployment log it to the production
deployment plan
2. Set the production deployment date:
Have them set at least 1 day (for deployment) and the day after for smoke testing
Make sure that all services, database, servers, software, etc. are prepared or ready 3 days before the
actual date of deployment.
Make sure to review everything before migrating to prod
3. Log a production issue or defect report
If there is/are issues or defects encountered during smoke testing or after the prod deployment log it
to production issue or defect report
Build and Testing Environments:
Dev Server:
used by Developers for their code development and own
testing.

Test Server:
used by QA and non-QA testers, functional and UI testing.

Production Server:
Live production – accessed by clients or actual users.
Web Application Links (QA Server)
Dev Server:
used by Developers for their code development and own
testing.

Test Server:
used by QA and non-QA testers, functional and UI testing.

Production Server:
Live production – accessed by clients or actual users.
Web Application Links (Prod Server)
Dev Server:
- Used by Developers for their code development and own
testing.

Test Server:
- Used by QA and non-QA testers, functional and UI testing.

Production Server:
- Live production – accessed by clients or actual users.
 OCI Current Projects
Ciergio is a property management platform where it provides quick communication between property
management and unit owners.

Ciergio is simple wireless solution, that improves communication and coordination especially within a
closed community. With Ciergio, administrators can easily manage and access the central admin features via a
web access portal.

1. Ciergio Home
2. Ciergio Pray (MTQ Parish)
3. Ciergio Pray (UP Parish)
4. Ciergio Circle (Luneta)
5. Ahente (Neighborgoods)
 OCI Projects Platform Availability
Mobile Application
Project Name Web Application In Production
(Android and IOS)
Ciergio Home Yes Yes Yes

Ciergio Pray (MTQ Parish) Yes Yes Yes

Ciergio Pray (UP Parish) Yes Yes Yes

Ciergio Circle (Luneta) Yes Yes Yes

Web Application Links (QA / PROD
Server)

Project Name QA Server PROD Server

Ciergio Home: Ciergio Home Revamp PROD Link
Ciergio Pray - MTQ: Ciergio Pray Revamp PROD Link
Ciergio Pray - UP: Ciergio Pray Revamp Not yet available
Ciergio Circle - Luneta Ciergio Circle Revamp PROD Link
 Mobile Application Links (QA
Server)
Reminder: Android Device
Internal Chanel – App copy
that is connected to QA
Server (for testing purposes)
and downloadable and visible
for internal organization. Project Name Internal Chanel Alpha Chanel

Alpha Chanel – App copy that Ciergio Home: Internal Alpha

is connected to Prod Server Ciergio Pray - MTQ: Internal Alpha
and downloadable and visible
for internal organization (not Ciergio Pray - UP: Internal
yet available for public Ciergio Circle - Luneta Internal Alpha
download.

For further clarifications,

please coordinate Kuya Rorr
(Mobile Android Developer)
 Mobile Application Links (QA
Server)
IOS Device
Instructions: 1. Download TestFlight App in App
1. Kindly coordinate your preferred Store.
email address to invite for 2. Check you email for App download
TestFlight account to Kuya Yuan. invite.
2. Once your email address has been 3. Download the App from TestFlight
invited, you need to accept the
invitation sent to your email.
3. Inform Kuya Yuan that you have
already accepted the invite.

For further clarifications, please

coordinate Kuya Yuan (Mobile iOS
Developer)
 Account Test Data Links
Project Name Web Application and Mobile App

Ciergio Home Link here

Ciergio Pray (MTQ Parish) Link here

Ciergio Pray (UP Parish) Link here

Ciergio Circle (Luneta) Link here

 Defect Report Links
Project Name Web Application Mobile Android App Mobile IOS App

Ciergio Home Link here Link here Link here

Ciergio Pray (MTQ Parish) Link here Link here Link here

Ciergio Pray (UP Parish) Link here Link here Link here

Ciergio Circle (Luneta) Link here Link here Link here

 Figma Links (UI/UX)
Project Name Web Application Mobile App
Ciergio Home Mobile App
Ciergio Pray (MTQ Parish) Web Mobile App
Ciergio Pray (UP Parish) Ciergio Pray - UP Parish
Ciergio Circle (Luneta)

For further clarifications, please coordinate Maia (UI/UX Designer)

 Other Links
Name Link

Daily Standup OCI - Daily Scrum / Daily Stand-up - Google Drive

Mailinator Mailinator | Main Site

QA Documents QA - Google Drive

For further questions, please coordinate Yuan, Rorr and Nick (Senior Developers)