
How to setup a QA function from scratch for agile startup
Many people getting stressed while joining start-up and don’t know where to start. Here is my experience how I started QA for a small agile start-up.
- Build flow-chart diagram for application.
It will help for:
- dividing app into section
- making clear and cover all user scenarios
- writing test cases/checklists
I started flow-chart in Powerpoint, then switched to Sketch. In Sketch you can connect sections using cursors (and make them different color).

2. Write test cases.
We used TestRail for storing all test cases and for integration with test automation. You can integrate with JIRA to create automatic bug reports if test cases will fail.
TR also creates statistics about percentage of failed/passed, manual and automated test cases,

3. Writing user scenarios in Gherkin (optional)
Usually it’s useful when new people join the company to understand app workflow and if QA writing scripts BDD format.
If it’s only will be used by QA I think it’s not worth time.

4. Cross-compatibility testing
You can simultaneously test on different OS’s, devices and environments using cloud services such as Browserstack or Saucelabs.
Or you can run test scripts connecting with these services.

5. Test Automation
After the product became more or less stable you can start writing test framework.
First — most important functionalities, such as login, log out, account settings, switching between pages.
Most popular programing languages for automation (in the world):

Personel recommendations to get familiar with:
Learn how to use git version control (to download code from github and launch on your PC), linux commands
Web testing — How to use console, developer tools
Test Automation: Syntax of the language, Basic of programing (functions, loops, if/else statements).
