Build analyzer #48
Labels
x:action/create
Work on something from scratch
x:knowledge/advanced
Comprehensive Exercism knowledge required
x:module/analyzer
Work on Analyzers
x:size/massive
Massive amount of work
x:type/coding
Write code that is not student-facing content (e.g. test-runners, generators, but not exercises)
In Exercism v3, we are making increased use of our v2 analyzers. Analyzers automatically assess student's submissions and provide mentor-style commentary. They can be used to catch common mistakes and/or do complex solution analysis that can't easily be done directly in a test suite.
Each analyzer is track-specific. When a new solution is submitted, we run the track's analyzer, which outputs a JSON file that contains the analysis results.
In v2, analyzer comments were given to a mentor to pass to a student. In v3, the analyzers will normally output directly to students, although we have added an extra key to output suggestions to mentors. If your track already has an analyzer, the only requisite change is updating the outputted copy to be student-facing.
The analyzer is an optional tool though, which means that if a track does not have an analyzer, it will still function normally.
Goal
Build an analyzer for your track according to the spec. Check this page to help you get started with building an analyzer.
It can be very useful to check how other tracks have implemented their analyzer.
If your track already has a working analyzer, please close this issue and ensure that the
.status.analyzer
key in the trackconfig.json
file is set totrue
.Choosing between representer and analyzer
There is some overlap between the goals of the representer and the analyzer. If you want to build both, we recommend starting by building the representer for the following reasons:
Tracking
exercism/v3-launch#53
The text was updated successfully, but these errors were encountered: