The system administrator standing top ten open source tools

It is said that the online flooded with more than 50,000 kinds of systems management tools - and the open source version has all the tools you need. , Sourceforge, currently lists more than 405,000 items, with over 25,000 system administrators tools - more than 21,000 of the Linux system under Windows for nearly 15,000. We elected you often need some tools can make your job easier.

1. Wireshark

Wireshark before the year 2006 called Ethereal, it is one of the most powerful network tools. The software to capture and analyze the Ethernet, IEEE 802.11, PPP, raw USB and a local connection of the data packets, are particularly useful for network troubleshooting. You can filter by displaying custom display, create plug-ins to support the new agreement, the captured file can be edited or converted via command line input.

Supported operating systems: BSD, Linux, Mac OS X, Windows, UNIX

License: GPLv2

2. Virtuawin

VirtuaWin is a Windows virtual desktop manager that allows users to display up to 20 virtual desktops. The software runs in the background, using the shortcut on the virtual desktop access. The most important is that the program as well as a mobile version, U disk lets you carry your desktop. VirtuaWin support dual monitors, and can be customized icon in the system tray.

Supported operating systems: Windows 95 or above

License: GPL

3. PhpMyAdmin

phpMyAdmin can use the Web browser interface manage MySQL database. The software uses a PHP developer, you can use the global database or use the custom the subset search queries, custom query by Query-by-example (QBE) to create. phpMyAdmin can create and delete database; create, delete and change table; delete, edit and add domain; execute SQL statements. Data import formats including CSV and SQL, data can be exported to CSV, SQL, XML, PDF, OpenDoc, and DOC, Excel and LATEX format. There is also a database layout save a PDF file functionality.

Supported operating systems: run cross-platform, browser.

License: GPLv2

4. Pandora FMS

Pandora FMS (Flexible Monitoring System) is a small and large systems environment (a server node), the availability and performance monitoring system. For the local system, the software agent to monitor the Linux, Solaris, FreeBSD and MAC OS X, Windows and AIX platforms, the numerical parameters, Boolean state or string. Users can use to create a proxy Shellscript, WSH, Perl or C. Remote network monitoring via SNMP v3, TCP check and remote WMI detection. The data report based Pandora own SQL background, and may be displayed on the configuration screen.

Supported operating systems: Linux

License: GPLv2

5. Process Hacker

Process Hacker is a comprehensive process viewer under Windows, the function is not only the end of the process, as well as the memory view and edit. This tool is particularly useful in that it can bypass the security software and systems for defense, some to force visualization function, for example, a thread waiting for events, the ability to restart the process to create the process dump to see if the process heap The injected DLL memory dump to a file, edit service properties.

Supported operating systems: Windows 32-bit, 64-bit

License: GPLv2, GPLv3

6. Notepad + +

Notepad + + is a convenient source code editor, you can replace Notepad that comes with Windows. Unlike the basic Windows tools, the software has a WYSIWYG printing, bookmarks, support tab stops, macro, start switch, auto-completion, syntax highlighting, zoom and multi-document support and other functions. The program has a long list of features, all the coding tools are displayed in the toolbar, it maintains the look and feel of the editor of a unique kind of lightweight most Windows software.

Supported operating systems: Windows 95 or above

License: GPL

7. Swiss File Knife

SFK including 96 function in a command-line functions. The tools include Task Category file system commands (directory and the directory tree), file conversion (for example, the hexadecimal data into binary), text processing, text / file search and compare (as in the binary file lookup field ), the network, the script (such as running HTTP and FTP servers), software development (including the conversion of binary data to the source code).

Supported operating systems: Windows XP or above, Linux (Ubuntu, DSL), Mac OS X

License: BSD

8. LDAP Admin

