In the early days of Exercism we named each track for the programming language, prefixed with an 'x'. This was reflected in the name of the repository as well as the title of the README. At some point we changed this decision, and renamed all the repositories. Over time most of the READMEs have also been updated. Some tracks changed the README title to be just the language name, whereas others changed the title to reflect that this isn't the language itself, but rather the Exercism track for that language. This normalizes the README title. Co-authored-by: Katrina Owen <katrina.owen@gmail.com>
Exercism ABAP Track
Exercism exercises in ABAP
This is the ABAP track, one of the many tracks on Exercism. It holds all the exercises that are currently implemented and available for students to complete. The track consists of various various practice exercises which you can find in the config.json.
Exercises for Students
With exercism, you can solve and test all exercises directly on the Exercism website.
Alternatively, you can clone this repository to your own SAP system using abapGit. Solve the exercises in your system and bring the solution back to the website.
For details, see Testing on the ABAP track
Contributing to the Track
We welcome contributions of all sorts and sizes, from reporting issues to submitting patches, or added complete new exercises.
For details, see Contribution Guidelines.
Testing
To test the exercises, run ./bin/test.
This command will iterate over all exercises and check to see if their exemplar/example implementation passes all the tests.
Track Linting
configlet is an Exercism-wide tool for working with tracks. You can download it by running:
$ ./bin/fetch-configlet
Run its lint command to verify if all exercises have all the necessary files and if config files are correct:
$ ./bin/configlet lint
The lint command is under development.
Please re-run this command regularly to see if your track passes the latest linting rules.
Basic linting finished successfully:
- config.json exists and is valid JSON
- config.json has these valid fields:
language, slug, active, blurb, version, status, online_editor, key_features, tags
- Every concept has the required .md files
- Every concept has a valid links.json file
- Every concept has a valid .meta/config.json file
- Every concept exercise has the required .md files
- Every concept exercise has a valid .meta/config.json file
- Every practice exercise has the required .md files
- Every practice exercise has a valid .meta/config.json file
- Required track docs are present
- Required shared exercise docs are present