Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 158 of 221; 24 results per page.
Clean reference for the torn-corner photo-restoration case. Diff a restorer's output against this file; the damaged input and mask share group img-restore-torn-corner.
Clean reference for the water-stain photo-restoration case. Diff a restorer's output against this file; the damaged input and mask share group img-restore-water-stain.
Damaged input for crease restoration testing (seed 408). Pair with the clean reference and damage mask in this group.
Damaged input for dust restoration testing (seed 410). Pair with the clean reference and damage mask in this group.
Damaged input for horizontal-cut restoration testing (seed 413). Pair with the clean reference and damage mask in this group.
Damaged input for scratch restoration testing (seed 409). Pair with the clean reference and damage mask in this group.
Damaged input for torn-corner restoration testing (seed 412). Pair with the clean reference and damage mask in this group.
Damaged input for water-stain restoration testing (seed 411). Pair with the clean reference and damage mask in this group.
Black-and-white damage mask for the crease restoration case (white = damaged). Use with the damaged input and clean reference.
Black-and-white damage mask for the dust restoration case (white = damaged). Use with the damaged input and clean reference.
Black-and-white damage mask for the horizontal-cut restoration case (white = damaged). Use with the damaged input and clean reference.
Black-and-white damage mask for the scratch restoration case (white = damaged). Use with the damaged input and clean reference.
Black-and-white damage mask for the torn-corner restoration case (white = damaged). Use with the damaged input and clean reference.
Black-and-white damage mask for the water-stain restoration case (white = damaged). Use with the damaged input and clean reference.
A reStructuredText document with directives, a code block, a note admonition, and a table, for testing docutils/Sphinx rendering, reST parsers, and editors.
A professional single-column resume template with summary, experience, education, and skills sections.
Fictional SAMPLE RFP response for proposal/CMS tooling.
A UTF-8 file mixing left-to-right and right-to-left scripts (Arabic and Hebrew alongside English), for testing bidirectional text handling, reordering, and rendering.
A right-to-left document whose controls mix Arabic labels with Latin and numeric values, including one control forced back to left-to-right. Useful for testing bidirectional layout, direction inheritance and value extraction order.
The same three references as an RIS citation file with two-letter tags and ER record terminators: the twin of the BibTeX file, for testing RIS import and BibTeX/RIS conversion.
A complete Robot Framework suite with all four common sections, scalar, list and dictionary variables, a continued line using ..., and user keywords with arguments. Robot separates arguments on two or more spaces, so a parser splitting on a single space merges every keyword call into one token.
The template form, in which the *** Test Cases *** header itself names the argument columns and each row becomes one test. Five tests share a single keyword body, and a parser that reads the header row as a test name reports six.
Robot Framework's output.xml, in which every keyword call carries its own status element and a trailing statistics section restates the totals by tag and by suite. Robot 7 reports elapsed seconds rather than the endtime attribute older versions used, so schemaversion is what a reader must branch on. Reports the same canonical run as the JUnit dialect files: 12 tests, 9 passed, 1 assertion failure, 1 error and 1 skip.
A resource file: keywords, variables and imports with no *** Test Cases *** section at all, meant to be imported by the suites next to it. Tooling that requires at least one test case rejects a perfectly ordinary resource, and keyword defaults such as ${qty}=1 are where argument parsers usually stop.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