One of the best directory management tools LDAP server is used to browse, query, modify, create and delete objects recently added Unicode support, an enhanced picture viewer, content highlighting, and AD support. As a free alternative to expensive procedures such LDAP Admin Tool or LDAP Administrator, the feature set is not very extensive, but you can still run complex tasks, such as copy a directory in the remote server, modify the operation of the data set, using the password management Manage the Posix group and account.

Supported operating systems: Windows

License: GPLv2

9. RackTables

If the spreadsheet is no longer the ideal solution for tracking data center equipment, then RackTables the asset management program may be more beneficial solution. Use the software, you include all of the components in the data center, including hardware assets, network addresses, rack space and network configuration. Still at an early stage of development, lack of some features, such as the limited number of switches support, but covers IPv4/IPv6 address management software, 802.1Q VLAN, CWDM and DWDM channel grid, as well as through CDP and LLDP neighbor discovery.

Supported operating systems: Windows, Mac OS X, Linux

License: GPLv2

10. Areca Backup

Areca Backup is a simple, but very effective backup solution that allows you to select a group of files or directories to be backed up and configure a custom backup behavior. The backup program supports ZIP ZIP64 format AES128/256 encryption, local or network drive, backup storage, incremental backups of file filters, file merging, data recovery, backup report. Users can create a script to run when the backup is complete. The software has a graphical interface and command line.

Supported operating systems: Windows 32-bit, Mac OS X, Linux

License: GPL

Traditional software testing problems and solutions

Traditional software testing process: small amount of unit testing in the software development process. Then end stage throughout the software development, focus on a large number of tests, including the function and performance of the integration testing and system testing. With the increasing complexity of software development, software testing process inevitably brings us the following question:

One problem: difficult to control the progress of the project, project management more difficult.

A large number of software errors often only to the system test phase of the project late been discovered to solve the problem of the time it takes to be difficult to predict, and often lead to the progress of the project can not control, a lack of understanding of the quality of projects throughout the software development process, project management and control, increase the difficulty of project management.

Second problem: weak project risk project risk control in the late project development can really reduced. After system testing before really determine whether the design truly meet the needs of the system functionality, performance and reliability.

Question three: software project development costs exceed the budget. The later errors found in the entire software development cycle, the higher the cost of the unit bug fixes, error delay to solve the entire cost of the project is bound to lead to a sharp increase.

The successful experience of the IBM Rational Software automated testing to solve the problem of the traditional test.

The core of the successful experience of the three best: early testing, continuous testing, automated testing, and on this basis to provide a complete software testing process and a set of software automation tools, so we eventually be able to do: a test team, based on a complete set of software testing process, the use of a complete set of automated software testing tools, and complete a full range of software quality verification.

Successful experience: as soon as possible to test

The so-called as soon as possible to test an idea through a variety of software engineering in the entire software development cycle as early as possible to complete a variety of software testing tasks. IBM Rational software engineering techniques early test for us in the following three aspects:

First of all, the entire testing life cycle of the software is essentially flush with the software development life cycle process. When demand analysis basic clear we should be based on a needs analysis of the results, and the entire project plan for software test plans; along with the analysis and design process should be completed test case design; When the software's first release came out, the test to immediately based on its implementation of test scripts and execute test cases based on the purpose of the test in the test plan, the assessment report of the test results. In this way, we can index real-time monitoring of various test project quality status, to improve the control and management of the entire project.

Project planning, demand management --- test plan

Test plans, analysis of the design --- test design

Test design --- test implementation

Test --- test results assessment

Secondly, through the iteration is software development to the original of the entire software development life cycle is divided into multiple iteration cycles, and in each iteration cycle test system testing time in advance, so largely, largely reduce project risk and project development costs.

Finally, IBM Rational early test of successful experience is also reflected in the expanded developer testing and system testing traditional testing phase from unit testing, integration testing, system testing, acceptance testing division of the entire software testing phases divided into two stage. Software testing duty bound to extend to the the developers work of the entire development process. Through advance testing time to improve the quality of software testing as soon as possible, to reduce the cost of software testing.

