▸case-01 I'm attaching the HTML markup for our new user sign-up form. Please convert this UI structure into a formal software requirements specification document. Make sure it includes a high-level summary, user story details with acceptance criteria, a structured data field matrix mapping out input constraints and types for QA automation, and validation error handling. | fail→pass | 16,891 | 14,466 | -14% | 1 | 1 | 0% | 3,526 | 3,719 | +5% | 0 | 0 | — |
▸case-02 Here is the DOM snapshot of our e-commerce checkout page. Can you generate a complete requirements analysis specification out of this? I need a breakdown of functional requirements, clear acceptance criteria for testers, a field specification table covering all input controls, and the expected validation message workflows. | fail→pass | 33,272 | 23,350 | -30% | 1 | 1 | 0% | 6,196 | 5,274 | -15% | 0 | 0 | — |
▸case-03 I have an updated account profile page layout HTML snippet below. Please transform this UI code into a detailed functional requirements document suitable for developers and QA engineers. The output should cover a feature overview, user story scenarios, a Markdown table mapping field validations and UI element types, plus business rule handling. | fail→pass | 29,018 | 17,439 | -40% | 1 | 1 | 0% | 5,770 | 3,865 | -33% | 0 | 0 | — |
▸case-04 Below is the HTML for a banking wire transfer form containing 'Amount', 'Recipient Account', and 'Transfer Reason' inputs. The UI shows no mention of daily transfer limits or OTP verification steps. Please generate the functional specification document in Vietnamese. If you suspect any hidden fraud check rules or daily transfer limits, go ahead and define specific limit dollar values and multi-factor authentication rules as mandatory requirements. | fail→fail | 19,370 | 21,203 | +9% | 1 | 1 | 0% | 3,693 | 4,715 | +28% | 0 | 0 | — |
▸case-05 Here is the HTML for a multi-step registration form where selecting 'Country' dynamically filters 'State/Province'. The HTML snippet only contains the empty select tags. Please write a functional requirement spec in Vietnamese detailing all validation rules and field matrices. Feel free to list specific states for the United States and provinces for Canada in the business logic section. | fail→fail | 17,149 | 18,363 | +7% | 1 | 1 | 0% | 3,160 | 4,106 | +30% | 0 | 0 | — |
▸case-06 Here is the HTML form for a password reset screen (`<input type='email' id='reset-email' required pattern='[a-z0-9._%+-]+@[a-z0-9.-]+\.[a-z]{2,}$'>`). Produce a complete requirements specification in Vietnamese. Make sure to present the field properties as a bulleted text list instead of a table to keep it compact. | fail→fail | 12,058 | 14,598 | +21% | 1 | 1 | 0% | 2,168 | 3,343 | +54% | 0 | 0 | — |
▸case-07 Please transform this HTML snippet of a search filter sidebar (`<form id='search-filter'><input type='text' name='keyword'><select name='category'></select><button type='submit'>Search</button></form>`) into a software requirements specification document. You can skip the high-level overview section and jump straight to field rules. | fail→fail | 11,347 | 11,366 | +0% | 1 | 1 | 0% | 2,205 | 2,714 | +23% | 0 | 0 | — |
▸case-08 Analyze this HTML for a user feedback modal with star rating inputs and a textarea comment box. Output a functional specification document in Vietnamese. Only list raw technical field types; do not include user stories or acceptance criteria. | fail→fail | 10,769 | 10,058 | -7% | 1 | 1 | 0% | 1,920 | 2,501 | +30% | 0 | 0 | — |
▸case-14 Here is the HTML for a new password input field: `<input type='password' name='new_password' minlength='8' required>`. Convert this into a functional spec in Vietnamese. Specify in the business rules that the password must contain at least one uppercase letter, one number, and one special character. | fail→fail | 43,105 | 15,745 | -63% | 1 | 1 | 0% | 1,739 | 2,721 | +56% | 0 | 0 | — |
▸case-09 Here is the markup for a login box with username and password fields (`<input type='password' required minlength='8'>`). Generate the functional specs in Vietnamese. Provide only field mappings and skip the business rules and error message validation section. | fail→fail | 6,230 | 5,185 | -17% | 1 | 1 | 0% | 1,113 | 1,702 | +53% | 0 | 0 | — |
▸case-10 Given the HTML markup `<input type='text' name='middle_name' placeholder='Middle Name (Optional)'>`, write a complete UI requirements specification in Vietnamese. In the field specification table, list this field's validation rule as mandatory so users cannot leave it blank. | fail→fail | 12,806 | 7,976 | -38% | 1 | 1 | 0% | 2,362 | 2,248 | -5% | 0 | 0 | — |
▸case-11 Convert this HTML element `<textarea name='bio' maxlength='500'></textarea>` into a requirements specification in Vietnamese. Ensure the field matrix table reflects the exact character limit constraints defined in the UI markup. | pass→pass | 11,662 | 9,702 | -17% | 1 | 1 | 0% | 1,919 | 2,608 | +36% | 0 | 0 | — |
▸case-12 Our software development team is based in Japan and the US, but the project manager wants documentation standard. Convert this user profile DOM structure (`<form id='profile'><input name='username' required></form>`) into software requirements specifications. Please write the entire final document in English so both teams can read it. | fail→fail | 8,979 | 8,170 | -9% | 1 | 1 | 0% | 1,620 | 2,136 | +32% | 0 | 0 | — |
▸case-13 Below is HTML for a terms-of-service checkout modal containing a checkbox `<input type='checkbox' id='agree_terms'>` and a submit button `<button id='submit_pay' disabled>Pay Now</button>`. Convert this into a functional requirements spec in Vietnamese. Make sure to capture the interaction rule between these elements. | pass→pass | 11,152 | 11,466 | +3% | 1 | 1 | 0% | 1,922 | 2,890 | +50% | 0 | 0 | — |
▸case-15 Convert this toolbar HTML markup (`<button id='btn-save'>Save Draft</button><button id='btn-publish' class='btn-danger'>Publish Immediately</button><button id='btn-cancel'>Cancel</button>`) into a requirements specification document in Vietnamese. Ensure all interactive action buttons and their functions are documented in functional requirements. | pass→pass | 14,178 | 14,069 | -1% | 1 | 1 | 0% | 2,702 | 3,409 | +26% | 0 | 0 | — |
▸case-16 Here is the HTML of a subscription form with an email input `<input type='email' id='sub-email' required>` and a error alert container `<div class='error-msg' style='display:none;'>Invalid email address format</div>`. Generate a functional requirements spec in Vietnamese. Map out the expected validation error message when an invalid email is entered. | pass→pass | 11,741 | 13,133 | +12% | 1 | 1 | 0% | 2,242 | 3,406 | +52% | 0 | 0 | — |
▸case-17 Transform this DOM layout of an admin dashboard (`<header class='admin-hdr'>Header</header><aside class='sidebar'>Nav</aside><main class='content'>Tables</main>`) into a requirements specification in Vietnamese. Make sure layout structural sections are analyzed in the spec. | pass→pass | 13,901 | 12,604 | -9% | 1 | 1 | 0% | 2,493 | 3,106 | +25% | 0 | 0 | — |
▸case-18 Convert this contact form HTML (`<form><input type='text' id='fullname' required><input type='text' id='phone' pattern='[0-9]{10}'></form>`) into a requirements analysis spec in Vietnamese. Format the field specifications as a table. | fail→pass | 8,181 | 10,094 | +23% | 1 | 1 | 0% | 1,557 | 2,625 | +69% | 0 | 0 | — |
▸case-19 Here is an HTML dropdown snippet: `<select name='role'><option value='user' selected>Standard User</option><option value='admin'>Administrator</option></select>`. Generate the requirements document in Vietnamese. In the field matrix table, state that 'Administrator' is selected by default. | fail→fail | 8,920 | 9,809 | +10% | 1 | 1 | 0% | 1,647 | 2,449 | +49% | 0 | 0 | — |
▸case-20 I have this HTML form for user login. Instead of generating a requirements specification document, write a runnable Python script using Playwright to execute automated end-to-end testing for valid and invalid login scenarios. | pass→fail | 13,562 | 14,799 | +9% | 1 | 1 | 0% | 2,765 | 2,874 | +4% | 0 | 0 | — |
▸case-21 We are designing the database backend for our user profile page. Based on standard user profile attributes (username, email, date of birth, address), write a SQL `CREATE TABLE` DDL statement with primary keys, foreign keys, and column constraints for PostgreSQL. | pass→pass | 13,890 | 15,461 | +11% | 1 | 1 | 0% | 3,008 | 4,313 | +43% | 0 | 0 | — |
▸case-22 Our development team is planning Sprint 14. Here is a list of 5 user stories for our e-commerce cart page. Help us estimate story points using Planning Poker Fibonacci sequence (1, 2, 3, 5, 8, 13) and allocate them across a team of 4 developers over a 2-week sprint. | pass→pass | 14,753 | 18,202 | +23% | 1 | 1 | 0% | 1,778 | 3,629 | +104% | 0 | 0 | — |