How to build a test environment

Question 1: How to build a test environment in software testing? Listening to your question, I guess you haven't done the test.

What is the test environment like? To put it bluntly, it is an environment where test cases can be basically executed accurately and the results are of reference significance ~

The premise is that your test case is valid. Without this, the test environment cannot be repaired.

Sometimes, the test environment may be just a system. P With this software, you don't have to worry about anything. You just need to test whether it can be installed on XP system. At this time, a complete XP system is the test environment.

Sometimes, you have to test whether a website supports multiple browsers. At that time, your test environment was an operating system with multiple browsers installed.

Do you understand what I said? The so-called building a test environment (recruiters always have this requirement and will build an environment) means that you can build a test environment. Simply put ~ it is an operating system ~ complex, it is an operating system with specific software and specific settings ~

Question 2: What is a test environment? How to build a test environment? Hardware: including PC, notebook, server and various terminals. For example, when testing photoshop software, should it be tested on a PC or a notebook? Is it measured on a computer with a Core cpu, or should it be measured on a cpu in Long Xuan? The processing speed of photoshop is different in different hardware environments.

Software: This mainly refers to the operating system where the software runs. For example, testing photoshop is testing under windows xp or vista? There may be compatibility issues. The software environment also includes compatibility issues when it coexists with other kinds of software in the same system.

Generally speaking, configuring the test environment can follow the following principles:

1, true: try to simulate the real use environment of users. What needs to be mentioned here is that project software and product software need to be treated differently. Because the project software is only aimed at a certain group of users, the test environment is relatively simple. The product software is aimed at the public, so the test environment is more complicated and should be considered in many aspects.

2. Cleanliness: Try not to install software irrelevant to the tested software in the test environment. I have encountered this kind of thing, two machines, aiming at one function, one testing OK and the other testing ng. Finally, according to the investigation, it is found that the machine that tests OK is installed with VC++ development environment that customers will not install at all, and the machine that tests ng is not installed with VC, so this bug is tested: the software lacks the necessary dynamic link library support. But this kind of cleanliness is not necessary. Sometimes, when other softwares coexist, it is necessary to deliberately test the compatibility of a certain software.

Question How does windows build a test environment Steps 1: Download IIS.

1. If you are not sure whether IIS is installed on your computer and running Microsoft Windows XP operating system, you can open IE browser and enter 127.0.0. 1 in its address bar, and press enter, as shown below.

2

If you can open the above webpage normally, it means that IIS (Internet Information Service) has been installed on this computer. If you can't open the above web page, you have to install IIS yourself. Here is how to install IIS. If you already know, you can skip this part. If not, you can study together.

three

2. There are IIS installation programs on the system installation CD, but since most of my friends' computers are now GHOST systems, you can download IIS independent installation packages with search engines. Open Baidu, enter "IIS for xp", find the relevant link URL, and download the required IIS installation package, as shown below.

four

3. The downloaded "IIS for XP" installation package is generally a compressed file, which should be decompressed before use, as shown in the following figure.

five

Step 2, install IIS

1. We open the Start → Control Panel, find and double-click Add or Remove Programs to open the Add or Remove Programs window, as shown below.

six

2. Click Add/Remove Windows Components on the left side of the window, as shown below.

seven

3. Tick "Internet Information Service" and click "Next" as shown in the figure below.

eight

4. The required file dialog box pops up, click the "Browse" command button in the lower right corner of the window to open the "Search" dialog box, find the IIS FO XP installation package that we just downloaded and unzipped from the Internet, find the required file, select Open, and then click the "OK" command button to continue IIS installation. If you need any files in the installation process in the future, just find the installation package and select the file. The following figure

nine

Click the "Finish" command button to complete the installation of IIS, as shown below.

10

Step 3: Test IIS

Open IE browser, enter "127.0.0. 1" in its address bar, and then press enter. When you see the interface shown in the figure below, it proves that IIS is successfully installed, as shown in the figure below.

1 1

At this point, we have successfully installed IIS, and the installation of IIS has been explained. Next, we will explain how to test our own ASP website.

12

Step 4: Establish a website

1. We copy the source code of our ASP website to any disk partition of the computer, such as disk D, as shown in the following figure.

13

2. Open "Computer" management. Right-click my computer, select and click Manage, and we will open the computer management window. On the left side of the window, click Services and Applications → Internet Information Services→ Website, then right-click the default website and select New → Virtual Directory, as shown below.

14