Successful experience: continuous testing

The test successful experience continuous test is derived from iterative software development model. Iterative method, we target the entire software development is divided into a series of small targets easier to implement and achieve these objectives are defined clear stage evaluation criteria. Iterations is engaged in a series of development activities in order to complete certain milestones must be based on the current state of the project and the milestones to be achieved before the start of each iteration develop iterative scheme and each iteration of the process including requirements development, design, coding, integration, testing a series of activities will be incremental integration of new system functions. Each iteration to generate a running system. System can run tests to assess the iterations have not reached the predetermined iteration goals, and as a basis to develop the next iteration. Thus, in each iteration of the iterative software development cycle, we will carry out activities of software testing, and completion of the entire software testing through each iteration cycle constantly incremental testing and regression testing.

Successful experience: automated testing

Should test as soon as possible in the whole process of software testing, continuous testing, can be said to improve the testing process is automated testing tools is to ensure that. The successful experience of the IBM Rational automated testing refers to the use of software testing tools provide complete support of the software testing process and various test automation implementation.

Addition to the test in order to make the software testing team, IBM Rational provides test successful experience, also provides us with a complete set of software testing processes and automated testing tools, software testing team can take time to complete the test task.

For the agility of the top five misconceptions

Myth: agile people demanding

Many people try to implement agile: agile requirements too high, we do not have such conditions, we do not have the people, so we can not agile. However, agile requirements really that high?

Software in the final analysis, is also a creative activity, developed the skill level and personal capacity plays a decisive role in the quality of the software or just a variety of processes and methods to help developers, testers and other roles to better cooperation, resulting in higher productivity. Regardless of the method, the developer level is always a major factor.

From another point of view: the process and methods of what help developers how big favor? Is about the same for the lower level of technology developers, agile methods and traditional methods to help him, so to see a less than significant effect, even when there are opposite effect; With the improvement of the technical level of the developer, agile methods be able to unlock the shackles, encourage innovation, and the effect will be more significant.

Agile requirements, and will help you develop the necessary capacity, of course, if you are in really agile environment.

Myth: agile design document, nor do

This misunderstanding from the XP start did not stop, XP encourage non to be necessary and of great significance not write the document. There mentioned "necessary and of great significance" is a criterion, not all documents are not written. For example, the user manual is not necessary and significant "? This depends on the requirements of the customer, if the customer does not need, then they do not need to write, if the customer needs, you must write; Another example, the architecture design document or else write? Complicated to write complex do not write. Architecture design usually only need a relatively simple document, for some projects, a simple UML diagrams is enough. Therefore, write, do not write, how to write, how much significance should be the basis of this document in the end, the decision of the proportion of outputs and inputs, as well as the specific circumstances of the project. Actual operation allows all project team personnel to vote, to be avoided by an individual (such as lead).

As for the design, XP pursuing sustainable design, and not without design. This is actually the design work allocated to day-to-day work, constant design improvements (reconstruction), the design has been kept flexible and reliable. As for the pre-design before coding, Kent Beck et al really practiced without any pre-designed development, but for those of us non-guru "level developers, the necessary pre-designed or need, just not too much, not too fine, there must be the will to overturn ready.

Misunderstanding number three: good agility, and other methods is not good

Some people mention dexterity shouted agile practice anything mentioned CMMI methods such shouted bad, no matter what as long as the stained side on where not good, seems agile and other methods is completely opposite. Newton said that, I am standing on the shoulders of giants. Agility also draw other methodological advantages, but also standing on the shoulders of giants, agile remains many historic practices and principles just different manifestations Bale.

From another perspective, the present do not have a good ring, good or bad depends on whether it is suitable to solve your problem. Each method has the most good at solving problems and the best play environment, demand is stable, and the era of software complexity is relatively high, the waterfall model can also work well, while Min Jieqia good applies to the risk of changes quickly The project - which is precisely the many projects in common.

