Ideally, you should complete each stage in the release management process in a discrete environment, separate from the other environments. Realistically, you may have to combine one or more of the environments due to hardware, time, or other resource constraints.
At a bare minimum you should separate the production environment from the other environments. Consider completing development, unit testing, and staging in a "virtual" environment. Performing development work, unit testing, and staging in a virtual environment offers great flexibility and uses considerably fewer hardware resources than required otherwise. If a virtual environment is used, allocate at least MB of memory for each virtual machine that is running on the host computer and an additional MB of memory for the host operating system.
For example, for a BizTalk Server environment that uses five virtual machines two computers running BizTalk Server, two Microsoft SQL Server cluster nodes, and one domain controller , you would plan to have 3 GB of memory installed on the host computer.
If the BizTalk Server environment requires more than 2 GB of memory, consider installing a bit version of Windows on the host computer to ensure that the maximum amount of installed memory is accessible by the host operating system. BizTalk Server is fully supported on a supported operating system that is running on any of the virtualization software listed in the Microsoft Knowledge Base Article Microsoft BizTalk Server supportability on a virtual machine.
However, BizTalk Server may not perform as expected if installed on a supported operating system that is running in a virtualization software other than the ones mentioned in the KB article. The BizTalk projects that are used for the BizTalk solution are created in the development environment. You should install the following software on the computers used in the BizTalk Server development environment:.
Typically developers should have their own development computer physical or virtual with the necessary software installed. We recommend that you purchase and use Visual Studio subscription for non-production environments. Visual Studio subscriptions are offered at a significant discount from the cost of a retail license for the same software. See Visual Studio Subscriptions. Unit testing can be completed in a virtual environment.
You should, however, conduct your performance testing in a physical environment with hardware and software that is identical to the production environment. The testing environment is used to measure performance characteristics such as maximum sustainable throughput MST and maximum sustainable tracking throughput of the BizTalk solution. It should therefore match the physical production environment as closely as possible.
You typically use the staging environment to "unit test" the actual deployment of the BizTalk solution. The software installed in the staging environment should closely match the software installed in the production environment. It may, however, be acceptable to use virtual computers in the staging environment since this environment is not to be used for measuring performance.
In such cases, the application crashes hampering the overall user experience. Testing in Production TiP if done on a daily basis eliminates the risk due to such frequent deployments on the production environment. In most of the project, testing in production is avoided considering it to be risky for the end user.
The QA team should be encouraged to integrate production testing in their daily testing cycle. An excellent way is to create a daily sanity checklist for the production testing that covers all the main functionalities of the application. Also, the modules in the application can be divided into small chunks and distributed among the QA team to test and check for the quality of the application.
The testers and QAs must ensure that the Testing in Production environment must regularly be followed to maintain the quality of the application. Outlined below are some testing guidelines that must be followed while testing in a production environment:. The ultimate goal of Testing in Production environment is to ensure that the application is stable and runs the way it is expected to in the production environment. Daily production testing gives confidence to the developers that the application runs smoothly and hassle free.
Your email address will not be published. Save my name, email, and website in this browser for the next time I comment.
0コメント