How to set up a test environment

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software Testing and Quality Assurance Why do performance testers write new scripts so often? How to create performance testing workload models Fixing Web application performance troubleshooting problems Expert advises on implementation of Selenium IDE for effective software testing When should regression testing occur in an automated test plan? Achieving peak performance in integration testing Getting answers about OpenSTA script problems Defining core software regression tests Breaking in functionality on UI application pages Where to find good methodology guides for software testing Software testing and quality assurance (QA) fundamentals How to deal with iteration issues in Agile Five steps to fostering better software tester and QA results Software Testing: New software testing technologies bring new challenges Testing strategies for complex environments Astronaut's STPCon advice: Teamwork delivers "The Right Stuff" How to make your software tamperproof Software consortium seeks standard quality metrics Demo: Using WebGoat, a free software testing tool Seven steps for a quality change and configuration management program Winning responses to "Why is QA always the bottleneck?" Advice from Scott Barber Performance testing SOA Acceptance testing for websites GUI automated testing projects Prioritizing software testing on little time Software testing processes and development methodologies Smoke and sanity testing Automating regression test cases Test plan and test strategy User acceptance testing that satisfies users and requirements Understanding performance, load and stress testing

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary build  (SearchSoftwareQuality.com) code review  (SearchSoftwareQuality.com) conformance testing  (SearchSoftwareQuality.com) error handling  (SearchSoftwareQuality.com) garbage in, garbage out  (SearchSoftwareQuality.com) load testing  (SearchSoftwareQuality.com) NUnit  (SearchSoftwareQuality.com) quality assurance  (SearchSoftwareQuality.com) stress testing  (SearchSoftwareQuality.com) white box  (SearchSoftwareQuality.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

For the most part, I don't set up test environments anymore and I recommend against test teams installing and configuring systems under test -- unless the end user is expected to install and configure the system on their local machine.

The key to test environments is that they should be as similar as possible to production environments (in most cases). It makes no sense to me for someone to expect the test team to be able to install and configure an application on machines that don't match production (or the development environment for that matter) when the test team wasn't even involved in figuring out how to install and configure the system the first time. Whoever is installing and configuring the development and production environments should be installing and configuring the test environment.

If you are asking about setting up a test lab to test application compatibility across various platforms, browsers, etc., I've become a huge fan of virtual environments.

If you are asking about testing support environments (defect tracking systems, automation tools, requirements management systems, test management systems and so forth), that is entirely dependent on your corporate policies, project goals and the tools your team uses.

Software testing resources: Test environment doesn't match production environment Performance testing in the production environment How to define a test strategy

I can think of no significant difference for the Web versus for client-side applications, with the exception that client-side applications start with a CD/DVD and Web-based applications start with a download. The fact is that if stuff gets installed, you want to make sure it gets installed properly on all supported systems/configurations. Typically, that's not possible given the time constraints. In those situations I use sampling methods like all-pairs or orthogonal arrays to help me reduce the total sample size, while managing degree and type of coverage.