Therefore choose a method or process, and not according to whether it is agile, but should be based on whether it is suitable. Learned a thing suitability, or want to try to understand things are not proven untrustworthy.

Misunderstanding: Agile XP, Scrum

XP and Scrum are just two of the many agile methods, as well as many other agile methods. The different dragon have nine sons, agile methods look is a big difference, but the reason they are called agile methods, because their underlying philosophy and principles are the same, this principle is "Agile Manifesto". Learning agile not only to study and practice, but also to understand the principle in practice, not only to understand how to do it, but also to understand why they do, and when not to do so.

XP or Scrum full application of your project, but also might not be able to successfully, for others may not be suitable for you. These practices and methodologies agile gave us a starting point, but certainly not the end, the best way for you, but also your own explore and find practical work.

Myth five: agility well, so I want to develop a standard, all projects must follow the standard

Which two projects are the same, the customer is not the same, the staff is not the same, the demand is not the same, not even what may be the same. Not the same environment and problems solved, using the same method, is good is impossible to solve. By serving others, you should find the most suitable method for the project team to determine the method and not let the team to adapt this method. Therefore there was no uniform for all items. Any attempt to unify all the project process methods are incorrect.

The same time, for the same team as the project progresses, needs to understand the depth, the depth of technical understanding, the beginning of the process and methods will gradually not suitable. At this time also timely adjustment process requires a team to ensure the quality and efficiency of the project. Agility is dynamic, rather than static, because this world is change, change the world use the same method, it is unrealistic. Silver bullet never had, and would not exist in the limited future.

loadrunner recording ftp protocol script

The FTP protocol is a low-level protocol used to simulate the action of the user on the ftp server, such as landing, transfer files, disconnected operation

The script can be generated by recording the FTP session or manually enter ftp function

Steps:

Open vuser, the new catalog select E​​-business, select the ftp protocol

Pop-up recording options, select ie, or win32 applications (ftp client)

3.ftp operation finished recording, generate the script

Commonly used functions:

* ftp_login

Log ftp

Syntax: init ftp_logon (char * transaction char * url [attributes] LAST);

Example: ftp_logon (FTPlogon, URL = ftp://test1:123456 @ servaername: port ", LAST);

If anonymous users compared with anoymous, the port number can be omitted

* ftp_logout: canceled ftp connection

Syntax: int ftp_logout ()

Example: ftp_logou ();

* ftp_Logon_ex specified session login ftp

Syntax: int ftp_logon_ex (FTP * ppftp, char * transaction, char * url attributes,] LAST);

Example: ftp1 = 0;

ftp_logon_ex (& ftp1, "ftplogon", "url = URL = ftp://test1:123456 @ servaername", last)

* ftp_put to upload files to ftp server

Syntax: int the ftp_put (char * transaction <item list> LAST);

Example: the ftp_put (the "the ftp_put" "source_path ftpfile_1.dat", "target_path = temp / test.txt" LATS);

* ftp_get get the file from the ftp server

Syntax: int ftp_get (char * transaction <item list> LAST);

Example: ftp_get ("ftp_get", "source_path = / home / test.txt", "target_path = d :/ test.txt", the "PASSIVE = TRUE" ENDITEM, LATS);

the * ftp_dir specified directory Run the dir command

Syntax: int ftp_dir (char * transaction <item list> LAST);

Example: ftp_dir (the "ftp_dir, path = pub / test" LAST);

 Display the files and subdirectories in the test directory

* ftp_delete: delete the ftp file

* ftp_rendir: rename files

* ftp_rmdir: delete folders

* ftp_mkdir: create a folder

Web software test data input checklist

Checklist (Checklist) can help testers to save time, because many effective methods are not needed for each test rediscovered predecessors have been full summary, and a lot of validation Secondly, the checklist help testers to avoid missing person's memory is limited, inevitably there will be missed by the checklist checks can be effective to prevent the omission. Recently, IBM engineers Sujing Gang summarizes checklist of Web software test data input, and provides a good reference for Web testers.

