Feature/de 1199 openspec driver resiliency - #770
Open
bluepal-prasanthi-moparthi wants to merge 3 commits into
Open
Feature/de 1199 openspec driver resiliency#770bluepal-prasanthi-moparthi wants to merge 3 commits into
bluepal-prasanthi-moparthi wants to merge 3 commits into
Conversation
bluepal-prasanthi-moparthi
requested review from
ajanikow and
jwierzbo
as code owners
July 24, 2026 08:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR standardizes official ArangoDB driver resiliency test behavior using OpenSpec (DE-1199) and archives the completed change
standardize-driver-resiliency-tests.It establishes a language-independent behavioral contract so other drivers (JavaScript, Java, Python, etc.) can implement the same resiliency / Toxiproxy scenarios against the shared Kubernetes harness, without reverse-engineering Go tests.
Changes
Added OpenSpec capability specs under openspec/specs/ for:
Added Scenario → Capability Mapping in
driver-resiliency-reference.mdAdded cross-driver implementer checklist:
driver-resiliency-implementer-checklist.mdSynced delta specs into main OpenSpec specs and archived the change under
openspec/changes/archive/2026-07-24-standardize-driver-resiliency-tests/Minor Go alignment:
TestToxiproxy_ExtremeLatencynow asserts recovery after toxic removal.Validation
openspec validate standardize-driver-resiliency-tests(before archive)All 9 main capability specs validate (
openspec validate --specs)OpenSpec change archived after sync
Notes
Focus is specification + documentation standardization (plus a small Toxiproxy recovery assert). No new driver product APIs. Shared harness remains
run-driver-tests.sh / toxiproxy.shwith the documented env contract.