leaderboard-totalcount-backend-regression

Name: leaderboard-totalcount-backend-regression
Availability: InStock
Author: tombelial666

Validate backend TotalCount against paged leaderboard data to detect regressions.

Updated Mar 24, 2026

Search Tags:#validation #backend #regression #leaderboard #paging #data-consistency

Ready to run

npx skills add https://github.com/tombelial666/test --skill leaderboard-totalcount-backend-regression

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: leaderboard-totalcount-backend-regression
Source: https://github.com/tombelial666/test/tree/main/.cursor/skills/leaderboard-totalcount-backend-regression
Command: npx skills add https://github.com/tombelial666/test --skill leaderboard-totalcount-backend-regression

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that the backend TotalCount aligns with the effective paged data to catch regressions that would mislead API consumers.

Core Features & Use Cases

Regression verification: compares TotalCount against actual page results across leaderboard data.
CI-friendly checks: integrates in release or bug-fix validation pipelines to flag inconsistencies.
Use Case: run in automated tests to ensure paging remains consistent after backend changes.

Quick Start

Set the required ETNA credentials and run the regression suite against the leaderboard backend.

Frequently Asked Questions about leaderboard-totalcount-backend-regression

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate backend TotalCount against effective paged data to detect paging regressions?▼

To detect backend TotalCount regressions, compare the reported TotalCount against the actual effective paged data returned by the leaderboard backend. This verifies paging consistency and flags data mismatches early.

Can I run leaderboard regression checks in a CI pipeline for backend release validation?▼

Yes, leaderboard regression checks integrate into CI pipelines for release validation. The suite runs automated tests to flag TotalCount and paging inconsistencies after backend changes, ensuring data flows remain correct.

What ETNA credentials and endpoints are required to test leaderboard paging consistency?▼

Validating leaderboard paging consistency requires ETNA_ACCOUNTS_URL, ETNA_TOKEN_URL, ETNA_APP_KEY, ETNA_USERNAME, and ETNA_PASSWORD. It calls the GET accounts-with-balances and POST token endpoints to verify data.

How does accounts-with-balances validation handle edge cases in leaderboard data flows?▼

Accounts-with-balances validation handles edge cases by using optional ETNA_LB_PAGE_SIZE, ETNA_LB_FILTER, and ETNA_LB_FULL_WALK configurations to thoroughly verify TotalCount invariants across complex leaderboard data flows.

Why does my leaderboard TotalCount mismatch the effective paged data returned by the backend?▼

A TotalCount mismatch occurs when the backend TotalCount invariant fails to align with the effective paged data, indicating a regression. Comparing TotalCount against actual page results detects these data consistency bugs early.