Scribd
Upload
17 views

3-Environment, Setup, Build and Deployment

Environment

Uploaded by

urvashi4301
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
17 views

3-Environment, Setup, Build and Deployment

Environment

Uploaded by

urvashi4301
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Environment, Setup, Build and Deployment

What is a Test Environment?


A testing environment is a setup of software and hardware for the testing teams to execute
test cases. In other words, it supports test execution with hardware, software and network
configured.
Test Environment Checklist
Hardware
Check whether required equipment for If this is not the case, analyse the supply
1
testing is available? time!
Check whether peripheral equipment is Such as scanners, special printers,
available? handhelds, etc.
Software / connections
An application such as excel, word, drawings,
2 Are the needed applications specified?
etc.
For the new software does the test Has the organization experience with use and
environment exist for the organization? maintenance of the software?
Environmental data
Check whether the standard test data sets With the regression test set, consider
3
are available? the Defect administration to collect test data.
Do agreements with the test data owners
Consider functional maintenance.
about the test data exist?
Maintenance tools/processes
If no, prepare a list of all possible members
Check whether a single point of contact involved in keeping the test environment
4 exists for test environment maintenance? running. It should include their contact
information as well.
For instance, acceptance criteria, maintenance
Does the agreement reached about the
requirements, etc. Also, check whether
readiness and quality of the test
other/extra quality attributes for environments
environment?
are there in agreement.
Do all members involved in the
maintenance process are known?

Besides these, there are a few more points to setting up the test environment.

• Whether to develop an internal Test Environment or to outsource?


• Whether to follow an internal company standard or follow any External (IEE, ISO,
etc.)?
• How long the test environment is required?
• Differences between the test and production systems and their impact on test validity
must be determined.
• Can you re-use an existing setup for other projects in the company?

Different Environment?
• DEV – Dev environment is the one created and maintained by Development team for
writing the code. The access for this environment is given to the development team
only. Usually, the QA team doesn’t have access to this environment. This
environment is mostly used by Dev team for their unit testing.

• QA – QA environment is the one where the testing actually takes place. This
environment is owned by the QA team. The DEV team doesn’t have access to this
environment. After design and coding completion, the code is moved to QA
environment for QA team to conduct test execution.

• UAT – User acceptance Test is an environment where the testing is conducted by the
business users. This is done after the system testing has been completed. The major
intention is to test the system from the business point of view. Access to this
environment is given only to the business users. However, on some occasions they do
seek QA assistance, in such circumstances, QA team is given temporary access to the
environment.

• PROD – The PROD environment is the actual live environment which is exposed to
the real users and none of the DEV and QA teams have read/write access to this
environment. Prod support teams are maintained to solve issues related to the
production environment.

BUILD and DEPLOYMENT


Build

Build is a Set of Executable code ready for use by end users... which has produced by
compiling the source code. We can say like. Developers take the code and run it through
compile the code and make it functional. Usually, Software programs are regularly updated
until companies decide to stop supporting the product. This is a cycle of builds and many of
which are released to End Users.

Deployment

Software deployment is the process of getting your program/Code ready for market release. A
newly created program may work fine on your computer and it needs revisions testing’s and
other things involved before deployment.

Why it is Important?
• If Testers are aware of the deployment process, they will understand the importance
of completing their tasks within the planned time-frame.
• Testers will get an idea if the issue is really a functionality bug or something caused
during deployment say a tester is assigned to test the report feature but when he tries
to log in to the website, he is seeing an error which means the environment is down,
such issues cannot be considered as functional issues but as environmental. If the
tester is aware of the deployment, he can relate the issue to be a deployment issue.
QA Checklist – Before and After Deployment
Before Deployment –
The entire test design phase takes place before the code is actually moved to the environment.
It’s the test execution that depends on the code availability in the QA environment while the
Deployment team works on getting the code deployed in QA, the QA team should ensure to
have completed below activities –
• Ensure the test cases are reviewed and approved
• Ensure the test team is available and resource planning is completed
• Ensure the test data needs are identified

After Deployment –
After deployment, the very first thing we as a QA team do is to get started with our Sanity
test. But before we start our sanity test, we should ensure following has been taken care –
• The QA team should have received notification from the deployment team about
successful deployment and ready for QA.
• The QA team should keep a track of the deployed build.
• Make sure the QA team has the list of changes successfully deployed and also of
items not deployed even if they were planned. It may happen that the deployment
team couldn’t deploy due to missing details etc.

You might also like