Green QA Metrics: Quality That Breathes.

With this post, we conclude the series dedicated to Green Quality Assurance. In the previous articles, we explained what Green QA means and its impact on companies as well as a possible framework for its implementation.

Now that we already understand what this methodology is and how to implement it, the only thing left is to understand how we can measure it. In this final post, we focus on the foundation of the entire process: measurement, addressing the KPIs that can be used to turn requirements into data and to track progress as accurately as possible based on objective information.

It is not an easy task to have all the tools and frameworks required to perform these measurements, which is why the process is progressive and requires commitment from every member of the organization.

In Green QA, metrics are the thermometer of our efficiency. We do not measure for bureaucracy’s sake, but to identify “energy leaks” and “digital waste.”

When defining the KPIs and OKRs needed to evaluate the different aspects of GQA, we grouped them into the following measurement categories:

• Energy and software (technical efficiency)
• Carbon and waste (planetary impact)
• ESG data quality (trust and compliance)
• Operational efficiency and “Digital Waste” (process improvement)

Energy and Software KPIs (Technical Efficiency)

Here, we measure the physical effort hardware performs to run our software. The KPIs used for this area are the following:

Carbon and Waste KPIs (Planetary Impact)

We transform watts into real environmental impact. The KPIs used for this area are the following:

ESG Data Quality KPIs (Trust and Compliance)

If sustainability data is unreliable, the strategy fails. The KPIs used to measure this area are the following:

Operational Efficiency and “Digital Waste” KPIs (Process Improvement)

It is not enough for a test to consume little; the key is not executing what is unnecessary. Digital waste is silent pollution. The data used to measure this area includes the following:

Standards and Compliance

It is not enough to “be green”; you must prove it to international regulators. Green QA is the final filter ensuring that a company does not incur legal risks by reporting inaccurate data.

In the previous post, we discussed legal aspects where applying Green QA within a company is beneficial. Here, we will look at how to ensure compliance through data and how to verify whether the quality process we followed has contributed to regulatory compliance using the KPIs defined above.

CSRD (EU Directive) + ESRS

The CSRD (Corporate Sustainability Reporting Directive) is the European regulation (in force since 2024) that requires large companies and publicly traded organizations to report detailed sustainability information under Environmental, Social, and Governance (ESG) criteria.

In Spain, the Corporate Sustainability Reporting Bill was approved on October 29, 2024, as a transposition of the CSRD. The ESRS (European Sustainability Reporting Standards) are the mandatory technical standards for complying with the CSRD.

From a QA perspective, we can audit sustainability data. Here, Green QA acts as the “Data Auditor.” It must ensure that ESG data (such as server consumption in Staging) is not based on rough estimates but has technical traceability. If reporting software fails, the company may face sanctions for Greenwashing. We can use the following checklist to verify compliance:

• Data traceability. Is it possible to trace emission data from the original sensor/log to the final report without manual alterations?
• ESG API validation. Has the integration with Cloud providers (AWS/Azure/GCP) been tested to ensure consumption data is extracted without loss?
• Auditability. Does the QA metric include verifiable technical evidence for external audits?
• Accuracy vs. estimation. Have generic estimates been replaced with real hardware consumption data whenever possible?

GHG Protocol (Scope 3 - Software)

The GHG Protocol (Scope 3) is the most widely used global standard for measuring and reporting indirect greenhouse gas emissions (GHG) occurring across a company’s value chain, excluding purchased energy emissions (Scope 2).

From a QA perspective, it is necessary to validate that third-party tools (testing SaaS platforms, CDNs, paid APIs) provide real emissions data. Quality Gates can be created to block deployments if the “carbon budget” of a microservice exceeds protocol limits. We can use the following checklist to verify compliance:

• Footprint calculation. Have updated CO2 conversion factors been applied to the energy consumed during deployment?
• Supplier filtering. Has it been verified that partners (testing SaaS platforms, CDNs) hold ISO 14001 or Energy Star certifications?
• Carbon budget. Does the current release remain within the established emissions limit compared to the previous period?
• Formula validation. Have unit tests been performed on emissions calculation formulas to ensure mathematical accuracy?

ISO/IEC 21031 (Software Carbon Intensity - SCI)

This is the Unit Testing of the carbon footprint. It is an international standard for calculating software carbon intensity (SCI).

The role of Green QA here is to integrate carbon footprint measurement into the testing pyramid. Just as we validate response times, QA validates the energy cost per transaction. If a database change increases CPU cycles, QA acts as the gatekeeper preventing that “energy waste” from reaching production.

• Intensity analysis. Has kWh consumption been measured for each test suite execution?
• CPU optimization. Does the code avoid unnecessary cycles or “Green Smells” (infinite loops, redundant API calls)?
• Headless testing. Have tests been run in headless mode to reduce the energy consumed by graphical rendering?
• Idle Energy validation. Has it been verified that Staging environments shut down or auto-scale to zero after execution?

Consumer Empowerment Directive (Anti-Greenwashing)

The EU is banning generic environmental claims without evidence (“100% eco-friendly software”). From a QA perspective, evidence must be certified. If marketing claims the app consumes 30% less battery, QA should have run energy regression tests (using tools such as GreenFrame or Lighthouse) that support the claim with empirical and repeatable data.

Web Accessibility (WAD / WCAG) as Sustainability

There is a direct correlation: an accessible and lightweight website is also a low-consumption website. From a QA perspective, the DOM must be validated for efficiency. Fewer unnecessary elements and redundant requests mean fewer CPU cycles on the client device. Here, QA combines social impact (inclusion) with environmental impact (efficiency).

Carbon Footprint Measurement Table

At this stage, we present a table with useful data commonly used to automate carbon footprint calculations. These values evolve as technologies improve and become more efficient, so they should be considered estimates.

Conclusions

Throughout this three-part series on Green Quality Assurance, we have explored the possibilities within the technology world, and specifically within the software industry, to take action and improve energy efficiency.