3. Create a new virtual directory. Click "Virtual Directory" to open the virtual directory creation wizard dialog box, click the "Next" command button, enter the "alias" of the virtual directory, such as glxt, and then click the "Next" command button to browse to find the directory where the website source code is located. We just put the source code in: D:\bysjASP, as shown below.

15

4. Complete the wizard. After selecting the directory, click Next, and in the access permission dialog box, select it as shown in the figure below. Then click Next to open the virtual directory creation wizard dialog box, and click Finish to complete the creation of the virtual directory, as shown in the figure below.

16

Step 5: Test the website.

1. In the "Computer Management" window, under "Default Website", we find the virtual directory "glxt" that has just been successfully created, and then click this virtual directory, as shown below.

17

2. On the right side of the window, find the home page of our website: index.asp, then right-click this file, select it in the pop-up shortcut menu, and click Browse, as shown in the following figure.

18

In this way, we opened our own website, and if there are no errors in the program, the website can be opened normally; If there is an error in the program, the network ... >>

Question 4: How to build a stable and repeatable test environment innodb _ data _ home _ dir =/longxibendi/MySQL/MySQL/var/

# innodb _ data _ file _ path = ibdata1:1g: automatic extension.

innodb _ data _ file _ path = IB data 1:500m； Ibdata2: 22 10m: Automatically extend # tablespace

Innodb _ file _ io _ threads = number of io threads.

Question: What is the android test environment? Before the android official website was built, the ADT version of Eclipse was released. It is recommended to use the IDE (upload attachment) provided by official website, that is, ADT CDT SDK Eclipse has been officially integrated and can be used without any configuration.

Question 6: The interview asked how to build a test environment in software testing. Building a test environment is actually a deployment environment, such as window+mysql+tomcat deployment.

Question 7: How to build an environment for software testing depends on the actual working environment and the running environment of the software. Generally speaking, it is like this:

1, operating system: win or Linux?

2. Software architecture: B/S or C/S

3. database type: orcale or mssql, db2deng.

. . . .

Question 8: How to build an environment for front-end development, debugging and testing? The purpose of building a series is to take the front-end team as a whole and how to effectively develop the team together. The first part is the development environment.

1. Code version management

SVN is essential, and the version number is planned according to the three-digit version of the project, and the four-digit version is developed and deployed. For example, I want to do project A, the version number is 1.0.0, and the code version I tested for the first time is 1.0.0. 1. Each four-digit version is distinguished by a label. QA deploys test code according to this label, and OP deploys online code.

If multiple projects are developed at the same time, branch. All these require a project management platform to manage versions.

2. Development environment

I assume that the category of the front-end team is V and C in HTML CSS JS MVC. The best environment is a development environment for everyone, and the code synchronizes other people's code through SVN. But the paths of the files are all the same.

take for example

Img.xx/css of css

Img.xx/js of js

Flash Img.xx/swf

Background environment, assuming that each back-end development also has an independent environment, if you are debugging code with someone, let him point the configuration to your V C directory for debugging.

The debugging problem of QA environment, your environment is consistent with the code deployment of QA environment, and you can switch static files, such as css js flash, through host. After all, most front-end problems are front-end code problems, and V and C problems are all debugged in their own environment, and static resources are switched to QA hosts.

Data problem. Finally, the big data platform provides an interface for data addition and modification with a general database. This is an ideal state. Of course, this platform will be very troublesome. If it is not feasible, the data will be manipulated through the background data operation interface.

3. Compile environment

Damn front-end code naked, there will be many problems, most of which are performance problems, and some are cache problems.

Therefore, it is necessary to provide a compilation environment. The compilation process is safe before testing, because it will pass the quality check of QA. If it should be troublesome in the OP link, no one will test the bugs of the compiled code.

Assemble general solutions

1, batch operation, such as version number.

2. Code merging and compression

3. Code optimization or function replacement, such as resource packaging.

The development I have encountered is not optimistic. So if you have time, take it yourself and see how complicated it is.

Generally, there is a general development environment, just one machine and one host, no matter where the main branch is placed, it is chaotic. There is also front-end versionless management software, and human flesh maintains multiple concurrent versions.

Or there is version management, and the development environment is still one person without a host. The introduction of static resources is managed by template conf. This kind of code is not conducive to resource path management, especially pictures. Adding png translucency requires a complete path, and the best way to merge multiple css is the root path.

All kinds of tragedies, this article ends here. The second part is the development mode and modularization.