Su Jinggang major input from the form data validation, data consistency, date input, digital input, the input of numeric characters summarized the main points need to check the Web test. Digital input, for example, which is a common test point checklist includes six elements:

1, to ensure that the minimum, maximum, correctly handle - For digital input domain, typically has its own maximum value and the minimum value of these two extremes processing requires special verification. In addition to verify the minimum and maximum values, the best testers with validation smaller than the minimum value, and the value is larger than the maximum that can be proper handling. For example, the need to enter a port number in the process of defining a connection, the minimum value of the port number 1. When the user input port number is 0, can be successfully added to the connection. When the user to verify the connection when prompted port number 0 is illegal. This is a defect in the product. The correct approach is When users view add the port number to 0, it gives the error message informing the user that the port number is illegal. A need to look at the place, when the input exceeds the maximum minimum, products need to give clear warnings and tips, inform the user what is the correct range.

2, to ensure that the numerical input box the first character position to enter a space error - When numerical input box characters to spaces when the input is no longer a value should be doing illegal input processing. Product process, you need to give an error message.

3 to ensure that the last character position of the input value of the input box to enter a space error - numerical input box last character to spaces when the input is no longer a value should do illegal input processing. Product process, you need to give an error message.

4, to ensure a positive sign (+) and the negative sign (-) is correctly processing - each relates to the numeric input are related to the problem of a numerical symbol. Because values ​​have positive and negative points, we need to ensure that the processing of positive and negative numbers are accurate and appropriate. Able to accept input box with a positive sign value, the processing results should talk without symbols (default is positive), the results of the numerical input, because in essence, the two values ​​are equal (except longer show the input values, because simple display on the difference of a + sign).

5, the divisor is 0 - divisor of 0 is the need to avoid all operations. Software products, if it comes to the division operation, you need to pay special attention to avoid division by 0 occurs. Which contains a variety of case the divisor is 0, the divisor is the input value of 0, the divisor is a middle results 0.

6, in all operations of adding 0 - 0 All the operator has an important role, and is also a very special value. Therefore, during the test, in all relates to the operation value of 0 has a good effect of the test product, can be tested to more 0.

Similarly, the list of data consistency test and boundary value:

1, check Enter the maximum character length working properly - each input domain has its own input character length limit, when the input length is the maximum length, the need to ensure that the product display and work properly. Usually belong to the maximum length of the character, to the difficulty of the page display great challenges, because of the limited page content displayed maximum.

2, verify digital input domain whether to accept the negative and whether it is reasonable to accept negative values ​​- digital number with area some cases should not accept negative input, then if not handled properly, when the negative input, there will be unpredictable situation. If allowed to accept the negative, test whether the processing of a negative test important.

3, to ensure that the data is saved all values ​​in the database have been complete save - save the data on the product page, you need to make sure that all values ​​are saved to complete the database. Access to the same data from different sources are consistent, synchronized. To verify this, the testers need to try to re-open after save and view the display, to see whether it is fully consistent with the data before saving, while trying to verify whether it can get consistent results from different path to access and apply the same input.

Data validation testing is often overlooked, Su Jinggang summarizes the three test points:

1, at any time when illegal data is entered, the system can perform poorly - software products designed for the purpose of not only receiving illegal data input, but the products need to ensure that when illegal data is still not bad, and still should make appropriate processing. Are many types of illegal data, including of data illegal characters in length, the size of the data, the data, the order of data input.

2 What are the consequences if the user is in the process of product use, remove the cookie will be? - Cookie is a product in order to identify the user and save user configuration information, session tracking and data stored in the local terminal. Product design needs to ensure that the user, if the user deletes cookies, the product is still handled properly, there will not be too bad, unpredictable behavior.

