Skip to content

tests

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History

tests

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 
a.json
a.json
 
 
an_eval.out
an_eval.out
 
 
an_eval.yaml
an_eval.yaml
 
 
demo.py
demo.py
 
 
dict.out
dict.out
 
 
dict.yaml
dict.yaml
 
 
dict_file.out
dict_file.out
 
 
dict_file.yaml
dict_file.yaml
 
 
eval_exec.out
eval_exec.out
 
 
eval_exec.yaml
eval_exec.yaml
 
 
file.out
file.out
 
 
file.yaml
file.yaml
 
 
file_as_meta.out
file_as_meta.out
 
 
file_as_meta.yaml
file_as_meta.yaml
 
 
func.out
func.out
 
 
func.yaml
func.yaml
 
 
func_prep.out
func_prep.out
 
 
func_prep.yaml
func_prep.yaml
 
 
hello.out
hello.out
 
 
hello.yaml
hello.yaml
 
 
meta_file.out
meta_file.out
 
 
meta_file.yaml
meta_file.yaml
 
 
metadata.out
metadata.out
 
 
metadata.yaml
metadata.yaml
 
 
nesting.out
nesting.out
 
 
nesting.yaml
nesting.yaml
 
 
nothing.out
nothing.out
 
 
nothing.yaml
nothing.yaml
 
 
prep.out
prep.out
 
 
prep.yaml
prep.yaml
 
 
recurse.out
recurse.out
 
 
recurse.yaml
recurse.yaml
 
 
test_replacement.py
test_replacement.py
 
 
yaml_as_meta.out
yaml_as_meta.out
 
 
yaml_as_meta.yaml
yaml_as_meta.yaml
 
 

README.md

Template Tests Directory

Each .yaml template file in this tests directory has a corresponding .out file giving the expected output.

Any other files are static input for one or more templates.

All examples from the project documentation should show the file path in this directory as a comment and be kept synchronized.

  • These test cases double as examples.
  • Examples which are not referenced and explained elsewhere in the documentation should have a section in this README.

  1. Base case: no output directives results in no output

  2. Working with dictionaries

  3. Substituting function arguments when 'prep' directive is given

  4. Populating 'meta' from file contents