SOFTWARE TESTING SERVICES

for startups

Based on availability, we offer a free 2-week trial for revenue generating/funded startups with at least 3 full time developers.

Based on availability, we offer the free 2-week trial to revenue generating (or funded) startups with at least 3 developers employed full time.

What you get in the two week trial period

an overview of your test strategy

    • mind maps • ACC model • layers model

your first automated test

    • typically an end to end scenario • Python • Selenium • Appium (Android)

a robust page object implementation for GUI automation

out of the box reporting to TestRail, Sauce Labs and BrowserStack

one hour tutorial on using and enhancing our light-weight automation framework

Your time commitment

During the two week trial period, you need to give us:

1. access to your test environment

2. a brief tour of your product

3. time with the product owner (~2 hours over Day 1-3)

4. time with a developer (~2 hours over Day 4-5)

5. time with DevOps (~2 hours over Day 6-7)

6. time with engneering head (~2 hours on Day 1,10)

What to expect in a two week trial

Here is an outline of a typical trial. We will modify it slightly to suit your needs.

Day(s) Activities Notes
1
  • Meet the team (~30-45 mins)
  • Get setup with access
  • Product tour (60-120 mins)
Product owner should prepare a brief product tour
2-3
  • Exploratory testing
  • Visualize product
  • Identify end to end workflow to automate
We typically Skype the product owner with our questions
4-5
  • Automate end to end workflow
  • Ask for mocks if necessary
We usually work with your developers when we have technology and architecture related questions.
6
  • Demo of automation
  • Automation code refactor
  • Jenkins integration
We need to work with your Systems/IT people to configure Jenkins
7
  • TestRail integration (30 day trial)
  • Sauce Labs integration (30 day trial)
  • Automation refactor and code clean up
Usually clients ask us about other testing problems - performance tests, mobile automation, better exploratory testing, unit testing, etc.
8
  • Tutorial prep
  • Enhance automation to show examples
Usually clients ask us about other testing problems - performance tests, mobile automation, better exploratory testing, unit testing, etc.
9
  • Demo to the sprint team
  • Tutorial on using/enhancing automation
  • Questions
We'd love to have open sessions with the QA team
10
  • Report writing
  • Clean up (credentials, accounts, etc.)
We like ending with a 1:1 with the head of engineering.