Apps/QA/Test Infrastructure: Difference between revisions

<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.  

</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.  

</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:

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

<ol><li> Weekly Push

</li><li> Wed Push to staging  

</li><li> Monday - Release to production

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

<ol><li> Infrastructure Diagram [&lt;a href="http://micropipes.com/temp/devprocess2.png"&gt;Dev Process&lt;/a&gt;]

</li><li> addons.allizom is staging server, but only updated as needed

</li><li> Release happens 2pm Thursday

</li><li> DBA Sheeri / MPressman

<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

<ol><li> As needed

<h2> The Purpose </h2>

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

<h2> Minimum Requriements </h2>

<h3> Hardware Requirements </h3>

<p>apps-dev.mozilla.com

</p><p>apps-staging.mozilla.com

<p>&lt;p&gt;myapps-staging.mozilla.com  

<h3> Concept </h3>

<p>[Image:Webapps_test_infrastructure.png]

<h2> The Purpose </h2>