3, if you delete the cookie using the product will be the consequences? - If you delete the cookie after using the product, the user again to access the product, you need to ensure that the product is still to make appropriate treatment, not unexpected action.

Web software test data input checklist details, readers can view the original, but also includes a checklist form input, date input, digital character input. These lists provide a good reference for Web testers design test cases.

Based on the development process of software testing process management

0 Introduction

With the development of the software industry. Software products have been affected in many areas of our society, people increasingly high expectations of software role, gradually increase the awareness of the importance of software quality.

However, the software defect (bug) is associated with software product development process and the perfunctory goods, the use of new technologies and methods, software defects can not be completely eliminated. Therefore, early in the software development process, the introduction of software testing techniques to ensure the quality of the software, to reduce the rate of software defects, has been recognized by the software industry. - A stage in the software development process will produce appropriate documentation and products, rigorous evaluation and testing of these documents and products, early detection of problems. Timely and identify the item does not comply with the requirements analysis and project plan. Software defects early detection, early treatment can greatly reduce the problem of traditional software testing in the molding of the software products, modify the waste of human and material resources problem.

A software defect management

Software defect management tracking software defects found in the software development process management. And record the information of the state of software defects, guarantee the each software defects can be found off. Software defects software development process management is an important part in the project management process. Software testing process management in its essence is a document management software defects, standardization process.

1.1 software defects report

Software defect report (bug report) is the most important document to be submitted in the testing process. The importance of it just as much as the test plan. And greater impact on the quality of the product other than the document output in the testing process. Recorded software bug occurs environment, steps and results to fix errors developers can duplicate reporting bugs, thus facilitating the analysis of the bug causes positioning bug. Therefore, the effective bug report:

(1) to reduce the the secondary defect rate of the development department.

(2) to improve the development of modify defects speed.

(3) improve the credibility of the test department.

(4) enhance the testing and development sector collaboration.

In order to write - a good bug report should follow the following terms:

(1) streamlining: bug report should be clear and brief. The most direct, concise language to describe the most useful and important information.

(2) Accuracy: Make sure each bug reported are valid, verifiable, rather than own understanding, installation, improper operation and other factors bugs.

(3) neutral: objective language to describe the bug. Does not add any personal character language color description.

(4) precision: a clear description of the bug generated steps to ensure that the language is clean, organized.

(5) Positioning: According to the company or industry standard for accurate positioning of the discovery of the bug, and try to use short step to reproduce this bug.

(6) summarized: try to summarize the discovery of the problem.

(7) to reproduce: Check the reported bug can be reproduced. If you can not reproduce, the contingencies of the problem.

(8) Isolation: reported a bug in the bug isolation, environmental information Xieqing bug.

(9) Check: peer review is one of the most effective means of problem.

A 1.2 traditional software testing process

When - a software project to test, go through the test plans, test environment and use case design, implementation, unit testing, integration testing, system testing, assessment tests, and finally given the corresponding test report these a process.

Traditional testing process, although a certain degree of correspondence between the V-development model and software engineering, but the testing process and the development process or two separate processes in the early stage of the software testing process, but a separate plan to do, not software. audit and review of all operations in the development process before coding. The real test is to wait until after the molding of the software product. Before running the test cases. Defects found in the software development cycle, the more late. The cost of repair is higher. Therefore, in order to improve the efficiency of software development, it is necessary to software testing throughout the entire software development process.

2, based on the testing process of the development process

According to the characteristics of the software development process, software development process can be divided into: the project, needs research, outline design, detailed design, coding & unit testing, integration testing, system testing, acceptance testing stages. Then in connection with the various stages of the corresponding test.

In the project of the project, the testing process to synchronize the start, and cover the entire software development process. This requires making the software testing process to consider the documents and products of the various stages of the audit and review of the software development process. Needs assessment document and product at various stages of the testing process.

