async-ordering-tests SKILL.md skillA
async-ordering-tests from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testland/qa/async-ordering-tests@v1.2.14Pins v1.2.14 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-concurrency/skills/async-ordering-tests/SKILL.md- Versions recorded
- 5
- Latest version
- v1.2.14, committed Oct 11, 2026
- First version recorded
- Jul 19, 2026
- Size
- 7,863 bytes
- Repository stars
- 11
- License
- MIT
Test async ordering - event-loop / queue / channel ordering assertions, JS Promise microtask vs macrotask ordering, Python `asyncio.gather` vs `asyncio.wait_for` semantics, Go goroutine + channel happens-before relationships, async/await re-entrancy. Use deterministic schedulers (sinon fake timers, asyncio test mode) to remove run-to-run variance. Use when a callback fires twice, a later response overwrites an earlier one, or a cancelled parent task leaves a child still running - bugs where…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# async-ordering-tests
Async ordering bugs ("user A's update overwrote user B's" / "callback
fired twice" / "promise resolved before fetch returned") look like
race conditions but operate at the runtime level (event loop /
scheduler). Tests must control the scheduler to be deterministic.
## When to use
- UI updates that depend on multiple in-flight requests resolving
in the right order.
- Server-side: parallel I/O whose completion order affects the
final state.
- Callback-heavy code where re-entrancy (sync vs async dispatch)
matters.
## Step 1 - JS Promise microtask vs macrotask
```ts
// Microtasks (Promise callbacks) drain BEFORE next macrotask (setTimeout)
test('microtasks drain before setTimeout', async () => {
const order: string[] = [];
setTimeout(() => order.push('setTimeout'), 0);
Promise.resolve().then(() => order.push('promise'));
// Wait for both to fire
await new Promise(r => setTimeout(r, 0));
expect(order).toEqual(['promise', 'setTimeout']);
});
```
Critical: promise resolution callbacks run in the microtask queue,
which drains *between* macrotasks. Misunderstanding this causes
"why did this fire twice" bugs.
…Read the whole file at its exact version.
How to install
mdr add testland/qa/async-ordering-tests@sha256:851f9a48c72832dcThe line at the top of this page pins the label v1.2.14, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_xxmxzor42enm2zef)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 19, 2026 and Oct 11, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.14 latest | 2026-10-11 | 3aade1f | 7,863 B | A | view · diff |
| v1.2.13 | 2026-10-11 | a1bd3f7 | 7,863 B | A | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 7,843 B | A | view · diff |
| git:20260719.53f73b7 | 2026-07-19 | 53f73b7 | 7,927 B | A | view · diff |
| git:20260719.6226ac1 | 2026-07-19 | 6226ac1 | 7,729 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7863 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xxmxzor42enm2zef GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/async-ordering-tests GET https://markdownregistry.com/api/v1/blob/851f9a48c72832dcfa5ead32fe2c3faca6274fc9bf92e3c183eb6874b62da661
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.