skills.rest
vladimir-shirmanov
vladimir-shirmanovCOMMUNITY
Explore all skills by this author →
GitHub

httpyac-http-e2e-assertions

Convert .http autotests into executable HTTP endpoint assertions.

Updated Apr 5, 2026
Search Tags:#qa#api-testing#e2e-tests#test-automation#http-testing#httpyac#executable-assertions
One-click install
npx skills add https://github.com/vladimir-shirmanov/tenax --skill httpyac-http-e2e-assertions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: httpyac-http-e2e-assertions
Source: https://github.com/vladimir-shirmanov/tenax/tree/main/.github/skills/httpyac-http-e2e-assertions
Command: npx skills add https://github.com/vladimir-shirmanov/tenax --skill httpyac-http-e2e-assertions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts QA-authored .http autotests into robust, executable assertions for reliable HTTP end-to-end verification.

Core Features & Use Cases

  • Inline assertions for status, headers, and body to produce deterministic test outcomes.
  • Support for multi-step flows with response data reuse when necessary.
  • Clear guidance on structuring scenarios and aligning with API contracts during QA handoffs.

Quick Start

Create or update an .http autotest under tests/http and add executable assertions to validate status, headers, body, and timing.

Frequently Asked Questions about httpyac-http-e2e-assertions

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

FAQPage Schema
How do I add executable assertions to .http files for API testing?▼

You can add inline httpyac assertions directly inside .http autotests under tests/http to verify status codes, headers, body structure, and timing across multiple scenarios like success, auth failures, and rate limits.

Can I verify JSON response fields and reuse data across multiple HTTP requests?▼

HTTP testing with inline assertions supports field-level verification for JSON responses and handles multi-step flows with cross-request response data reuse when necessary for complex API verification workflows.

What is the best way to structure E2E HTTP tests for different API scenarios?▼

Structuring E2E HTTP tests involves organizing .http autotests under tests/http with executable assertions that align with API contracts, covering scenarios like validation errors, not found, and auth failures during QA handoffs.

Do I need JavaScript blocks for complex HTTP response checks?▼

Inline httpyac assertions handle standard status, header, and body checks, while optional JavaScript blocks provide support for complex assertion logic when inline checks are insufficient for API verification.

How does converting .http autotests into executable assertions improve test automation?▼

Converting .http autotests into executable assertions produces deterministic test outcomes by automating verification of HTTP endpoints, ensuring reliable checks for status, headers, body structure, and timing across varied scenarios.

Related Skills

Explore More Software Engineering Skills→
ericwang915ericwang915
38

http_request

Perform HTTP requests to any API endpoint with custom headers and JSON payloads.

Community
Intermediate
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
eleva-labseleva-labs

api-validate

Validate API implementations against OpenAPI specifications and contracts.

Official
Intermediate
jieni777jieni777
1

api-testing

Send HTTP requests and validate API responses against assertions.

Community
Intermediate