Skip to content
Novus Examples
ini75 B

App Config (INI)

Sample INI config file for legacy config parser tests.

Preview, first 7 linesini
[DEFAULT]
env = sample

[database]
host = localhost
name = sample_db

Specifications

Format
INI

Testing contract

Expected to pass
Scenario
Exercise App Config (INI) in its config workflow. Sample INI config file for legacy config parser tests.
Expected result
6 text lines, decoded as UTF-8; first nonempty line is '[DEFAULT]'.

What is a .ini file?

INI is an informal configuration format organizing key-value pairs under bracketed section headers, with comment lines and no strict standard. Parsing details like comment characters, quoting, and nesting vary between implementations. It is a long-standing choice for simple application and system configuration.

How to use this file

Use an example INI file to test section and key-value parsing, comment handling, and configuration loaders that must tolerate dialect differences.

How to use this file for testing

“App Config (INI)” is a deterministic Novus Examples fixture for Config testing, Conversion testing. TOML, INI, YAML, .env, and dotfile configuration samples with nested sections and typed values, for testing config parsers, loaders, and environment tooling.

Documented properties for this file: INI. 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.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.

Code examples

import configparser

c = configparser.ConfigParser()
c.read("app.ini")
print(c.sections())

Generated by generation/data_wave_f.py. Free for any use, no attribution required, license.