You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 4, 2020. It is now read-only.
For now, we'll do single-line regexp-based tests. We propose to have the following structure for each service:
$tt_root/$service/
TT files come here.
pan
Contains at least schema.pan.
test/
profiles/
Contains test profiles for this service. The data we feed to
the file starts from "/metaconfig" in the profile, for simplicity.
regexps/
Contains the regular expressions the rendered TT file for each
profile should match. For each profile we'll have either:
A single file with the same name of that profile.
A directory containing all the regular expression files for
that profile. The name of the directory must be the same of
the profile, and the names of the files is free.
Then, each regexp file file will have a description header, a separator and one regexp per line, like this.
We want to test how these templates render.
For now, we'll do single-line regexp-based tests. We propose to have the following structure for each service:
$tt_root/$service/
pan
Contains at least
schema.pan
.test/
profiles/
Contains test profiles for this service. The data we feed to
the file starts from "/metaconfig" in the profile, for simplicity.
regexps/
Contains the regular expressions the rendered TT file for each
profile should match. For each profile we'll have either:
that profile. The name of the directory must be the same of
the profile, and the names of the files is free.
Then, each regexp file file will have a description header, a separator and one regexp per line, like this.
All sections are mandatory, but can be empty.
We'll package only the .tt files and the
json2tt
script fordevelopment and debugging purposes.
The text was updated successfully, but these errors were encountered: