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 187 of 221; 24 results per page.
Intentionally invalid semantic test records for Tern Client Services. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.
Linked operating model for Tern Client Services. 98 records across 9 linked tables; no duplicate primary keys or missing references. Total deal value=34,500.00 USD; Weighted deal value=15,825.00 USD; Recorded activity time=720.00 minutes.
Numeric expected results for Tern Client Services. Exact table counts, metric formulas, 4 chart points and three negative-test outcomes. Total deal value=34,500.00 USD; Weighted deal value=15,825.00 USD; Recorded activity time=720.00 minutes.
Operating chart PNG for Tern Client Services. A 1440 by 900 RGB chart with 4 labeled source-derived observations in USD.
Operating model JSON Schema for Tern Client Services. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.
Operating report PDF for Tern Client Services. Three readable pages summarize the same model, chart, source tables and usage instructions. Total deal value=34,500.00 USD; Weighted deal value=15,825.00 USD; Recorded activity time=720.00 minutes.
Workflow and import guide for Tern Client Services. Documents 9 source tables, exact expected totals and supported versus manual workflows.
An intentionally invalid Terraform configuration: an unclosed resource block, a colon where HCL needs an equals sign, a reference to an undeclared resource, and a resource block missing its second label. Four documented faults for a parser to report.
A terraform.tfvars assigning the staging defaults, including a nested map-of-objects value. Pairs with the production overrides file, which replaces that map wholesale rather than merging into it.
The expression-heavy half of the stack: for expressions producing both a map and a filtered list, conditional expressions selecting whole objects, and a dynamic block that generates two firewall rules from a local list.
Three module calls covering the shapes a dependency grapher has to handle: a local path with explicit provider passing, a versioned registry source under for_each, and a count-gated conditional module.
Five Terraform outputs exercising a splat expression over a counted resource, a for expression over a for_each module, and a sensitive output that must stay redacted when propagated from a sensitive input.
A Terraform plan JSON document with create, update and delete changes, after_unknown markers, sensitivity annotations, and a configuration section. This is the artifact policy engines read before anything runs, which is why it sits with pipeline definitions rather than with run reports.
The production tfvars overrides. Its point is a semantic that surprises people: a complex-typed variable is replaced whole, not deep-merged, so the staging app-b subnet does not survive the override.
The terraform settings block: a version constraint range, two pinned providers, a local backend, default tags, and a second aliased provider configuration. The fictional examplecloud provider means nothing resolves to a real service.
The resource graph: a network, a for_each subnet set, a counted instance resource, a data source, and a bucket on an aliased provider. Both repetition meta-arguments appear, plus lifecycle and an explicit depends_on edge.
Sample terraform.tfvars with fictional region, for HCL/tfvars parser tests.
Seven Terraform variables covering string, number, map and a map(object) with an optional attribute and a default, plus two validation blocks with error messages. The sensitive variable's default is explicitly a SAMPLE note, not a credential.
Twelve test cases with level, priority, the requirement each covers, preconditions, steps and expected result: the table a test-management import expects. Eleven of the twelve are automated, and the requirement column joins this file to the traceability matrix next to it.
A complete release test plan for the fictional Novus Checkout Service: scope, test levels, entry and exit criteria, a risk table and deliverables. Useful as a Markdown-rendering fixture with three tables and nested lists, and as a realistic input for documentation tooling that has to extract structure from prose.
TestNG's own result document, with suite/test/class/test-method nesting, signature attributes and full stack traces in CDATA. TestNG has no error status, so the errored case is reported as FAIL and the header attributes read failed=2. Reports the same canonical run as the JUnit dialect files: 12 tests, 9 passed, 1 assertion failure, 1 error and 1 skip.
A set of 24 L2-normalised 16-dimensional text embeddings as JSON: each record pairs an id and its source text with a float vector. A fixture for testing vector stores, similarity search, and embedding loaders. Parquet and .npy twins included.
The same 16-dimensional embeddings as Apache Parquet: id and text columns plus one column per dimension. The columnar twin, for testing analytics engines and Parquet-based vector pipelines.
The embeddings as a raw NumPy array: a 24×16 float32 matrix in .npy format, loadable with numpy.load. The binary twin of the JSON and Parquet files, for testing tensor and matrix loaders.
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.
