File tree 3 files changed +27
-0
lines changed
3 files changed +27
-0
lines changed Original file line number Diff line number Diff line change 230
230
"path" : " building/tracks/new/prepare-for-launch.md" ,
231
231
"title" : " Prepare for launch"
232
232
},
233
+ {
234
+ "uuid" : " 3d4a4f07-7229-4910-9ba5-b7d931ff9177" ,
235
+ "slug" : " tracks/new/test-track" ,
236
+ "path" : " building/tracks/new/test-track.md" ,
237
+ "title" : " Test track"
238
+ },
233
239
{
234
240
"uuid" : " 296dbe06-3384-409b-b2de-be52593c76d3" ,
235
241
"slug" : " tracks/new/find-maintainers" ,
Original file line number Diff line number Diff line change @@ -15,6 +15,7 @@ Once you've completed that step, the next steps are:
15
15
- [ Build test runner] ( /docs/building/tracks/new/build-test-runner )
16
16
- [ Configure tooling] ( /docs/building/tracks/new/configure-tooling )
17
17
- [ Prepare for launch] ( /docs/building/tracks/new/prepare-for-launch )
18
+ - [ Test track] ( /docs/building/tracks/new/test-track )
18
19
- [ Find Maintainers] ( /docs/building/tracks/new/find-maintainers )
19
20
- [ Launch!] ( /docs/building/tracks/new/launch )
20
21
- [ Enable syntax highlighting] ( /docs/building/tracks/new/syntax-highlighting )
Original file line number Diff line number Diff line change
1
+ # Test track
2
+
3
+ _ Before_ launching your track (meaning, the ` "active" ` key is still ` false ` in the track's ` config.json ` ), it is important the track is tested.
4
+ This will help find (common) errors and allows them to be fixed _ before_ the track is launched, which means that students won't ever encounter them.
5
+
6
+ ## How to enable the track for testing
7
+
8
+ To enable the track for testing, it needs to be added to our database, which is something only site admins can do.
9
+ Please open a topic on the forum requesting this at: https://forum.exercism.org/c/exercism/building-exercism/125 .
10
+
11
+ Note that adding the track to the database will _ not_ launch the track, but it _ will_ make it accessible on the website for maintainer users.
12
+
13
+ ## How to find testers
14
+
15
+ The ideal users to test the track are other track maintainers, as they:
16
+
17
+ - Have experience building a track (and thus know what should have been built)
18
+ - Are able to access track's that are not yet active
19
+
20
+ To get maintainers to test your track, open a topic on the forum requesting this at: https://forum.exercism.org/c/exercism/building-exercism/125 .
You can’t perform that action at this time.
0 commit comments