Docstoc

Checklist Requirements Test Environment - Goal description

Document Sample
Checklist Requirements Test Environment - Goal description Powered By Docstoc
					                                                              Author
                                                              Date
                                                              Version



Test Environment Requirements Checklist
This checklist can be used to identify the requirements of the test environment.

The tester who is setting up the test environment fills out the checklist and discusses it
with the test coordinator. Together they check whether the requirements for the test
environment support the test strategy.

The purpose of the checklist is to help build a bridge to the system management
organization. While discussing the list, the system administrator gets a picture of the
requisites and fills out the rest of the list. This requirements list is used to decide how the
environment will be set up and which hardware needs to be purchased.

Requirement                        Option
1. Type of environment              Development
                                    Test
                                    Acceptance
                                    Live
2. Which test levels does the       Module tests
environment have to support         System tests
                                    Functional acceptance tests
                                    Production acceptance tests
                                    Chain tests
                                    Pilot
                                    Performance tests
                                    Security tests
                                    Training
                                    Other ….
3. Configuration check              Complete (it is not possible to change anything in the
                                     software versions, in the configuration or in versions
                                     of supporting packages like DBMS, server software
                                     etc.)
                                    Partial (releases, patches and upgrades of supported
                                     packages are controlled, but the configuration can be
                                     changed without notice.)
                                    None (everybody can change everything, there is no
                                     control)
4. Black box or white-box           White box, check whether development tools are
testing                              needed.
                                    Black box
5. System components                Standalone
                                    Client, quantity: …
                                    Server (for example, for database, Apache, active
                                     directory, etc.), quantity:…
                                    Network components (hub, router, switch, UTP




Test Environment Requirements Checklist                                                       1/5
TestGoal® template
                                                       Author
                                                       Date
                                                       Version


                                 cables, etc.)
                                Generic platform
                                Other ….
6. Resemblance with live        Hardware same as live environment
environment                     Infrastructure (for example, network connection and
                                 redundancy) same as live environment
                                Software configuration same as live environment
                                Software not same as live environment, there is a
                                 special test build with additional hooks and checks
7. Performance                  Network performance:
                                High/Standard/N/A
                                Server performance:
                                High/Standard/N/A
                                Client performance
                                High/Standard/N/A
                                Peripheral equipment
                                High/Standard/N/A
                                (hub, router)
8. Concurrent users             Number of testers simultaneously working on the
                                 system: ….
9. Interfaces with external     Yes ….
systems                         Simulated ….
                                No
10. Connection with external    Through a network
systems                         Through the Internet
                                Through message exchange
                                Through batch (e-mail, data storage exchange)
                                N/A
11. Software security           None
                                Log in
                                Encryption
                                Authentication
                                Firewalls
                                Other …..
12. Physical security           None
                                Test environment is in a separate room only
                                 accessible to staff
                                All components and all data are in a separate room
                                 only accessible to authorized staff
13. Accessibility               The test environment is accessed from the standard
                                 workplace
                                The test environment is accessed from a separate PC,
                                 additional requirements are: ….
                                The test environment is part of the standard business
                                 network
                                The test environment is part of an standalone



Test Environment Requirements Checklist                                              2/5
TestGoal® template
                                                         Author
                                                         Date
                                                         Version


                                   development/test network
14. Protection                    Permissions to view or edit system logs
                                  Permissions to view or edit queue
                                  Permissions to view or edit database
                                  Permissions to view or change system configuration
                                  Permissions to view or change system users
                                  Permissions to use the system as a user
                                  Permissions to work as an administrator or user in
                                   interfacing systems
15. Tools                         Test data repository
                                  Bug tracking system
                                  Development tool
                                  Unit test tool
                                  SQL client or database administration tool
                                  Drivers
                                  Stubs
                                  Simulators
                                  Monitoring tools
                                  Test tool (create load, measure performance)
                                  Result analysis tool
                                  Test tool (test automation and/or result logging)
                                  Separate machines to run simulators and test tools
                                  XML editor
                                  Text editor
                                  Message editor/generator
                                  Data analysis tool
                                  Version management tool
                                  Other ...
16. License policy, additional    Only freeware (no license costs)
tools                             Only limited license costs (€ .… max.)
                                  Only after extensive tool selection, no maximum, but
                                   business case required
17. Stability and uptime          Automatic restart
                                  Yes/No
                                  Automatic deployments
                                  Yes/No
                                  Automatic processes
                                  Yes/No
                                  Automatic closing down of connections
                                  Yes/No
18. Speed of deployment cycle     Within 1 hour
                                  Within 1 day
                                  Other ...
19. Test data                     Technical test data
                                  Logical test data
                                  Training data



Test Environment Requirements Checklist                                               3/5
TestGoal® template
                                                           Author
                                                           Date
                                                           Version


                                  Live data (anonymized)
                                  Live data (not anonymized)
                                  Live data (migrated)
20. Size of the test data set     Small          size < ………..MB
                                  Medium         size < ………..GB
                                  Large          size < ………..GB
21. Sharing information           Own data, own system
                                  Same test data, but own data set to work with
                                  Same test data, all testers work with the same
                                   database
22. Test data, maintenance        Test data is defined by the tester, no fixed test data
                                  Test data has been defined and is maintained
                                   centrally. Test data repository
                                  Test data is rolled back to the starting point after each
                                   test
23. Test data, starting points    Are always implemented from the application
and configuration                 Are initially implemented from the application and
                                   are rolled back to the starting point after each test.
                                  Are entered from the database using SQL
                                  Other ….
24. System needs to work with     Works with following versions of MS Windows ….
different configurations          Works with following versions of Web browsers ….
                                  Works with following versions of DBMS ….
                                  Works with another OS….
                                  Works with other components …..
25. System availability,          The environment has been assigned to this project
sharing with other projects        only
                                  The environment is shared, but software installations
                                   are independent, switching has no impact
                                  The environment is shared, changing software
                                   components or configuration is necessary and
                                   switching has impact
26. Compatibility                 Test environment must be interchangeable with other
                                   environments (Development, test, Acceptance, Live)
                                  Test environment should be interchangeable with
                                   other environments (e.g. Acceptance 1, Acceptance 2,
                                   etc.)
27. Manual or automated test      Manual
execution                         Automated
28. Test environment is           Test team
installed by                      Development department
                                  Maintenance department
29. Additional tools are          Test team
installed by                      Development department
                                  Maintenance department




Test Environment Requirements Checklist                                                   4/5
TestGoal® template
                                                    Author
                                                    Date
                                                    Version


30. Maintenance and support    Own maintenance
                               Maintenance by development department
                               Maintenance by maintenance department
31. Knowledge and skills of    System knowledge
management team                Network knowledge
                               Database knowledge
                               SQL
                               Tool knowledge
                               Other ….




Test Environment Requirements Checklist                                 5/5
TestGoal® template

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:124
posted:6/5/2010
language:Afrikaans
pages:5