skills17/task-config
Parses and validates task config files.
Table of contents
Installation
npm install @skills17/task-config
Usage
Create a config.yaml
file for your task in the root folder of the task.
See the configuration section below for a detailed overview of all possible configuration values.
Then, create a new config instance and load the configuration file:
import Config from '@skills17/task-config';
const config = new Config();
await config.loadFromFile();
To load the config synchronously, the additional method loadFromFileSync()
is available.
You can now access the configuration via the available getter methods:
getId()
getSource()
getServe()
getPoints()
getGroups()
getProjectRoot()
getMetadata()
isLocalHistoryEnabled()
arePointsDisplayed()
Or directly create a new test run instance (from @skills17/test-result
) where you can start recording the tests:
const run = config.createTestRun();
run.recordTest('Countries > IndexAll', 'IndexAll', false, true);
Browser
It is also possible to use this library in a browser.
Webpack and other bundlers should automatically pick the correct files.
If you are not using a bundler, make sure to use the lib/index.browser.js
file.
Since the browser does not have access to the filesytem, it cannot load the config.yaml
automatically.
Instead, you have to pass the configuration object directly to the load method:
import Config from '@skills17/task-config';
const config = new Config();
await config.load({ points: { defaultPoints: 2 }, groups: [ ] });
From then on, the same methods can be used as within a node environment, except the getProjectRoot()
method is not available.
Configuration
The following properties are available and can be set in the config.yaml
file.
id: string
Uniquely identifies the task within one championship.
source: string[]
Default: ["./src/**"]
Specifies all source files the competitors are allowed to modify.
All files that do not match will get reset before a test.
The files can be specified by using globs.
tests: string[]
Default: ["./tests/**/*.spec.*", "./tests/**/*.test.*"]
Some skills17 packages require all test files to be specified.
If that is the case, it will be stated in the install instructions.
The files can be specified by using globs.
database: Database
Default:
database:
enabled: false
dump: ./database.sql
name: skills17
user: root
password: ''
host: 127.0.0.1
Defines if a database is used by the tests and if that is the case, which one.
The dump file specifies the location of a valid SQL Dump that will get automatically imported before every test run in order to ensure consistent data across test runs.
serve: Serve
Default:
serve:
enabled: false
port: 3000
bind: 127.0.0.1
mapping:
/: ./src
Some integration tests require that files are accessible over an URL.
If this feature is enabled, the files or directories specified in the mapping
property will be served on the defined endpoint.
The key specifies the URL path and the value the local file path.
localHistory: boolean
Default: false
If true, every executed test run will be saved in JSON locally in a .history
folder.
This later allows a performance analysis over time.
displayPoints: boolean
Default: true
If false, points will not be displayed in the normal output.
For JSON outputs, they will still be available.
points: Points
Default:
points:
defaultPoints: 1
strategy: add
Those settings define how many points a test will award by default and which strategy will be used.
Valid strategies are add
and deduct
.
Those values can be overwritten by a single test or test group.
groups: Group[]
Default: []
A core concept is test groups.
You usually don't want to test everything for one criterion in one test function but instead split it into multiple ones for a cleaner test class and a better overview.
Each test group can have the following configuration:
groups:
match: CountriesIndex.+
displayName: CountriesController::index
defaultPoints: 1
strategy: deduct
maxPoints: 3
tests:
- match: CountriesIndexJson
points: 0
required: true
metadata: Record<string, string>
Default: {}
Can contain any key and value pair which can be used lated in other libraries.
Validation
The config file automatically gets validated against a provided schema at runtime when the configuration is loaded.
Additionally, to get earlier feedback, editors can also be configured to use the provided schema.
The schema is published at: https://schema.skills17.ch/task-config/v3/config.schema.json
Visual Studio Code
Add the following line at the beginning of the config.yaml
file and install the yaml plugin:
Full example
Many of the values in this example are default values and can be left out.
But it shows how a full config.yaml
can look like and what settings are available.
id: js-task-1
source:
- ./src/**
tests:
- ./tests/**/*.spec.*
- ./tests/**/*.test.*
database:
enabled: true
dump: ./database.sql
name: skills17
user: root
password: ''
host: 127.0.0.1
serve:
enabled: true
port: 3000
bind: 127.0.0.1
mapping:
/: ./src
localHistory: false
displayPoints: true
points:
defaultPoints: 1
strategy: add
groups:
- match: CountriesIndex.+
displayName: CountriesController::index
defaultPoints: 1
strategy: deduct
maxPoints: 2
tests:
- match: CountriesIndexJson
points: 0
required: true
- match: CountriesIndexSearch
points: 2
License
MIT