掌握Apache JMeter：自动化测试与网站性能实战指南

5星 · 超过95%的资源需积分: 9 155 浏览量更新于2024-07-28 1 收藏 32.28MB PDF 举报

Apache JMeter 是一款强大的、实践导向的入门级指南，专为自动化测试和网站性能测量而设计。本书由 Emily H. Halili 编写，由 Packt Publishing 出版，版权于2008年。《Apache JMeter：自动化测试与性能衡量实用指南》旨在帮助那些寻求网站性能提升的测试人员，无论是经验丰富的手动测试者，还是希望从手动测试转向自动化的开发者，甚至是测试经理和领导者寻找适合团队需求的测试工具。这本书的受众是测试社区，而非主要面向开发人员或技术人员，强调了 JMeter 在HTTP测试中的广泛应用性，即使没有编程背景的用户也能轻松上手。其特点是拥有直观且易于使用的拖放式图形用户界面（GUI），使得非技术用户也能迅速掌握基本操作。通过本书，读者可以学习如何使用 JMeter 对网站进行负载测试，检查其功能行为，并测量其性能指标。书中覆盖了以下关键知识点： 1. **JMeter基础**：介绍 JMeter 的安装、配置和基本工作原理，让读者了解如何创建和管理测试计划。 2. **测试脚本编写**：学习使用 JMeter 的内置元件（如HTTP请求、断言和定时器）来构造测试场景，以及如何编写简单和复杂的测试脚本。 3. **性能测试**：涵盖如何模拟大量并发用户、设置测试循环和事务处理，以评估网站在压力下的表现。 4. **功能测试**：学习如何验证网页元素，比如表单提交、API调用和页面响应，确保功能的正确性。 5. **报告与分析**：掌握如何生成测试结果报告，包括响应时间、吞吐量、错误率等关键性能指标的分析方法。 6. **自动化测试流程**：探讨如何将 JMeter 与其他测试工具集成，以及持续集成和持续交付（CI/CD）环境中的应用。 7. **案例研究和最佳实践**：书中提供实际项目中的应用实例，分享如何解决常见问题和优化测试策略。 8. **维护和扩展**：对于已有的测试脚本，了解如何维护和升级，以及如何处理未来的需求变化。 9. **预算和选择工具**：对测试经理来说，章节会讨论如何根据组织的预算和需求，决定是否采用 JMeter 作为测试自动化工具。 10. **版权声明**：最后，提醒读者关于版权的规定，强调未经出版商书面许可，不得复制、存储或传输书中的任何内容。《Apache JMeter：自动化测试与性能衡量实用指南》是一本全面而实用的教程，无论你是测试新手还是寻求工具替代的现有测试人员，都能从中获益匪浅，提升你的网站测试能力和效率。

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页未读，继续阅读

kawaei

粉丝: 1
资源: 8

掌握Apache JMeter：自动化测试与网站性能实战指南

非GUI模式下的简易jmeter：easy-jmeter-master.zip

快速入门Apache JMeter：性能测试与接口自动化

Apache JMeter：Java压力测试神器 - 功能与操作指南

Apache JMeter: A practical beginner's guide to automated testing and performance measurement for your websites

深入探讨 JMeter：性能测试的强大工具.pdf

RROR o.a.j.JMeter: Uncaught exception in thread Thread[#67,StandardJMeterEngine,6,main] java.lang.NoSuchMethodError: 'void org.apache.jmeter.samplers.SampleSaveConfiguration.setFormatter(java.text.DateFormat)'这个是什么意思

Linux 中的jmeter打开报错bash: jmeter: command not found.

Apache JMeter：功能与性能测试工具

最新资源