Skip to content
Onboarding Check list
Onboarding Check list
Welcome to Rizzle - Quality Assurance Engineering Team.
QA Onboarding Checklist
Check list
Notes
1
HR Onboarding
Complete all the HR formalities
2
Create Coda account
Create an account in , using you official EmailID as only Email from (thesilverlabs.com) domain will have access to all the Coda in the organization
4
Test Rail Access
Get Access for Testrail from
@Jayaram Ghanta
5
Github Access
@Jayaram Ghanta
6
Apple ID
@Jayaram Ghanta
7
Internal TestTrack
Get access to test Production builds, before releasing to user , InternalTest Track Access.
8
Test-flight build Access
Once creating AppleId share the emailId with get access to TestFlight build.
@Jayaram Ghanta
9
Laptop Assigned
Check with regarding you official Laptop assignment
@Jayaram Ghanta
10
Devices Assigned
Check with which team you will be working on get relevant official device.
@Jayaram Ghanta
12
Get task tracker created
Check with / to create your daily task tracker.
@Kishan G
@Deepak Thatiparthi
15
Display Picture
Set your slack , Coda , Git Hub and google account Display picture.
There are no rows in this table
Slack Channels Introduction
Usage of Slack Channels
Channel Name
Used for
Link
1
#qa-internal-group
Internal team communication.
Queries
Requesting help from team members on a task
Absence updates for small duration - (30 minutes or less)
2
#leaves_notification
Posting leave updates.
Posting absence updates
3
#design-discussions
To raise any valid design query
To suggest any valid design change
(Query only after doing required research from your end)
4
#design-transfer
Designs are transferred from design to devs and QA here.
Review design post queries in respective threads
There are no rows in this table
Accounts set-up
Accounts set-up
Email
Purpose
usage
Set-up
1
@thesilverlabs.com mail
Permanent account on Rizzle
To create regular videos and browse feed.
To test and observe real user scenarios
Login with office email.
Add a good profile picture, social accounts, Bio
2
test account 1
Testing intermediate builds
Create new channel for each release.
Add all required data to test
Create a random Gmail account.
Check all positive and negative scenarios
3
US/test account 2
to test US user flows
Use VPN while logging in with this account.
Check all US user flows and behavior using this account
Create a random Gmail account.
Login with this mail in Rizzle and note down user name.
Get this user ID’s region updated from admin panel to US (+1)
There are no rows in this table
Most Used URL
Important credentials
Login details
Name
Link
UserName
Password
3
Admin Panel - Prod
qa@thesilverlabs.com
— Get this from lead when required —
There are no rows in this table
Jira:
Epic --> A big user story that needs to be broken down. Epics group together bugs, stories, and tasks to show the progress of a larger initiative. In agile development, epics usually represent a significant deliverable, such as a new feature or experience in the software your team develops.
Bug --> A bug is a problem which impairs or prevents the functions of a product.
Story --> A user story is the smallest unit of work that needs to be done.
Task --> A task represents work that needs to be done.
Subtask --> A subtask is a piece of work that is required to complete a task. Subtasks issues can be used to break down any of your standard issues in Jira (bugs, stories or tasks).
New feature --> Requesting new capability or software feature.
Improvement -->Requesting an improvement in the existing software feature.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.