Sample Dockerfile
Sample Dockerfile — small deterministic fixture for parsers and the in-browser editor.
FROM node:20-alpine
WORKDIR /app
COPY package*.json .
RUN npm ci
COPY . .
CMD ["npm","start"]
Specifications
- Role
- sample fixture
Testing contract
Expected to pass- Scenario
- Exercise Sample Dockerfile in its config workflow. Sample Dockerfile — small deterministic fixture for parsers and the in-browser editor.
- Expected result
- 6 text lines, decoded as UTF-8; first nonempty line is 'FROM node:20-alpine'. Declared feature checks: role=sample fixture.
What is a .dockerfile file?
A Dockerfile is a plain-text script of instructions that Docker reads to build a container image layer by layer, using directives like FROM, RUN, COPY, and CMD. Each instruction defines a step in assembling a reproducible image. It is the standard definition format for containerized applications.
How to use this file
Use an example Dockerfile to test instruction parsers and linters, build-tool integration, and tooling that analyzes or generates container image definitions.
How to use this file for testing
“Sample Dockerfile” is a deterministic Novus Examples fixture for Editor testing, Config parsing. Text-based files you can open, edit, and download directly in the browser editor.
Documented properties for this file: sample fixture. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Web-platform fixtures are standards-compliant samples against fictional example.com data. Test crawlers, PWA installers and manifest validators, favicon/icon pipelines, service-worker registration, or .well-known parsers against the documented structure.
Related files
- envSample App .envSample App .env — small deterministic fixture for parsers and the in-browser editor.
- txtmta-sts.txt (RFC 8461 SMTP MTA-STS policy)An SMTP MTA-STS policy in enforce mode listing three MX patterns, one of them a wildcard, with a seven-day max_age. RFC 8461 specifies CRLF line endings, so this fixture is written with them deliberately - for testing policy parsers that split on bare LF.
- yamlArgo CD Application with Sync PolicyAn Argo CD Application with automated sync, prune and self-heal, retry backoff, sync options, and an ignoreDifferences rule that exempts replica counts from drift detection. All Git and cluster endpoints are example.invalid.
- yamlArgo CronWorkflow ScheduleAn Argo CronWorkflow wrapping an inline workflowSpec: a cron schedule with an explicit timezone, Replace concurrency, history limits, and a suspend flag. Nested-spec shape that flat schedule extractors miss.
- ymlAzure Pipelines Matrix StrategyAzure's named-leg matrix form, where each leg is a mapping of variables rather than an axis product: three Python legs, a maxParallel cap, a job timeout, and a JUnit results publish step that runs on failure too.
- ymlAzure Pipelines Stages and Deployment JobA three-stage Azure Pipelines definition with a build-number format expression, a variable group reference, stage conditions built from the expression functions, and a deployment job using the runOnce strategy against a named environment.
Generated by generation/breadth_extra_wave_c.py. Free for any use, no attribution required, license.