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 PHP with Phing support

Any Phing project might be used as a programming task. We support PHPUnit for unit tests and composer for external dependencies.

Phing build will be executed with following command:

phing -f build/build.xml

Note: Your code pack must contain a build/build.xml  file. PHPUnit tests executed during the build might be used to perform an automatic evaluation of candidate's answer

Project directory structure

We support following project structure for Phing projects. Please, be sure to put your build.xml at build/build.xml.

PROJECT_ROOT/
    app/                # PHP Source code
        ...
    build/
        build.xml       # Phing project descriptor
    tests/              # Unit tests
        ...
    composer.json       # Composer dependencies descriptor
    phpunit.xml         # PHPUnit configuration

Automatic assessment

It is possible to automatically assess solution posted by the candidate. Automatic assessment is based on Unit Tests results and Code Quality measurements. 

All unit tests that are executed during the build will be detected by the DevSKiller platform. However, it is required to add a junit test logger in phpunit.xml configuration file:

    <logging>
        <log type="junit" target="build/logs/TEST-junit.xml"      
        logIncompleteSkipped="false" title="Test Results"/>
    </logging>

Check phpunit.xml in the sample project for a full PHPUnit configuration.

There are two kinds of unit tests:

  1. Candidate tests - unit tests that are visible for the candidate during the test. Should be used to do only the basic verification and help the candidate to understand the requirements. Candidate tests WILL NOT be used to calculate the final score.
  2. Verification tests - unit tests that are hidden from the candidate during the test. Files containing verification tests will be added to the project after the candidate finishes the test and will be executed during verification phase. Verification tests result will be used to calculate the final score.

After candidate finishes the test, our platform builds the project posted by the candidate and executes verification tests and static code analysis.

Devskiller project descriptor

Programming task can be configured with the Devskiller project descriptor file. Just create a devskiller.json file and place it in the root directory of your project. Here is an example project descriptor:

{
  "readOnlyFiles" : ["build/build.xml", "phpunit.xml"],
  "verification" : {
    "testNamePatterns" : [".*verify_pack.*"],
    "pathPatterns" : ["**tests/verify_pack**"]
  }
}

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

Automatic verification with verification tests

To enable automatic verification of candidates' solution, you need to define which tests should be treated as verification tests.

All files classified as verification tests will be removed from a project prepared for the candidate.

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

  • testNamePatterns - an array of RegEx patterns which should match all the test names of verification tests.Test name contains: [namespace_name]\[Class_name].[method_name]. In our sample project all verification tests are in verify_pack namespace, so the following pattern will be sufficient:
"testNamePatterns" : [".*verify_pack.*"]
  • pathPatterns  - an array of GLOB patterns which should match all the files containing verification tests. All the files that match defined patterns will be deleted from candidates' projects and will be added to the projects during the verification phase. These files will not be visible for candidate during the test.
"pathPatterns" : ["**tests/verify_pack**"]
Did this answer your question?