{"id":19446356,"url":"https://github.com/SkillPanel/devskiller-sample-apex","last_synced_at":"2026-07-18T14:30:18.636Z","repository":{"id":54615831,"uuid":"336273254","full_name":"Devskiller/devskiller-sample-apex","owner":"Devskiller","description":"Salesforce Apex - Sample programming task","archived":false,"fork":false,"pushed_at":"2021-11-04T13:11:15.000Z","size":10,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":5,"default_branch":"main","last_synced_at":"2025-01-07T22:54:35.237Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Apex","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Devskiller.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2021-02-05T13:02:23.000Z","updated_at":"2021-11-04T13:11:18.000Z","dependencies_parsed_at":"2022-08-13T21:40:32.289Z","dependency_job_id":null,"html_url":"https://github.com/Devskiller/devskiller-sample-apex","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Devskiller%2Fdevskiller-sample-apex","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Devskiller%2Fdevskiller-sample-apex/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Devskiller%2Fdevskiller-sample-apex/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Devskiller%2Fdevskiller-sample-apex/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Devskiller","download_url":"https://codeload.github.com/Devskiller/devskiller-sample-apex/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":240631441,"owners_count":19832271,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-10T16:13:45.188Z","updated_at":"2026-07-18T14:30:18.582Z","avatar_url":"https://github.com/Devskiller.png","language":"Apex","funding_links":[],"categories":[],"sub_categories":[],"readme":"# DevSkiller programming task sample - Apex\n\n## Introduction\n\nWith [DevSkiller.com](https://devskiller.com) you can assess your candidates'\nprogramming skills as a part of your recruitment process. We have found that\nprogramming tasks are the best way to do this and have built our tests\naccordingly. The way our test works is your candidate is asked to modify the\nsource code of an existing project.\n\nDuring the test, your candidates have the option of using our browser-based\ncode editor and can build the project inside the browser at any time. If they\nwould prefer to use an IDE they are more comfortable with, they can also\nclone the project’s Git repository and work locally.\n\nYou can check out this short video to see the test from the [candidate's\nperspective](https://devskiller.zendesk.com/hc/en-us/articles/360019534639-How-the-TalentScore-test-looks-like-from-the-candidate-perspective).\n\nThis repo contains a sample project for Apex and below you can\nfind a detailed guide for creating your own programming project.\n\n**Please make sure to read our [Getting started with programming\nprojects](https://devskiller.zendesk.com/hc/en-us/articles/360019531059-Getting-started-with-Programming-Tasks) guide first**\n\n## Technical details\n\n- The project structure has to have the sfdx project structure. All the files have to be in proper folders and include metadata files when needed (for example, the Calculator Apex class consists of two files `Calculator.cls` and `Calculator.cls-meta.xml`).\n\n- What is more, if your code includes custom objects or custom fields, their metadata files also have to be added to the structure (see the `Value__c.field-meta.xml` custom field of the `Tax__c` custom object in the example). The same thing goes for all other metadata like Profiles, Flows, Workflows, etc.\n\n- Furthermore, the project has to include a permission set to all the necessary fields (both standard and custom). The permission set has to be named like in the example: `Fields.permissionset-meta.xml`.\n\n## Automatic assessment\n\nIt is possible to automatically assess the solution posted by the candidate.\nAutomatic assessment is based on unit tests results and code quality\nmeasurements.\n\nThere are two kinds of unit tests:\n\n1. **Candidate tests** - unit tests that the candidate can see during the test\n   should be used only for basic verification and to guide the candidate in\n   understanding the requirements of the project. By default candidate tests **WILL NOT** be used\n   to calculate the final score (see example in `CalculatorTest.cls`).\n2. **Verification tests** - unit tests that the candidate can’t see during the\n   test. Files containing verification tests will be added to the project after\n   the candidate finishes the test and will be executed during the verification\n   phase. The results of the verification tests will be used to calculate the\n   final score(see example in `IllegalArgumentsTest.cls` and `RandomNumbersTest.cls`).\n\nOnce the solution is developed and submitted, the platform executes\nverification tests and performs static code analysis.\n\n## Devskiller project descriptor\n\nProgramming tasks can be configured with the Devskiller project descriptor file:\n\n1. Create a `devskiller.json` file.\n2. Place it in the root directory of your project.\n\nHere is an example project descriptor:\n\n```json\n{\n    \"readOnlyFiles\": [\n        \"force-app/main/default/classes/*Test*\",\n        \"force-app/main/default/objects/**\",\n        \"sfdx-project.json\"\n    ],\n    \"hiddenFiles\": [],\n    \"verification\": {\n        \"testClassNamePatterns\": [\n            \".*CalculatorTest.*\"\n        ],\n        \"pathPatterns\": [\n            \"**verify_pack**\"\n        ],\n    }\n}\n```\n\nNote: If you want to, you can include Candidates test in scoring as above. \n\nYou may find more information regarding the `devskiller.json` descriptor in our\n[documentation](https://devskiller.zendesk.com/hc/en-us/articles/360019530419-Programming-task-project-descriptor).\n\n## Automatic verification with verification tests\n\nThe solution submitted by the candidate may be verified using automated tests.\nYou’ll just have to define which tests should be treated as verification tests.\n\nAll files classified as verification tests will be removed from the project\nprior to inviting the candidate.\n\nTo define verification tests, you need to set two configuration properties in\n`devskiller.json`:\n\n- `testClassNamePatterns` - an array of RegEx patterns which should match all the\n  names of the verification tests.\n- `pathPatterns` - an array of GLOB patterns which should match all the files\n  containing verification tests. All the files that match defined patterns will\n  be deleted from candidates' projects and will be added to the projects during\n  the verification phase. These files will not be visible to the candidate during\n  the test.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FSkillPanel%2Fdevskiller-sample-apex","html_url":"https://awesome.ecosyste.ms/projects/github.com%2FSkillPanel%2Fdevskiller-sample-apex","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FSkillPanel%2Fdevskiller-sample-apex/lists"}