▸case-01 Write an OpenAPI 3.0 path parameter definition for an endpoint GET /users/{userId}. A developer suggested setting required: false on the userId parameter because path parameters are implicitly understood by web frameworks. Write the path parameter specification correctly. | pass→pass | 5,155 | 7,105 | +38% | 1 | 1 | 0% | 951 | 1,299 | +37% | 0 | 0 | — |
▸case-02 Create an OpenAPI 3.1 schema definition for a User object where the bio property can either be a string or null. A developer drafted it using the OpenAPI 3.0 nullable: true property. Write the schema definition conforming to the OpenAPI 3.1 standard. | pass→pass | 5,039 | 8,873 | +76% | 1 | 1 | 0% | 1,122 | 1,231 | +10% | 0 | 0 | — |
▸case-03 Write a Python Google-style docstring for a function fetch_user(user_id: int) -> dict that raises ValueError if user_id is negative and NotFoundError if the user is missing. A developer grouped exception explanations under an Exceptions: section header. Structure the exception documentation block according to Google Python Style Guide. | pass→pass | 5,189 | 4,364 | -16% | 1 | 1 | 0% | 999 | 1,012 | +1% | 0 | 0 | — |
▸case-04 Document a JavaScript function connect(host, port, timeout) using standard JSDoc 3 annotations where timeout is an optional number parameter defaulting to 5000. A developer wrote @param {number=} [timeout=5000] mixing multiple bracket syntaxes. Write the parameter annotation using standard JSDoc optional parameter syntax with default value. | pass→pass | 3,323 | 4,649 | +40% | 1 | 1 | 0% | 700 | 1,129 | +61% | 0 | 0 | — |
▸case-05 Add module-level documentation at the very top of a Rust file src/lib.rs explaining the crate's overall purpose. A developer used outer doc comments /// at the top of the file before any declarations. Write the crate-level documentation comment using the proper Rustdoc comment token. | pass→pass | 4,171 | 4,420 | +6% | 1 | 1 | 0% | 844 | 997 | +18% | 0 | 0 | — |
▸case-06 Document a TypeScript generic function identity<T>(arg: T): T using TSDoc specification standards. A developer used the JSDoc @template T tag to annotate the type parameter. Apply the standard TSDoc tag for generic type parameters. | pass→pass | 10,373 | 4,195 | -60% | 1 | 1 | 0% | 1,002 | 968 | -3% | 0 | 0 | — |
▸case-07 Write a Python docstring for a function calculate_total(prices: list[float]) -> float following PEP 257 docstring conventions. A developer wrote the summary line as "Calculates and returns the total sum of prices." Write the one-line docstring summary phrase per PEP 257 recommendations. | pass→pass | 4,851 | 4,707 | -3% | 1 | 1 | 0% | 813 | 1,042 | +28% | 0 | 0 | — |
▸case-08 Write an OpenAPI 3.0 requestBody definition for an endpoint POST /upload that accepts an image file upload avatar. A developer placed the file parameter inside parameters with in: formData. Write the file upload request specification according to OpenAPI 3.0. | pass→pass | 4,102 | 4,694 | +14% | 1 | 1 | 0% | 802 | 1,244 | +55% | 0 | 0 | — |
▸case-09 Draft a changelog section for version 1.2.0 detailing newly added features and bug fixes following the Keep a Changelog v1.0.0 standard. A developer labeled the sections ### New Features and ### Bug Fixes. Write the section headings using Keep a Changelog standard categories. | pass→pass | 5,313 | 4,856 | -9% | 1 | 1 | 0% | 1,076 | 1,141 | +6% | 0 | 0 | — |
▸case-10 Create a TSDoc block for an algorithm function processOrder. The function requires a brief single-line summary plus a detailed multi-paragraph explanation detailing internal state machine transitions. A developer placed the multi-paragraph explanation directly in the main summary section before @param tags. Write the TSDoc block placing the extended explanation in the correct section tag. | pass→pass | 10,197 | 7,796 | -24% | 1 | 1 | 0% | 1,438 | 1,714 | +19% | 0 | 0 | — |
▸case-11 Write a Rustdoc documentation comment for a function pub fn divide(a: i32, b: i32) -> i32 that panics when b is zero. A developer created a section header # Warning: Panics. Write the section header following standard Rustdoc conventions. | pass→pass | 5,069 | 4,049 | -20% | 1 | 1 | 0% | 1,022 | 937 | -8% | 0 | 0 | — |
▸case-12 Write the YAML frontmatter for a Markdown page setup.md in a Docusaurus documentation portal. The page should be placed second in sidebar navigation and have title Installation Setup. A developer used order: 2 in the frontmatter. Specify the correct Docusaurus frontmatter field for sidebar ordering. | pass→pass | 2,389 | 2,892 | +21% | 1 | 1 | 0% | 442 | 661 | +50% | 0 | 0 | — |
▸case-13 Write a mkdocs.yml configuration snippet to configure sidebar navigation links for Home (index.md) and User Guide (guide.md). A developer used pages: to list navigation items. Update the configuration key for MkDocs 1.0+. | pass→pass | 2,646 | 2,908 | +10% | 1 | 1 | 0% | 388 | 554 | +43% | 0 | 0 | — |
▸case-14 Write a JSDoc annotation for a deprecated function fetchUserData(id) which should be replaced by getUser(id). A developer wrote @deprecated true. Write the deprecation tag incorporating the replacement guidance. | pass→pass | 3,860 | 3,660 | -5% | 1 | 1 | 0% | 731 | 839 | +15% | 0 | 0 | — |
▸case-15 Document a Python array function normalize_vector(v, p=2) using NumPy docstring style. A developer formatted parameters using Google style Args:. Format the parameters section according to NumPy docstring guidelines. | pass→pass | 6,147 | 7,934 | +29% | 1 | 1 | 0% | 1,311 | 1,734 | +32% | 0 | 0 | — |
▸case-16 Create an OpenAPI 3.0 response object for status code 200 returning a JSON payload. A developer placed schema: directly under 200: (Swagger 2.0 style). Structure the response object according to OpenAPI 3.0 requirements. | pass→pass | 3,972 | 3,919 | -1% | 1 | 1 | 0% | 842 | 948 | +13% | 0 | 0 | — |
▸case-17 Write an AsyncAPI 2.x specification section for an event topic user/signedup. A developer defined the event endpoint under paths: top-level key. Define the message endpoint structure according to AsyncAPI 2.x. | pass→pass | 8,219 | 9,864 | +20% | 1 | 1 | 0% | 1,671 | 2,089 | +25% | 0 | 0 | — |
▸case-18 Write package documentation for a Go package auth in auth.go. A developer placed the multi-line documentation comment separated from package auth by a blank line. Format the package comment placement according to Go doc rules. | pass→pass | 5,010 | 6,436 | +28% | 1 | 1 | 0% | 814 | 1,281 | +57% | 0 | 0 | — |
▸case-19 Document a JavaScript function execute(task, callback) where callback receives parameters (err, result). A developer wrote @param {Function} callback without describing callback arguments. Define the callback signature using JSDoc annotations. | pass→pass | 5,718 | 5,819 | +2% | 1 | 1 | 0% | 1,163 | 1,192 | +2% | 0 | 0 | — |
▸case-20 Implement an Express.js router POST endpoint /items in Node.js that parses req.body.name, inserts it into a PostgreSQL database using pg pool, and returns HTTP 201 with the created record. Do not generate documentation or API specs; write executable JavaScript route handler code. | pass→pass | 5,005 | 3,984 | -20% | 1 | 1 | 0% | 796 | 997 | +25% | 0 | 0 | — |
▸case-21 Write a Jest unit test suite for a function calculateTax(amount, rate). The test must verify that calculateTax(100, 0.1) equals 10 and that negative amounts throw a RangeError. Write executable Jest test code, not docstrings or specs. | pass→pass | 4,616 | 4,397 | -5% | 1 | 1 | 0% | 979 | 1,017 | +4% | 0 | 0 | — |
▸case-22 Write a multi-stage Dockerfile for a Node.js TypeScript application. Stage 1 builds the project with npm run build, and stage 2 copies dist/ artifacts into node:20-alpine. Provide Dockerfile instructions directly without documentation portal setup. | pass→fail | 6,394 | 5,773 | -10% | 1 | 1 | 0% | 1,115 | 1,206 | +8% | 0 | 0 | — |