测试环境层次
来源:互联网 发布:改车软件 编辑:程序博客网 时间:2024/06/01 21:13
For smaller companies (it's not clear how big yours is), three environments (dev, stage, production) are common. Larger companies will often have a QA environment between dev and stage.
These normally break down as follows:
dev: Working code copy. Changes made by developers are deployed here so integration and features can be tested. This environment is rapidly updated and contains the most recent version of the application.
qa: (Not all companies will have this). Environment for quality assurance; this provides a less frequently changed version of the application which testers can perform checks against. This allows reporting on a common revision so developers know whether particular issues found by testers has already been corrected in the development code.
staging: This is the release candidate, and this environment is normally a mirror of the production environment. The staging area contains the "next" version of the application and is used for final stress testing and client/manager approvals before going live.
production: This is the currently released version of the application, accessible to the client/end users. This version preferably does not change except for during scheduled releases.
A stage environment should mirror the production environment as closely as possible.
It is used for verification of deployment procedures - making sure that when code is production ready it can be deployed without causing problems.
That is, code goes to staging - this is comprehensively tested and regressed to ensure that deployment went as planned (and to iron out any issues if it didn't).
The stage environment is a preprod environment that mirrors production. Often, it may have some production data so that a test group composed of actual users and QA testers can confirm that the pre-released code base/data will deploy and work properly in a prod-like environment, usually through scripted use cases and regression tests.
参考:
http://programmers.stackexchange.com/questions/117945/dev-vs-stage-environment-vs-prod-environment
http://msdn.microsoft.com/en-us/library/ms942990(v=cs.70).aspx
- 测试环境层次
- 软件测试的层次
- 层次查询测试
- 系统测试设计的层次
- 研发测试的6层次
- 测试python最大递归层次
- 环境测试
- 测试环境
- 环境测试
- 测试环境?
- 四种测试层次的比较
- 四种测试层次的比较
- 软件测试的两张藏宝图和三个层次
- java.util.logging.Logger 层次结构测试
- 软件测试层次,你到了哪层
- 软件测试的第五个层次 - 测试脚本自动生成
- 什么是测试环境?如何搭建测试环境?
- [唐胡璐]软件测试环境 - 测试环境搭建
- windows 简单窗口
- apache无法解析php文件显示源代码
- 存储过程中的declare
- 一次修改表为nologging状态的痛苦过程
- show interface | include (^Ether|^Fast|^Giga|loop-inconsistent) 牛x的命令
- 测试环境层次
- 毕业设计(一)---写在前面
- RAM和ROM简介
- fedora14下设置静态IP地址
- Drools Planner--问题,议题,博客(第1.5章节)
- java: cannot execute binary file错误
- vc 特殊字体
- springMVC 用query.ajax文件上传
- S3C2440之I/O寄存器和中断寄存器