Apache JMeter：自动化测试与性能衡量实战指南

5星 · 超过95%的资源需积分: 10 131 浏览量更新于2024-07-26 收藏 5.24MB PDF 举报

Apache JMeter 是一款开源的性能测试工具，由 Apache Software Foundation 发行，专为 Web 应用程序进行自动化测试和性能测量而设计。该工具最初在2008年6月由 Packt Publishing 出版的《Practical Beginner's Guide to Automated Testing and Performance Measurement for Your Websites》一书中详细介绍，作者是 Emily H. Halili。这本书为初学者提供了实践指导，帮助他们理解和掌握如何使用 JMeter 进行负载测试、功能测试、性能基准分析等任务。 Apache JMeter 主要用于检查系统的稳定性、响应时间、吞吐量、并发用户能力等关键性能指标，适用于软件开发和质量保证过程中，尤其是在进行系统上线前的性能压力测试。它支持多种协议，包括 HTTP、FTP、JDBC、JMS、SOAP、FTPS等，使得测试范围广泛，适用于不同类型的网络应用。在使用 JMeter 时，读者可以创建和管理测试计划，设置测试脚本（如采样器、断言、监听器等），以及配置虚拟用户和线程组来模拟真实的用户流量。通过图形化的界面，用户可以直观地监控测试过程中的性能数据，如响应时间、成功率、错误率等，并进行详细的报告生成。版权方面，这本书享有Packt Publishing的独家权利，未经许可，不得复制、存储或通过任何方式传输书中的内容，除非用于嵌入在评论或批判性文章中。尽管作者和出版社已尽力确保信息的准确性，但本书不提供任何形式的保证，包括明示或暗示的，因此对由此产生的损失或声称的损害不负责任。此外，虽然 Packt Publishing 在出版时会尽力提供商标信息，但并不能保证这些信息的准确性。本书首次出版日期为2008年6月，生产参考编号为1200608。作为一本专业的技术书籍，Apache JMeter 的学习和使用对于提升应用程序的性能优化和测试能力具有重要意义，适合那些希望深入理解并应用于实际工作中的 IT 专业人士。

Automated Testing

Really, what is test automation? Is it something like pressing some button to turn on

the testing on auto-pilot? To an extent, yes, you can have that, and more. According

