Overview
A controlled testing environment is a simulated production environment to observe the code and its behavior. This environment, in which QA will conduct the testing lifecycle, will be created and maintained independently of the development environment.
This environment must be isolated and independent from the corporate network in order to conduct controlled testing. All stress testing, for instance, needs to be limited to the testing servers to avoid stressing the corporate network and to ensure a true test of the desired servers.
There are numerous benefits of having a separate testing environment. For instance, development of future components may continue while existing builds are tested independently.
Requirements
A controlled testing environment must include one box with access to the servers as well as to the corporate network. This box will contain the source code (Microsoft Source Safe, or SS). The configuration management team needs full access to this SS box in order to move code from the development environment to the testing environment. All code in the servers will be maintained in the SS box and labeled accordingly.
The servers must also have dial-up access in order to conduct download testing, as the majority of users are not using DSL or other fast Internet connections. Though there are many tools that estimate this time, such estimates cannot replace tests of live behavior.
Numerous test machines are an important part of the controlled test environment. The QA team will conduct stress tests and OS and browser compatibility tests using these test machines.
Estimated Need for Equipment
| Hardware | Quantity | Basic Software |
| Hub | 1 | N/A |
| Server | 2 | NT, IIS, … |
| Server | 1 | Unix, Apache |
| Server | 1 | Solaris, ATG Dynamo |
| Server | 1 | Solaris, Oracle |
| Server | 1 | NT, SQL |
| Stress PC (max RAM) | 1 | Windows, stress test software, browsers |
| Test machine | 2 | Windows, testing software, browsers |
| Test machine | 1 | Mac OS, testing software, browsers |
| Removable hard drives | 10 | Different OS/browsers/software |
| Source control PC | 1 | Windows, Microsoft Source Safe |
| Monitor/keyboard/mouse | 6 | N/A |
| Omni View | 1 | N/A |
RELATED POST
SOFTWARE QUALITY ASSURANCE AND CONTROL
SOFTWARE QUALITY AND COST ASPECT
STABLE PROCESS OF SOFTWARE TESTING
STABLE PROCESS OF SOFTWARE TESTING PART TWO
DEFECTS IN SOFTWARE TESTING
REDUCTION OF DEFECTS IN SOFTWARE TESTING
SOFTWARE TESTING AND EFFECTING FACTORS
SCOPE OF SOFTWARE TESTING
TESTING LIFE CYCLE PART ONE
TESTING LIFE CYCLE PART TWO
TESTING LIFE CYCLE PART THREE
SOFTWARE TESTING AND CONSTRAINTS WITH IN IT
TESTING CONSTRAINTS PART TWO
LIFE CYCLE TESTING
TEST METRICS
Independent Software Testing
Test Process
Testing verification and validation
Functional and structural testing
Static and dynamic testing
V model testing
Eleven steps of V model testing
Structural testing
Execution testing technique
Recovery Testing technique
Operation testing technique
Compliance software testing technique
Security testing technique
Here i am adding the further topics list on software testing subject and the topics may be scattered and you can find under different groups.
MAJOR SYSTEM FAILURES IN THE HISTORY
WHAT IS A SOFTWARE BUG ?
ROLE OF A TESTER
SOFTWARE TESTING INTRODUCTION PART ONE
TESTING INTRODUCTION PART TWO
TESTING INTRODUCTION PART THREE
TESTING INTRODUCTIONS PART FOUR
SOFTWARE TESTING FUNDAMENTALS
SOFTWARE TESTING FUNDAMENTALS PART TWO
SOFTWARE TESTING FUNDAMENTALS PART THREE
No comments:
Post a Comment