Apps/QA/Test Infrastructure: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
<h1> Test Infrastructure Requirements </h1> | |||
<h1> Test Infrastructure Requirements </h1> | |||
<h2> The Problem </h2> | |||
<p>The problem we are currently facing in our testing environments is that each group has their own infrastructure. | |||
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. | ||
</p><p>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. | |||
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. | </p><p>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. | ||
</p><p>Current Release Schedules Are the following: | |||
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. | </p><p>Sync Service - https://intranet.mozilla.org/QA/Server_Weekly_Trains_Staging#Schedules | ||
</p> | |||
Current Release Schedules Are the following: | <ol><li> Weekly Push | ||
</li><li> Wed Push to staging | |||
Sync Service - https://intranet.mozilla.org/QA/Server_Weekly_Trains_Staging#Schedules | </li><li> Monday - Release to production | ||
</li></ol> | |||
<p>MarketPlace - https://mail.mozilla.com/home/wclouser@mozilla.com/AMO%20Schedule.html | |||
</p> | |||
<ol><li> Infrastructure Diagram [<a href="http://micropipes.com/temp/devprocess2.png">Dev Process</a>] | |||
MarketPlace - https://mail.mozilla.com/home/wclouser@mozilla.com/AMO%20Schedule.html | </li><li> addons.allizom is staging server, but only updated as needed | ||
</li><li> Release happens 2pm Thursday | |||
</li><li> DBA Sheeri / MPressman | |||
</li></ol> | |||
<p>BrowserID - https://wiki.mozilla.org/QA/BrowserID/TestPlan#Weekly_Test_Schedules | |||
</p> | |||
BrowserID - https://wiki.mozilla.org/QA/BrowserID/TestPlan#Weekly_Test_Schedules | <ol><li> Thursdays: deployment to Production, Stage (QA), and Dev | ||
</li><li> Thursdays/Fridays: open testing and experimentation by Dev, QA, and community | |||
</li><li> Following week: Monday - Wednesday: QA testing and sign off of current deployment | |||
</li><li> DBA: petef | |||
</li></ol> | |||
<p><br /> | |||
Apps - Web Services (HTML / JS / Dashboard) | Apps - Web Services (HTML / JS / Dashboard) | ||
</p> | |||
<ol><li> As needed | |||
</li></ol> | |||
<p><br /> | |||
</p> | |||
Define an apps test environment that tests the apps javascript api's, as well as the . | <h2> The Purpose </h2> | ||
<p>Define an apps test environment that tests the apps javascript api's, as well as the . | |||
</p> | |||
<h2> Minimum Requriements </h2> | |||
<h3> Hardware Requirements </h3> | |||
<p>apps-dev.mozilla.com | |||
apps-dev.mozilla.com | |||
myapps-dev.mozilla.com | myapps-dev.mozilla.com | ||
</p><p>apps-staging.mozilla.com | |||
apps-staging.mozilla.com | <p><p>myapps-staging.mozilla.com | ||
myapps-staging.mozilla.com | </p> | ||
</p> | |||
<p></p> | |||
[Image:Webapps_test_infrastructure.png] | </p> | ||
<h3> Concept </h3> | |||
<p>[Image:Webapps_test_infrastructure.png] | |||
</p> | |||
<h2> The Purpose </h2> | |||
<p><br /> | |||
</p> | |||
Revision as of 00:49, 9 February 2012
Test Infrastructure Requirements
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</a>]
- 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 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>myapps-staging.mozilla.com
</p>
Concept
[Image:Webapps_test_infrastructure.png]
The Purpose