Apps/QA/Test Infrastructure: Difference between revisions
| Line 2: | Line 2: | ||
== The Problem == | == 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 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 | |||
Weekly Push | |||
Wed Push to staging | |||
Monday - Release to production | |||
MarketPlace - https://mail.mozilla.com/home/wclouser@mozilla.com/AMO%20Schedule.html | |||
Infrastructure Diagram [a href="http://micropipes.com/temp/devprocess2.png" Dev Process] | |||
addons.allizom is staging server, but only updated as needed | |||
Release happens 2pm Thursday | |||
DBA Sheeri / MPressman | |||
BrowserID - https://wiki.mozilla.org/QA/BrowserID/TestPlan#Weekly_Test_Schedules | |||
Thursdays: deployment to Production, Stage (QA), and Dev | |||
Thursdays/Fridays: open testing and experimentation by Dev, QA, and community | |||
Following week: Monday - Wednesday: QA testing and sign off of current deployment | |||
DBA: petef | |||
Apps - Web Services (HTML / JS / Dashboard) | Apps - Web Services (HTML / JS / Dashboard) | ||
As needed | |||
== The Purpose == | == The Purpose == | ||
Define an apps test environment that allows for testing javascript api's, the firefox browser, and the android Soup app. | Define an apps test environment that allows for testing javascript api's, the firefox browser, and the android Soup app. | ||
Revision as of 19:51, 9 February 2012
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
Weekly Push Wed Push to staging Monday - Release to production
MarketPlace - https://mail.mozilla.com/home/wclouser@mozilla.com/AMO%20Schedule.html
Infrastructure Diagram [a href="" Dev Process] addons.allizom is staging server, but only updated as needed Release happens 2pm Thursday DBA Sheeri / MPressman
BrowserID - https://wiki.mozilla.org/QA/BrowserID/TestPlan#Weekly_Test_Schedules
Thursdays: deployment to Production, Stage (QA), and Dev Thursdays/Fridays: open testing and experimentation by Dev, QA, and community Following week: Monday - Wednesday: QA testing and sign off of current deployment DBA: petef
Apps - Web Services (HTML / JS / Dashboard)
As needed
The Purpose
Define an apps test environment that allows for testing javascript api's, the firefox browser, and the android Soup app.
QA should have the ability to qualify a build, and know with certainty that those are the bits being shipped. Production releases should be done using the jenkins server to push the files to production.
Minimum Requriements
Initial Hardware Requirements
build.apps.mozilla.com apps-staging.apps.mozilla.com myapps-staging.apps.mozilla.com
Concept