In the software testing process to consider a review of the various stages of the software development process documentation set. Appropriate assessment or test results, then they would have to document the formation of a new software defect reports or records. Project leader or senior executives through the reading of these documents, you can clearly know the software exists in various stages of development, eliminate software defects able to occur due to pre-design problems in the bud, to ensure the efficiency of software development and software quality . Records and documentation of the various stages of the testing process.

Based on the development process of the software testing process has the following advantages:

(1) are added at various stages of the software development software accreditation and Figure 3 test process test work added to the document and the product review to ensure that the development efficiency of the whole process of software development and software quality.

(2) to get rid of the traditional test processes and development processes are independent of each other, the status of software testing is only responsible for molding software products.

(3) The detailed documentation of the evaluation and test results for the various stages of the software development process. Beneficial project leader or high-level quality checks.

(4) assessment or testing throughout the software development process, can greatly reduce the workload of late testers and developers, conducive to optimize and upgrade the software.

3, Conclusion

Any software development organization would like to completely eliminate software defects are unrealistic and impossible to achieve. In order to develop high-quality software products, in addition to a rigorous development process and development standards. The introduction of software quality assurance throughout the software development process is an effective means. Through the review of documents and products in various stages of the software development process and test, a detailed documentation of the results, is to protect the quality of software products and reduce late workload management solutions. With the continuous expansion of the scale of software, the increasing number of software defects, the advantage of this program will be much more significant.

Talk about the need for performance testing of Internet banking project

Network life over the past decade network technology presents an ever-changing scene, people are more and more rich, especially in the last two years the popularity of the social network service (SNS). Demand for consumer services through a network of concurrent amount has become increasingly evident, software performance testing also will be more and more important.

Applications like "man" word, functional testing is the left write as if people left leg; development and design in the middle position, as if the brain core central; performance test with a flick of the right, like a person's right leg. A need to walk on two legs, step left leg, right leg step, in order to move forward in an upright manner, if the lack of First will be the foot of the slope, and even seat wheelchair dangerous. Software testing is the last "door" is software quality assurance throughout the software development process can not, or the lack of a strong referee. As a test engineer, had also been used in performance testing experience too stupid method, one of the functional modules of the application system performance testing: left hand holding the stopwatch Qiazhao count time, and the right hand controls the mouse to trigger action Now that I think really funny. In recent years, the performance testing across the stage when development is moving in the direction of automation and intelligent. The importance of performance testing highlights the importance, in the banking sector, it is difficult to predict because of the complexity and diversity of the network environment of the banking system (including core and peripheral systems), database environment, application server environment, system platform and technology architecture user load and increasingly complex application software performance is very difficult to control.

Here are two bank case to explain the need for performance testing:

   In early June 2011, XX online banking system shortly after the on-line, the user login failed the exception information network error. Project team responsible for the timely apply to the corporate headquarters for the relevant technical staff, which includes performance testing experts, to quickly build a performance test environment and system performance test of the entire online banking login exception reproduce the problem, senior developer code eleven investigation. Found that the main causes of the problem through performance testing the the password controls above in the third-party company. Password controls in code using a global variable, resulting in abnormal system concurrency visit other users of the system can not properly parse password to login failures. These problems appear in the on-line, although the problem is in the third-party password controls above, but also bring to the company, the project team and customer loss, especially damage to the image of the company, we work in the front of the line to do is not enough. In fact, these issues can before the on-line through the formal performance testing to circumvent, why do not you reflect on it?

Performance test by the vast majority of people think is a simple thing to do, is to take the tools that running ", this is a misunderstanding. Not done performance testing applications, the performance of a non-payment responsibility, with great risk, is not sound. In the bank so complex and diverse environment, even the best software development engineers also can not guarantee that the developed software performance issues. To improve system performance not rely solely on the performance testing can be done, but the performance tests are still effective means of control performance.

So software testing is an important performance testing is the most important, can not be ignored.