Apps/QA/Test Infrastructure: Difference between revisions

(Created page with "= Test Infrastructure Requirements = == The Problem == The problem we are currently facing in our testing environments is that each group has their own infrastructure. The inf...")
 
Line 8: Line 8:
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.  


Understanding what specific release version you tested against as well as the dependency matrix is important as products become more integrated.  
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 http://micropipes.com/temp/devprocess2.png
- 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
 
[edit]
Understanding what specific release version you tested against as well as the dependency matrix is important as products become more integrated.


== The Purpose ==
== The Purpose ==
409

edits