to Wikipedia, (http://en.wikipedia.org/wiki/Test_automation):

Test automation is the use of software to control the execution of tests, the

comparison of actual outcomes to predicted outcomes, the setting up of test

preconditions, and other test control, and test reporting functions.

Simply put, it is the process of automating the manual testing process currently in

use, by the use of software. Hence, this denition goes further than simply using

some Word Processor software.

This chapter will give you a quick overview of what test automation is all about and

its signicance in the testing process, and ultimately, the software process. It aims

to help you decide whether test automation is the way to go for testing applications.

It will also describe the cost-effectiveness of test automation in comparison with

manual testing or no testing at all.

As you begin to ponder if test automation is what you need, some questions may be

lingering in your mind:

Why do I need to automate software testing?

How do I decide whether to automate or not?

How much would test automation add to the total cost of testing?

This chapter will answer your questions.

•

Automated Testing

[ 8 ]

Why Automate Testing?

Some software project managers hold strongly to the myth that testing costs too

much, takes too much time, does not help them build the product, and can create

hostility between the tester(s) and the development team. You will nd these are the

very people who would spend the least on testing.

On the other hand, there are smarter software managers who understand that

testing is an investment in quality. Hence, they tend to spend more on testing.

Efcient test project management produces a positive return, ts within the overall

project schedule, has quantiable ndings, and is seen as a denite contributor to

the project.

However, as developing software overruns, as it normally does, time is at a

premium. As you may know or have experienced, 'manual' testing, especially

regression testing can be exhausting. A time-consuming and tedious process, it is

inefcient and conicts with today's shorter application development cycles. As a

result, it gets in the way to test an application thoroughly—enabling critical bugs to

slip through undetected. What's more, manual tests are prone to human error and

inconsistencies that can distort test results.

Can we do without automation? Yes, of course—if time is abundant and your client

(or boss) is NOT on your tail for the application's next release. However, for most of

the time, this is not the case. In software testing, time is a determining factor and the

effective use of automation CAN help improve the testing speed.

On the other hand, despite of the appeals of test automation, we need to bear in

mind that test automation may just be suitable for only parts of the software testing

process. Automated testing IS NOT a total replacement for manual testing. Certain

aspects of testing an application would rely more on the human tester than on

test automation. The ultimate testers still are the human testers themselves; where

applicable, test automation only complements manual testing. Test automation may

not test any better than the human tester, but if implemented wisely, can certainly

help the tester test faster. Since certain testing of the application can be automated,

the tester can spend more quality time on more important and critical aspects of the

testing. Ultimately, the tester can test better and more effectively.

Chapter 1

[ 9 ]

To Automate or Not to Automate—Some

Hints

The previous paragraph cautions against using automation to replace manual

testing, putting you, the reader (or the tester) in an awkward predicament. However,

let us think about an average-case scenario: You are pressed against a tight budget

and schedule, and you are sure that manually regression testing the application

completely would only leave you and your team physically and mentally exhausted.

Would automation help you test, if not any better, at least faster? Some hints may

just help you decide:

Pick a good time to start automating:

Automation is best used after the tester has grasped the fundamental testing

skills and concepts through manual testing experience. Another good time is

when the tests that are going to be repeated or simulated, as normally found

in regression testing and performance testing, respectively. As this goes, not

all testing approaches may justify the use of automation.

Rex Black in his article, Investing in Software Testing: Manual or Automated?

concludes that the decision to automate testing comes from the need to repeat

tests numerous times or reduce the cycle time for test execution while higher

per-test costs and needs for human skills, judgment, and interaction incline towards

decision to test manually.

Not all testing approaches are suitable to automate:

Suitable: Acceptance, Compatibility, Load, Volume or Capacity, Performance

and Reliability, Structural testing, Regression, Exception or Negative testing.

Type of Testing

Description (adapted from source: http://www.istqb.org)

Acceptance

testing

Formal testing with respect to user needs, requirements, and

business processes conducted to determine whether a system satises

or does not satisfy the acceptance criteria and to enable the user,

customers, or other authorized entity to determine whether or not to

accept the system.

Compatibility

testing

The process of testing to determine the interoperability of a

software product.

Load testing A type of performance testing conducted to evaluate the behavior of

a component or system with increasing load, e.g. numbers of parallel

users and/or numbers of transactions, to determine what load can be

handled by the component or system.

Volume/Capacity

testing

Testing where the system is subjected to large volumes of data.

•

Automated Testing

[ 10 ]

Type of Testing

Description (adapted from source: http://www.istqb.org)

Performance

testing

The process of testing to determine the performance of a software

product.

Reliability testing The process of testing to determine the reliability of a software

product.

Structural testing Testing based on an analysis of the internal structure of the

component or system (also known as white-box testing)

Regression testing Testing of a previously tested program following modication

to ensure that defects have not been introduced or uncovered in

unchanged areas of the software, as a result of the changes made.

Exception testing Testing behavior of a component or system in response to erroneous

input, from either a human user or from another component or

system, or due to an internal failure.

Negative testing Tests aimed at showing that a component or system does not work.

Not suitable: Installation and setup, Conguration and Compatibility,

Documentation and help, Error handling and Recovery, Localization,

Usability, and any other that relies heavily on human judgment.

Type of Testing

Description (adapted from source: http://www.istqb.org)

Installation and

setup testing

Testing that focuses on what customers will need to do to install and

set up the new software successfully.

Conguration

testing

The process of testing the installability or congurability of a

software product.

Compatibility

testing

Testing to evaluate the application's compatibility with the

computing environment.

Documentation

testing

Testing the quality of the documentation, e.g. user guide or

installation guide.

Error handling

testing

Testing to determine the ability of applications system to properly

process the incorrect transactions.

Recovery testing Testing how well the software is able to recover from crashes,

hardware failures, and other similar problems.

Localization

testing

Testing that focuses on internationalization and localization aspects

of software in adapting a globalized application to a particular

culture/locale.

Usability testing Testing to determine the extent to which the software product is

understood, easy to learn, easy to operate, and attractive to the users

under specied conditions.

Chapter 1

[ 11 ]

A point worthy of note is that there are tests that may justify the use of both

manual and automated testing. These include: functionality testing, user

interface, date and time handling, and use cases (user scenarios).

Make automation only a supplement to a testing project:

In many cases, when a test requires the human mind making better

judgments, use of automation merely accommodates that, but is not its

replacement. For example, performing usability testing on application

with a user interface designed for visually impaired users, no automation

test can be any better than the human tester making judgments about the

appropriate page element sound, size, or colors that would benet the

application's targeted users. While testing other aspects of the application,

load testing or performance testing, for example, can be automated.

Do some comparison of Automated vs. Manual Testing:

Manual Testing Automated Testing

Running (and re-running) tests manually

can be very time consuming.

Cost-effective, if you have to repeat tests

numerous times.

All required tests need to be rerun each

time there is a new build—which eventually

would become very mundane and tiresome.

Also, would wear out the tester.

Allows you to run automation against code

that frequently evolves in a timely manner.

Most suited to test codes within Agile

software development framework.

Manual tests would have to be run

sequentially.

Automated tests can be run simultaneously

on different machines.

Time-consuming and tedious if testing a

large test matrix. Highly error-prone.

Aids in testing a large test matrix.

If the test case only runs twice a coding

milestone, it should most likely be a manual

test. Less cost than automating it.

It costs more to set up and congure a test

automation framework and test cases.

Better suited if you are testing UIs. Cannot automate visual information. More

suited for non-UI tests

It allows the tester to perform more ad hoc

(random testing), which increases the odds

of nding real user bugs.

Automation test tools are software

themselves, and there is no 'perfect'

software. Bugs may also surface in

these tools.

Tester can do testing without automation. Only suitable for portions of the testing

process.

•

剩余137页未读，继续阅读

齐格飞飞

粉丝: 17
资源: 32

Apache JMeter：自动化测试与性能衡量实战指南

Apache-JMeter-5.1.1安装包

ApacheJMeter

ApacheJMeter.jar

[零成本实现WEB性能测试.基于APACHE.JMETER].温素剑.扫描版.pdf

[零成本实现WEB性能测试.基于APACHE.JMETER].温素剑.扫描版

org.apache.jmeter.samplers.SampleSaveConfiguration.setFormatter(java.text.DateFormat) 方法

could not initialize class org.apache.jmeter.gui.util.filedialoger

Error generating the report: org.apache.jmeter.report.dashboard.GenerationException: Cannot create temporary directory "C:\Program Files\apache-jmeter-5.4.1\bin\temp", check property "jmeter.reportgenerator.temp_dir" ... end of run

最新资源