Skip to main content

Cloud Testing Standards That Matter for Performance Testing

Cloud Testing Standards That Matter for Performance Testing

Almost no published standard tells you how to load test a cloud application. What exists is a handful of standards and frameworks that give you words for the test process, a quality model that names performance as a requirement, and a certification scheme for testers. This post sorts them by what they define and which ones touch performance testing in the cloud. The companion post covers security and compliance standards for cloud load testing.

Key Takeaways

  • ISO/IEC/IEEE 29119-1 defines general software testing concepts and the vocabulary for the 29119 series. It is a vocabulary and process reference, not a cloud or performance standard.
  • ISO/IEC 25010:2023 is a product quality model with nine characteristics. One of them, performance efficiency, is the standard place to hang performance requirements.
  • ISTQB runs a tester certification scheme. It is a body of knowledge, not a standard your system can comply with.
  • No standard sets pass or fail numbers for response time or throughput. Those come from your own requirements.

Which standards apply to cloud performance testing?

Three bodies of work are worth knowing for testing quality and process, and none was released in 2026 or changes anything about how cloud tests run.

Standard or schemeWhat it definesBearing on cloud load testing
ISO/IEC/IEEE 29119-1:2022General concepts in software testing and key concepts for the 29119 seriesShared vocabulary for test strategy and planning
ISO/IEC 25010:2023A product quality model for ICT and software products, nine characteristicsNames performance efficiency as a quality characteristic to specify and measure
ISTQB Certified TesterA certification scheme at Foundation, Advanced, Specialist and Expert levelsCommon terminology among testers; not a compliance standard

What does ISO/IEC/IEEE 29119 say about testing?

The IEC webstore lists ISO/IEC/IEEE 29119-1:2022, “Software and systems engineering - Software testing - Part 1: General concepts”, as an International Standard, edition 2.0, published 2022-02-04. Its scope is one sentence: it “specifies general concepts in software testing and presents key concepts for the ISO/IEC/IEEE 29119 series” (webstore.iec.ch, read 2026-10-23). Part 1 replaces the 2013 edition.

For a performance team the value is practical but modest. It gives you agreed terms for things like test strategy, test levels and risk-based testing, so a test plan written for an auditor or a new colleague means the same thing to both. It does not say how many virtual users to run, from where, or what an acceptable 95th percentile is. I only read the Part 1 listing; the other parts of the series are paid documents I did not open, so this post makes no claim about them.

What does ISO/IEC 25010 say about performance?

ISO/IEC 25010:2023 is the second edition of the product quality model, which applies to ICT and software products and is meant for specifying and evaluating quality across a product’s life (national standards store previews, read 2026-10-23). It has nine characteristics: functional suitability, performance efficiency, compatibility, interaction capability, reliability, security, maintainability, flexibility and safety. Under performance efficiency sit time behaviour, capacity and resource utilization (quality.arc42.org summary of the standard, read 2026-10-23; I could not reach the ISO page itself, which refused automated requests).

This is the most useful of the three for load testing, because it turns “make it fast” into three testable questions:

  • Time behaviour: response and processing times under stated conditions. Your percentile targets belong here.
  • Capacity: the limit at which the product still meets its requirements. Stress and spike tests find this.
  • Resource utilization: CPU, memory and network used while meeting those times. Soak tests show leaks here.

Write each requirement with a number and a condition (“95% of checkout requests under 800 ms at 500 concurrent users”) and the test becomes a check against the requirement. The same idea is covered with examples in sample non-functional requirements, and the test types behind capacity and resource questions are listed in performance testing types.

Is ISTQB a standard?

No. ISTQB, the International Software Testing Qualifications Board, runs the Certified Tester scheme with Foundation, Advanced, Specialist and Expert levels. Its Foundation Level syllabus, v4.0, is positioned for Waterfall, Agile, DevOps and continuous delivery teams (istqb.org, read 2026-10-23). It is useful for common terminology and for hiring and training, but nothing in it can be “complied with” by a system. I did not find a performance-testing certification on that page, so I do not claim one.

What about cloud-specific standards?

Cloud security and compliance frameworks exist, but they concern the provider’s and your organisation’s controls, not how a load test is designed. Where they matter for a load test (test data, environment access, the vendor that generates the load) is the subject of the security and compliance post. For the security side of performance testing specifically, see performance testing security.

What should a performance team do with this?

Use the standards as scaffolding and put your own numbers in it:

  1. Pick a quality vocabulary, such as the 25010 characteristics, and list your performance requirements under time behaviour, capacity and resource utilization.
  2. Give every requirement a measurable target and the load condition it applies under.
  3. Write the test plan in shared terms so it survives a reviewer or an audit.
  4. Run the tests from the regions your users are in; LoadFocus load testing runs tests from 25 AWS regions (loadfocus.com/load-testing, read 2026-10-23).
  5. Record results against the requirement, not against last week’s run.

Frequently Asked Questions

Is there an official cloud testing standard for 2026?

No standard released this year redefines cloud testing. The relevant ones are older: ISO/IEC/IEEE 29119-1 (2022) for testing concepts and ISO/IEC 25010 (2023) for the quality model.

Which standard defines performance requirements?

ISO/IEC 25010:2023 names performance efficiency as a quality characteristic, with time behaviour, capacity and resource utilization. It does not give target values; you set those.

Do I need ISO 29119 compliance to run load tests?

No. Load tests do not require it. Some organisations adopt it for process consistency or because a customer or regulator asks.

Is ISTQB certification required for performance testing?

No. It is optional professional training and a shared vocabulary, not a legal or technical requirement.

Sources

  • ISO/IEC/IEEE 29119-1:2022, webstore.iec.ch/publication/74072, read 2026-10-23.
  • ISO/IEC 25010:2023: ANSI webstore preview and Estonian standards body listing (scope and edition), and quality.arc42.org/standards/iso-25010 (characteristics), read 2026-10-23.
  • ISTQB Certified Tester Foundation Level v4.0, istqb.org, read 2026-10-23.
  • LoadFocus load testing page, loadfocus.com/load-testing, read 2026-10-23.

Chris

Head of Content at LoadFocus

Chris leads content and oversees development across the services this blog covers. The guides and tool comparisons here come out of the same decisions that shape what ships.

Weekly tips right in your inbox.

Don’t miss out on the latest testing tips and tricks, tools and news related to software testing.

Already +20,000 members in the list.

The Load Testing Platform with AI That Explains Your Results

Load test websites and APIs from 25 cloud regions, monitor page speed and uptime, and get AI analysis that explains your results in plain English.

Cloud load testing, website speed and API monitoring in one place.

Hi there! Can I share a cool thing I'm working on with you?

A software testing newsletter that sparks joy.

Our goal is to create helpful content for software developers and testers.

If you're not into it, you can unsubscribe instantly.