Apps/QA/Test Infrastructure

Test Infrastructure Requirements

The Problem

The problem we are currently facing in our testing environments is that each group has their own infrastructure. The infrastructure is built around varying concepts of dev , beta, staging environments.

The problem is those environments all have different schedules that code is pushed, and released, and it is not possible to guarantee what version of the marketplace, browser id, Apps , Sync Tests have gone through a level of integration testing.

Each group has their own infrastructure, and it's not entirely clear to each group what the benefits of moving to a shared environment are.

Current Release Schedules Are the following:

Sync Service - https://intranet.mozilla.org/QA/Server_Weekly_Trains_Staging#Schedules

1. Weekly Push
2. Wed Push to staging
3. Monday - Release to production

MarketPlace - https://mail.mozilla.com/home/wclouser@mozilla.com/AMO%20Schedule.html

1. Infrastructure Diagram [<a href="">Dev Process</a>]
2. addons.allizom is staging server, but only updated as needed
3. Release happens 2pm Thursday
4. DBA Sheeri / MPressman

BrowserID - https://wiki.mozilla.org/QA/BrowserID/TestPlan#Weekly_Test_Schedules

1. Thursdays: deployment to Production, Stage (QA), and Dev
2. Thursdays/Fridays: open testing and experimentation by Dev, QA, and community
3. Following week: Monday - Wednesday: QA testing and sign off of current deployment
4. DBA: petef

Apps - Web Services (HTML / JS / Dashboard)

1. As needed

The Purpose

Define an apps test environment that tests the apps javascript api's, as well as the .

Minimum Requriements

Hardware Requirements

apps-dev.mozilla.com myapps-dev.mozilla.com

apps-staging.mozilla.com

<p><p><p>myapps-staging.mozilla.com

</p>

</p>

</p>

Concept

[Image:Webapps_test_infrastructure.png]