TIP: Please make sure to read Getting started with programming tasks first.

You can start with our sample project that can be found on GitHub:

Open sample project.

Download sample project. 

Technical details for DevOps support

With Devskiller.com you can assess your candidates' programming skills as a part of your recruitment process. We have found that programming tasks are the best way to do this and have built our tests accordingly. The way our test works is your candidate is asked to modify the source code of an existing project.

During the test, your candidates have the option of using our browser-based code editor and can build the project inside the browser at any time. If they would prefer to use an IDE they are more comfortable with, they can also download the project code or clone the project’s Git repository and work locally.

You can check out this short video to see the test from the candidate's perspective.

This repo contains a sample DevOps project and below you can find a detailed guide for creating your own programming project.

Please make sure to read our Getting started with programming projects guide first

Technical details

This task consists of two parts:

  • the initialization script init.sh,
  • bats verification tests.

The init.sh script is used for initializing the candidate's Virtual Machine. You can use it to install and pre-configure all required services.

Candidate's files

There are cases when you need to save some candidate's files for a later review. Directory /var/lib/candidate exists on every Virtual Machine and its contents will be archived after the test.

All archived files will be available for the recruiter for a review.

Automatic assessment

It is possible to automatically assess the solution posted by the candidate.

Verification tests are unit tests that are hidden from the candidate. The final score, calculated during verification, is a direct result of the verification tests.

Devskiller project descriptor

Programming tasks can be configured with the Devskiller project descriptor file:

  1. Create a devskiller.json file.
  2. Place it in the root directory of your project.

Here is an example project descriptor:

{
    "verification" : {
        "testNamePatterns" : [ ".*Verification.*" ],
        "pathPatterns" : [ "**verification/verify_**.bats" ]
    }
}

You can find more details about the devskiller.json descriptor in our documentation.

Automatic verification with verification tests

The solution submitted by the candidate may be verified using automated tests. Simply define which tests should be treated as verification tests.

To define verification tests, you need to set two configuration properties in devskiller.json:

  • testNamePatterns - an array of RegEx patterns which should match all the names of the verification tests.
  • pathPatterns - an array of GLOB patterns which should match all the files containing verification tests. These files will not be visible to the candidate during the test.

In our sample task all verifications tests are located in verification/verify_*.bats files and their names start with Verification. In this case the following patterns will be sufficient:

"testNamePatterns" : [".*Verification.*"],
"pathPatterns" : ["**verification/verify_**.bats"]
Did this answer your question?