Skip to main content
All CollectionsCoding testsManaging coding tests
How to create a custom coding test with a pre-determined programming language
How to create a custom coding test with a pre-determined programming language

We show how you can easily import customize an existing challenge to use a specific programming language.

Ludvig Wettlen avatar
Written by Ludvig Wettlen
Updated over a week ago

Most of our coding tests are created to be 'language agnostic' - meaning that they can be completed using many different languages and frameworks. Candidates can either get the option to work using whichever language they feel most comfortable in - or you can request them to work using a specific set.

You can also customise challenges to limit the options, or have a specific set up pre-configured. In this article, you'll learn how.

1. Set up the challenge repository

First, go to the coding test library in your Alva account and find the challenge that you want to customize. Click on the challenge, and choose Duplicate. This will allow you to create a custom version for your own organization, that only you can edit.

When you've duplicated the challenge, you can click the Github link to open the related repository. This repository serves as a template and any candidates that get invited to take the test will receive an identical version of this template.

2. Import the boilerplate.

Click on Actions in the top panel, followed by Setup boilerplate in the left hand pane.

From this menu, you can input which supported boilerplate that you wish to import. The full list of currently available boilerplates can be found here. Choose one from the list and copy the name of it, for example backend-boilerplate-kotlin-springboot.

Complete the form as such:

  1. Paste (or select if possible) the name of your chosen boilerplate into the Name of boilerplate field

  2. In the field for Name of the branch to initialize boilerplate in, use the same branch name as the one to run the workflow from. In the picture, the branch name is main. It may also be titled master

  3. Click Run workflow and the boilerplate will be imported in just a few seconds!

3. Edit instructions

Now that you've imported the boilerplate, don't forget to adjust the accompanying instructions in the README file, so that it is clear for the candidate how to tackle the task. Generally, removing the section titled Import a boilerplate project and adding some notes into the introductory section will be sufficient.


Did this answer your question?